Security Operations Centers have spent years trying to solve essentially the same problem: too much telemetry, too many tools, too many alerts, and not enough time.

We added SIEM platforms to centralize logs. We added SOAR platforms to automate repetitive actions. We introduced XDR to correlate activity across identities, endpoints, email, applications, and cloud resources. More recently, Security Copilot and generative AI started helping analysts summarize incidents and perform investigations.

Now Microsoft is moving toward something significantly bigger.

On September 23, 2026, Microsoft announced the Integrated Security Operations Center, or ISOC, in Microsoft Defender, describing it as the foundation for what Microsoft calls the agentic SOC. Rather than treating SIEM, XDR, automation, threat intelligence, AI, and security agents as independent layers, Microsoft is attempting to bring them together into a common operational system inside the Microsoft Defender portal.

This is more than another Defender portal update.

If Microsoft delivers on the architecture it is describing, the underlying model for how security teams investigate and respond to threats is starting to change.

Traditional SOC Architecture Problems

Most enterprise SOCs evolved organically.

An organization might deploy Microsoft Defender for Endpoint, Defender for Identity, Defender for Office 365, Sentinel, third-party firewalls, network detection tools, vulnerability platforms, threat intelligence feeds, and various ticketing and orchestration systems.

Each tool solves a legitimate problem. The difficulty is what happens between them.

Security teams routinely spend time:

• Moving between portals.
• Correlating events across different products.
• Reconstructing incident timelines.
• Copying indicators between platforms.
• Writing queries to correlate otherwise disconnected datasets.
• Maintaining automation workflows.
• Tuning SIEM ingestion.
• Managing connectors and parsers.
• Determining whether multiple alerts represent one attack.
• Translating detection findings into remediation actions.

Microsoft describes this problem as the boundaries between security systems themselves becoming a limitation. As attackers increasingly use automation and AI, every integration boundary or manual handoff introduces delay for defenders.

That is an important point.

The challenge facing security teams is no longer simply detecting malicious activity. It is turning enormous quantities of security telemetry into decisions quickly enough to matter.

That is where the concept of an agentic SOC starts to become interesting.

What Is Microsoft ISOC?

Microsoft describes ISOC as bringing together XDR, SIEM, threat intelligence, automation, and AI inside Microsoft Defender.

Instead of starting with a traditional SIEM deployment and then building security operations around it, eligible organizations can begin using security operations capabilities directly within Microsoft Defender and expand the environment when additional telemetry or functionality is required. The current preview includes capabilities such as:

• Case management.
• Workbooks.
• Enhanced automation rules.
• AI-generated playbooks.
• Threat intelligence.
• User and Entity Behavior Analytics.
• Content Hub integrations.
• CI/CD-based security content deployment.
• Additional Microsoft and third-party data ingestion.

Some capabilities are available directly in Defender, while others require an ISOC workspace backed by an Azure subscription. That distinction is important.

ISOC does not mean that telemetry ingestion suddenly disappears or that organizations no longer require a SIEM-style data architecture. Microsoft is changing how those capabilities are exposed and integrated.

For organizations already using Microsoft Sentinel, Microsoft specifically states that they should continue using their existing Sentinel environment during this phase of the preview and should not disconnect a production Sentinel workspace simply to participate in the ISOC preview.

This is an evolutionary architecture, not a forklift replacement.

From Linear Workflows to a Security Feedback Loop

One of the more interesting concepts Microsoft introduced alongside ISOC is what it calls the integrated protection loop.

Traditional incident handling tends to be linear:

Detection > Alert > Investigation > Response > Remediation.

Once the incident is closed, the organization hopefully learns something from it and updates controls later. The agentic model attempts to make that process continuous.

Signals generated by endpoints, identities, workloads, applications, email systems, and third-party platforms provide awareness.

• Context turns those signals into understanding.
• Agents and analytics reason across that context.
• Actuators then translate those decisions into defensive actions.

The outcome can then improve future detection and prevention.

Microsoft describes this architecture as a stack containing sensors and signals, context, models, an agent harness, specialized agents, and actuators. Think of it as moving from:Alert ↓ Analyst ↓ Investigation ↓ Decision ↓ Response

toward something closer to:Signals ↓ Context ↓ AI + Agents ↓ Decision / Human Approval ↓ Response ↓ Improved Protection ↓ New Signals

That feedback loop may ultimately be more important than any individual AI feature.

Attack Disruption Already Shows Where This Is Going

Microsoft Defender already provides an early example of this model through automatic attack disruption.

Rather than waiting until an investigation has been completed, Defender can correlate signals and take protective action while an attack is still occurring.

Microsoft describes the system as using telemetry, exposure information, threat intelligence, and controls to detect and disrupt attacks in progress while attempting to anticipate the attacker’s next movement.

The important architectural shift is that detection and protection are no longer independent processes.

Imagine an attacker compromises a user account, steals a token, moves laterally toward another identity, and begins accessing resources.

