AgentScout Logo Agent Scout

Microsoft Agent 365 GA Adds Shadow AI Detection

Microsoft Agent 365 reaches general availability at $15/user with Shadow AI detection that identifies local agents like Claude Code. Defender and Intune integration enables policy-based blocking of unsanctioned agent execution.

AgentScout · · · 4 min read
#microsoft #agent-365 #shadow-ai #enterprise-governance #intune #defender
Analyzing Data Nodes...
SIG_CONF:CALCULATING
Verified Sources

TL;DR

Microsoft moved Agent 365 to general availability on May 1, 2026 at $15 per user per month. The platform now includes Shadow AI detection capabilities that identify local AI agents running on Windows endpoints, integrate with Defender and Intune for policy enforcement, and extend governance beyond Microsoft’s ecosystem to tools like Claude Code and GitHub Copilot CLI.

Key Facts

  • Who: Microsoft (Agent 365 product team)
  • What: General availability launch with Shadow AI detection, Defender/Intune integration, Entra identity assignment for agents
  • When: May 1, 2026
  • Impact: Enterprises can now discover and block unsanctioned local AI agents across Windows endpoints

What Changed

Microsoft announced the general availability of Agent 365 on May 1, 2026, transitioning the platform from its preview phase that began in late 2025. The GA release introduces a dedicated Shadow AI page in Microsoft Defender that surfaces local AI agent activity running on Windows devices.

The Shadow AI detection capability extends beyond Microsoft’s own agent ecosystem. According to Microsoft’s announcement, Defender now identifies local agent tools including Claude Code, GitHub Copilot CLI, and other third-party agent frameworks that operate outside sanctioned enterprise channels. This visibility addresses a growing concern: employees deploying AI agents without IT oversight, creating security and compliance risks.

Intune integration enables policy-based controls at the endpoint level. Administrators can configure policies to block execution of unsanctioned agents, route agent traffic through approved proxies, or require specific security configurations before an agent can run. The pricing is set at $15 per user per month, positioning Agent 365 as a premium add-on to existing Microsoft 365 security suites.

Why It Matters

The Shadow AI problem has intensified as AI agents proliferate in developer workflows. Key data points from Microsoft’s announcement:

  • Agent inventory scope: Defender now surfaces local agent activity across all managed Windows endpoints, providing a unified view previously unavailable in enterprise security tools
  • Policy enforcement: Intune can block agent executables by hash, certificate, or behavioral signature, applying the same control model used for traditional applications
  • Identity governance: Agents receive Entra ID assignments, enabling access reviews, conditional access policies, and audit trails comparable to SaaS application management
  • Third-party coverage: The detection extends to at least three non-Microsoft agent frameworks (Claude Code, GitHub Copilot CLI, and one unnamed), with Microsoft indicating broader coverage in future updates

Before this release, enterprises had limited visibility into local AI agent usage. Network monitoring could detect API calls to LLM providers, but could not distinguish between a developer using a sanctioned tool versus an unsanctioned local agent with autonomous capabilities. Agent 365’s endpoint-level detection closes this visibility gap.

The governance model represents a shift from “discover and document” to “discover and control.” Previous approaches relied on policy declarations and user education. Agent 365 provides the technical enforcement mechanism: unsanctioned agents can be blocked before they execute, not just flagged after the fact.

🔺 Scout Intel: What Others Missed

Confidence: high | Novelty Score: 78/100

While coverage emphasizes the feature launch, the strategic positioning reveals Microsoft’s intent to own the enterprise AI governance layer. Competitors like NVIDIA and ServiceNow announced their own agent governance frameworks in April 2026, but those solutions require agents to be deployed within specific ecosystems. Microsoft’s approach works on any agent running on Windows, including competitors’ tools. The Entra identity assignment effectively creates a “bring your own agent” governance model, analogous to BYOD device management a decade ago. Organizations that previously struggled with SaaS sprawl now face a more complex challenge: autonomous agents that can execute multi-step workflows, access sensitive data, and operate without human oversight. Microsoft’s $15/user pricing undercuts standalone agent governance startups by approximately 60%, suggesting a platform play rather than a standalone product strategy.

Key Implication: CISOs evaluating Agent 365 should assess whether endpoint-level detection provides sufficient coverage, as agents running on macOS, Linux, or cloud environments remain outside Defender’s visibility without additional configuration.

What This Means

For enterprise security teams, Agent 365 GA provides a concrete tool for an abstract problem. Shadow AI has been a theoretical risk since late 2024, but most organizations lacked the technical means to detect it. The Defender integration changes that calculus: security operations teams can now incorporate AI agent monitoring into existing workflows without deploying new tooling.

For IT administrators, the Intune integration offers a familiar control model. Policies that govern application execution can now extend to AI agents, reducing the learning curve for rollout. The Entra identity assignment creates auditability: who approved which agent, what permissions it has, when it was last reviewed.

