Microsoft Pushes AI Agents Into Security Operations With ISOC, Unifying SIEM and XDR

Microsoft announced on Sept. 23, 2026, the public preview of an Integrated Security Operations Center, or ISOC, in Microsoft Defender. It brings SIEM together with Defender’s existing XDR, threat intelligence and automation tools in a single portal.

“Security cannot operate at the speed of AI when protection and operations are built as separate systems,” said Rob Lefferts, Microsoft’s corporate vice president of Threat Protection.

The ISOC architecture is built on Microsoft’s Project Perception, announced in July 2026, and its first in-house security model, MAI-Cyber-1-Flash. Human approval is still required when an AI agent takes high-risk actions.

Microsoft 365 E5 and E7 customers can run SIEM in Microsoft Defender without additional licensing costs, and Microsoft waives data-ingestion fees for logs from its own security products. Native Microsoft log data included in ISOC is retained for 30 days during the public preview, rising from 30 to 90 days on Nov. 15, 2026.

Organizations connecting external sources must create an ISOC workspace linked to an Azure subscription; the workspace offers more than 500 data connectors. Data ingested from third-party security tools and other external sources will be billed on a pay-as-you-go basis at $2.40 per GB, effective Oct. 1, 2026.

The current ISOC public preview excludes organizations with active Microsoft Sentinel workspaces. Eligible existing customers can choose to migrate to ISOC starting Nov. 15, 2026.

Yih Khai Wong, senior research manager at IDC, said integrating Sentinel into E5 and E7 enables free native ingestion, but concentrating with a single vendor increases reliance on its roadmap and pricing, while agents themselves expand the attack surface.

Sanchit Vir Gogia, chief analyst at Greyhound Research, advised enterprises to reproduce their highest-value cross-vendor detections before replacing a mature SIEM with ISOC. He warned that granting agents permission to change identities, endpoints or cloud policies creates a potential blast radius.