A traditional SOC might generate several alerts. An integrated system can potentially understand those events as one attack sequence. An agentic system goes further by reasoning across the sequence and coordinating action. That could mean:

• Identifying the compromised identity.
• Mapping associated endpoints.
• Determining whether token theft occurred.
• Identifying lateral movement.
• Correlating known threat intelligence.
• Identifying exposed attack paths.
• Containing compromised resources.
• Recommending additional Conditional Access restrictions.
• Creating new detection logic.
• Updating hunting queries.
• Producing an incident summary for the analyst.

The objective is not simply better alerting. It is shortening the distance between observation and action.

Project Perception Is the Agent Layer

The second major part of this architecture is Project Perception.

Perception is Microsoft’s multi-agent security system and is currently in limited public preview. It introduces specialized security agents grouped broadly around three security functions:

• Red-team agents identify weaknesses and exposure.
• Blue-team agents investigate, triage, and detect attacks.
• Green-team agents remediate findings and improve security posture.

Microsoft describes these agents as collaborating through reusable playbooks. The output of one agent can become the input for another, allowing multiple specialized agents to cooperate on a single security objective.

For example, a threat intelligence agent could analyze new intelligence and identify indicators, techniques, vulnerabilities, and attacker behavior. That information could then feed a detection authoring agent.

Another agent could evaluate whether the organization’s environment is exposed to those techniques. A remediation-focused agent could then identify changes required to reduce the exposure.

That becomes much more interesting than simply asking Copilot:

“Summarize this incident.”

We are moving from AI assisting an analyst with individual tasks toward AI systems coordinating entire security workflows.

Agents Need Identity Too

There is another architectural detail that security architects should pay very close attention to. Agents have identities.

Microsoft Perception agents use dedicated Microsoft Entra Agent IDs. Those identities determine which resources and information the agent can access.

That means the same Zero Trust principles we apply to human identities increasingly need to be applied to autonomous software identities.

For every security agent, organizations will need to understand:

• What identity does the agent execute as?
• What permissions does it have?
• Which data can it retrieve?
• Which systems can it modify?
• Which APIs can it invoke?
• What actions require human approval?
• What actions can execute autonomously?
• How is agent activity audited?
• How quickly can the agent be disabled?

This becomes extremely important when agents have access to security controls.

An AI system that can only summarize alerts presents relatively little operational risk.

An agent that can isolate machines, change policies, disable accounts, create detection rules, modify firewall configuration, or alter identity controls is fundamentally different. The agent effectively becomes a privileged identity.

Least privilege therefore becomes just as important for agents as it is for administrators.

Microsoft’s Perception documentation specifically emphasizes configurable agent identities, permission boundaries, human approval gates, and immutable session records.

That is exactly the direction this architecture needs to go.

Human Oversight Is Still Critical

The phrase “autonomous SOC” tends to create the wrong mental model.

The goal should not be removing people from security operations.

It should be removing low-value repetitive work from people. Microsoft’s current architecture reflects that distinction.

Perception sessions allow analysts to monitor agent activity, stop sessions, approve or reject actions, and redirect agents when necessary. Microsoft also notes that agent-generated outputs can be inaccurate, incomplete, or outdated and recommends that critical results be validated before action is taken.

That is important because security investigations frequently involve uncertainty.

• A suspicious process might be malware. It might also be an administrator running an unusual script.
• A new privileged account might represent persistence. It might also be part of an approved migration.
• A large amount of downloaded data might indicate exfiltration. It might also be an authorized backup operation.

Security decisions often depend on business context that does not exist inside telemetry. AI can correlate massive datasets considerably faster than a person.

Human analysts still provide something equally important: judgment. The operating model becomes something like:

Humans define strategy, risk tolerance, and security outcomes. Agents provide scale, investigation, correlation, and execution.

Microsoft summarizes the same idea in its ISOC architecture as:

“Strategy stays human. Scale becomes autonomous.”

That is probably the best way to think about the agentic SOC.

Dynamic Threat Detection Changes Detection Engineering

Another interesting capability is Microsoft’s Dynamic Threat Detection Agent.

This agent continuously analyzes Defender and Sentinel telemetry looking for threats that traditional detection rules may have missed.

Rather than relying entirely on predefined analytics rules, Microsoft says the agent correlates alerts, events, anomalies, and threat intelligence to identify potential false negatives. When something is discovered, it can generate a dynamic alert including context, MITRE ATT&CK mappings, explanations, and remediation guidance.

This introduces an interesting change for detection engineering. Historically, detection engineering has largely involved creating logic such as:IF these events occur AND these conditions match THEN create an alert

Agentic detection can potentially operate differently:Observe the environment Understand expected behavior Correlate unusual activity Evaluate the attack context Determine whether the behavior is meaningful Generate a detection dynamically

Rules are not disappearing. Deterministic detection remains extremely valuable. But AI-driven detection introduces another layer capable of identifying combinations of activity that were never explicitly modeled in a detection rule.