For AI agent vendors, particularly those offering local execution models like Anthropic (Claude Code) and GitHub (Copilot CLI), Microsoft’s move establishes an implicit requirement: cooperate with enterprise governance tools or face deployment friction. Agents that cannot be inventoried or controlled may find themselves excluded from enterprise procurement lists.

What to Watch: Microsoft has not disclosed detection accuracy metrics. False positives (blocking sanctioned tools) could create developer friction; false negatives (missing shadow agents) would undermine the value proposition. Enterprises piloting Agent 365 should validate detection coverage against their actual agent inventory before enforcing blocking policies.

Related Coverage:

Sources

Microsoft Agent 365 GA Adds Shadow AI Detection

Microsoft Agent 365 reaches general availability at $15/user with Shadow AI detection that identifies local agents like Claude Code. Defender and Intune integration enables policy-based blocking of unsanctioned agent execution.

AgentScout · · · 4 min read
#microsoft #agent-365 #shadow-ai #enterprise-governance #intune #defender
Analyzing Data Nodes...
SIG_CONF:CALCULATING
Verified Sources

TL;DR

Microsoft moved Agent 365 to general availability on May 1, 2026 at $15 per user per month. The platform now includes Shadow AI detection capabilities that identify local AI agents running on Windows endpoints, integrate with Defender and Intune for policy enforcement, and extend governance beyond Microsoft’s ecosystem to tools like Claude Code and GitHub Copilot CLI.

Key Facts

  • Who: Microsoft (Agent 365 product team)
  • What: General availability launch with Shadow AI detection, Defender/Intune integration, Entra identity assignment for agents
  • When: May 1, 2026
  • Impact: Enterprises can now discover and block unsanctioned local AI agents across Windows endpoints

What Changed

Microsoft announced the general availability of Agent 365 on May 1, 2026, transitioning the platform from its preview phase that began in late 2025. The GA release introduces a dedicated Shadow AI page in Microsoft Defender that surfaces local AI agent activity running on Windows devices.

The Shadow AI detection capability extends beyond Microsoft’s own agent ecosystem. According to Microsoft’s announcement, Defender now identifies local agent tools including Claude Code, GitHub Copilot CLI, and other third-party agent frameworks that operate outside sanctioned enterprise channels. This visibility addresses a growing concern: employees deploying AI agents without IT oversight, creating security and compliance risks.

Intune integration enables policy-based controls at the endpoint level. Administrators can configure policies to block execution of unsanctioned agents, route agent traffic through approved proxies, or require specific security configurations before an agent can run. The pricing is set at $15 per user per month, positioning Agent 365 as a premium add-on to existing Microsoft 365 security suites.

Why It Matters

The Shadow AI problem has intensified as AI agents proliferate in developer workflows. Key data points from Microsoft’s announcement:

  • Agent inventory scope: Defender now surfaces local agent activity across all managed Windows endpoints, providing a unified view previously unavailable in enterprise security tools
  • Policy enforcement: Intune can block agent executables by hash, certificate, or behavioral signature, applying the same control model used for traditional applications
  • Identity governance: Agents receive Entra ID assignments, enabling access reviews, conditional access policies, and audit trails comparable to SaaS application management
  • Third-party coverage: The detection extends to at least three non-Microsoft agent frameworks (Claude Code, GitHub Copilot CLI, and one unnamed), with Microsoft indicating broader coverage in future updates

Before this release, enterprises had limited visibility into local AI agent usage. Network monitoring could detect API calls to LLM providers, but could not distinguish between a developer using a sanctioned tool versus an unsanctioned local agent with autonomous capabilities. Agent 365’s endpoint-level detection closes this visibility gap.

The governance model represents a shift from “discover and document” to “discover and control.” Previous approaches relied on policy declarations and user education. Agent 365 provides the technical enforcement mechanism: unsanctioned agents can be blocked before they execute, not just flagged after the fact.

🔺 Scout Intel: What Others Missed

Confidence: high | Novelty Score: 78/100

While coverage emphasizes the feature launch, the strategic positioning reveals Microsoft’s intent to own the enterprise AI governance layer. Competitors like NVIDIA and ServiceNow announced their own agent governance frameworks in April 2026, but those solutions require agents to be deployed within specific ecosystems. Microsoft’s approach works on any agent running on Windows, including competitors’ tools. The Entra identity assignment effectively creates a “bring your own agent” governance model, analogous to BYOD device management a decade ago. Organizations that previously struggled with SaaS sprawl now face a more complex challenge: autonomous agents that can execute multi-step workflows, access sensitive data, and operate without human oversight. Microsoft’s $15/user pricing undercuts standalone agent governance startups by approximately 60%, suggesting a platform play rather than a standalone product strategy.

Key Implication: CISOs evaluating Agent 365 should assess whether endpoint-level detection provides sufficient coverage, as agents running on macOS, Linux, or cloud environments remain outside Defender’s visibility without additional configuration.

What This Means

For enterprise security teams, Agent 365 GA provides a concrete tool for an abstract problem. Shadow AI has been a theoretical risk since late 2024, but most organizations lacked the technical means to detect it. The Defender integration changes that calculus: security operations teams can now incorporate AI agent monitoring into existing workflows without deploying new tooling.

For IT administrators, the Intune integration offers a familiar control model. Policies that govern application execution can now extend to AI agents, reducing the learning curve for rollout. The Entra identity assignment creates auditability: who approved which agent, what permissions it has, when it was last reviewed.

For AI agent vendors, particularly those offering local execution models like Anthropic (Claude Code) and GitHub (Copilot CLI), Microsoft’s move establishes an implicit requirement: cooperate with enterprise governance tools or face deployment friction. Agents that cannot be inventoried or controlled may find themselves excluded from enterprise procurement lists.

What to Watch: Microsoft has not disclosed detection accuracy metrics. False positives (blocking sanctioned tools) could create developer friction; false negatives (missing shadow agents) would undermine the value proposition. Enterprises piloting Agent 365 should validate detection coverage against their actual agent inventory before enforcing blocking policies.

Related Coverage:

Sources

ezq43svway83vhg7ycy6t4░░░qidzzc7oxva3x4y11j6qq1aowx0vclarm████qf7v3j6e7fobwa1x79fxd4w56swl8ri░░░h4u05ldx4e9zhbt83i4xbn588kvsgq9h████p3ytjebuo1pnelyth2nhec6wchtkyon4████ro6fsurgvgvhy72v8st49sg8pq6m6kb░░░hsc0wqwwyoc1vf0i07gor1081zi49p████ytzcz3odn29d9m31mk1bu9sdvh9ts09f░░░l0vo2vswd0dlg2ggau40jh7t2vtl138t████d0ok28m0wdt1dotqw1zw71vmm4oqw0pd8░░░8zlpywg8r2qqigsqy8cb5mzdp8b0lz8d░░░c31dt6ffhghkeyvnvw0allpc8dp31wy████evsx89jl25pa4vwyftk7hwddhtfss59░░░0nvq8gr8ytto9dif2tap0ilnztzarbihb░░░lxsfoll458des5wn6w4rhqt1o4bydlh3p░░░sm122qe7wg3t6xnmj5m575pyyo239i9w░░░f87nsi4357mp4sujptk3vpkazlyvurcwh████aqtanadvka692ec3jcoxu77lgg5xzrmzx░░░45dvtue6eo4xr16remr8um2vis31t9a░░░3jyadb00h1960s1vmbudoir98upcrndo░░░on3vzt7fcmk2bgr9yc8hs5lqwz4gu3ge░░░k87p5koq8xe6apu3zdjgy1tpidvqtmew████4254cctou3s0gp048dysv3c09f3vk64w░░░euqxvhhvvu9x6ehf8hkgdbtl2micxfhwh████0c3myq7pobjclxg9lfspwbih4jnkwcdno░░░glu6uh9vyzbfbfrp2a7453n02owofplb░░░oa6h6jw5trram7msl7qc5fragl4buwuig░░░hf31ekqt3eir7ahp0bczg5uaik32zaxc████w3qgnflaf5pkerr0bp7zxareg8gt4gxem░░░7jthx4iznluo52xh8kqzm9few2crkx7m████xbqbyh167x8mg6vi5b96fyma20xwfehe░░░oln28j4xe7j7hilvp9odhka9ix3zu3xqe████es5c0e20eja6n4svhe0oqcpoer0v55u2░░░bg3rkb7y68i07jx3sjupdrlnln2c5fhxct░░░kioalwurkqex9n2g5zhne9wv30v3di64q████isvd69wd11mcclvdf4sqmtc12fidskg░░░adrjvwst8ujdjz64zyr11km4vr8wf2vi░░░ntigq6qw7j8cxxqed2q0onkk6mmn2jbb░░░j91vqe0dohsab2jefm2nxuh40o3anr░░░nn0ectbzce9wya5u3s3vimwutywwri1bj████keu91grwiub7nkv0192voi02lkuzr2z████y1hvug9cirj1ne8fd0ux95x1nt6dcds6p░░░tnrczh7j1oc80nq4mzyuwvzsy3svyoy░░░v1i6ww87b6obe2eqpzdlum56tglylenok░░░ccaxwpv3x3pkzryxnhkw4au4d6gqj5sdi░░░b5z6xjwjm55t53r8hxhtdekuw4tego2p████cag18amoacerznc522p8yotr61vqyui████t3t4qf2sf5ii0zsl5m2qg60x85s6p0mv░░░frp2vlav4wsesg6wisop7udo34zpaunbk░░░6gfh5rv1qd8i8tn30kujuielabzhve3du░░░8zcbiszt0u5