That could help address one of the biggest problems in modern SOCs: false negatives caused by detection logic that never anticipated the attack pattern.

Data Quality Becomes Even More Important

There is a simple rule with AI systems:

Bad context produces bad decisions faster.

Agentic security therefore makes telemetry architecture even more important, not less.

If your Defender deployment is incomplete, your identity telemetry is missing, endpoints are unmanaged, cloud applications are disconnected, or important third-party logs are unavailable, an agent cannot magically compensate.

Its reasoning is only as good as the environment it can observe.

ISOC supports additional Microsoft and non-Microsoft telemetry through hundreds of connectors, and Microsoft states that more than 500 data connectors can be used to expand visibility beyond native Defender information.

Organizations preparing for agentic security should therefore focus heavily on foundational visibility:

• Endpoint coverage.
• Identity telemetry.
• Cloud application visibility.
• Email telemetry.
• Azure and cloud workload logging.
• Network security data.
• SaaS activity.
• Threat intelligence.
• Vulnerability and exposure information.
• Privileged identity activity.

Before asking whether AI can automate your SOC, ask whether the SOC has enough reliable data for AI to understand what is happening.

Security Operations Roles Will Change

Microsoft has already acknowledged that modern SOC teams must operate across traditional technology boundaries.

Its existing Defender XDR operational guidance recommends defining responsibilities across areas such as threat intelligence, hunting, investigation, incident response, forensics, analytics, vulnerability management, XDR, and SOAR rather than treating individual Defender products as isolated operational silos.

• Agentic security accelerates that trend.
• Tier 1 analysts may spend considerably less time manually triaging repetitive alerts.
• Detection engineers may increasingly supervise AI-generated detections rather than writing every rule themselves.
• Threat hunters may move from constructing every query manually toward directing agents to explore hypotheses.
• Security engineers may spend more time designing agent permissions, approval gates, data access, and automation boundaries.

The valuable skill becomes less about clicking through security portals and more about understanding how the entire defensive system operates. That requires deeper knowledge of:

• Identity.
• Endpoint security.
• Cloud architecture.
• Threat intelligence.
• Detection engineering.
• KQL.
• Automation.
• APIs.
• AI security.
• Agent identities.
• Zero Trust.
• Security governance.

Ironically, increased automation may make strong security architects and experienced analysts more valuable, not less.

What Organizations Should Do Now

ISOC and Project Perception are still preview technologies, so organizations should not immediately redesign production security operations around them.

However, the architectural direction is clear enough that security teams can start preparing.

First, consolidate security visibility wherever possible.

If Defender products, Sentinel, identity telemetry, cloud workloads, endpoints, and SaaS environments are operating independently, start looking at how those signals can be correlated.

Second, improve identity governance. Agent identities will become another class of workload identity that needs governance, least privilege, auditing, and lifecycle management.

Third, review automation boundaries. Determine which security actions can safely happen automatically and which should require approval.

Fourth, improve telemetry coverage. AI cannot reason about data it cannot see.

Finally, make your SOC API-driven and automation-friendly.

Security teams that rely entirely on manual portal interaction will find agentic security much harder to adopt than organizations that already understand APIs, automation, detection-as-code, infrastructure-as-code, and programmatic security operations.

The SOC Is Becoming a System, Not a Collection of Tools

For years, cybersecurity vendors have talked about creating a “single pane of glass.” That phrase never really solved the problem. Putting several dashboards into one interface does not create an integrated security architecture.

What Microsoft is attempting with ISOC is more significant. The goal is to create a shared operational foundation where telemetry, context, detection, investigation, threat intelligence, automation, response controls, and AI agents operate against the same security environment.

If that works, analysts stop being the integration layer between security products.

That might be the most important part of the entire announcement. The SOC of the agentic era will not simply have AI added to it.

It will increasingly operate as a continuous security system where machines handle the scale of observation, correlation, and repetitive execution while people retain control over priorities, risk, and consequential decisions.

• That does not eliminate the analyst.
• It changes what the analyst spends time doing.

Instead of asking:

“Which alert should I investigate next?”

The more important question becomes:

“What security outcome should the system achieve?”

That is a very different operating model. And it is probably where security operations have been heading for a long time.

References

Microsoft Security Blog, Reimagining the SOC for the agentic era in Microsoft Defender, September 23, 2026. (Microsoft)

Microsoft Learn, Integrated Security Operations Center (ISOC) in Microsoft Defender. (Microsoft Learn)

Microsoft Learn, What is Project Perception? (Microsoft Learn)

Microsoft Learn, Key concepts in Project Perception. (Microsoft Learn)

Microsoft Learn, Deploy AI agents in Microsoft Defender. (Microsoft Learn)

Microsoft Learn, Microsoft Security Copilot Dynamic Threat Detection Agent. (Microsoft Learn)

Microsoft Learn, Integrating Microsoft Defender XDR into your security operations. (Microsoft Learn)