05 September 2026

Microsoft Agent 365: observe, govern, secure

Agent 365 is the control plane for enterprise agents — registry, identity, Purview, and Defender. Wave 0 for the agent estate.

microsoftagent-365agentssecuritygrc

DIGITAL SKILL WORKS LTD / 12 PANES

Microsoft Agent 365 is the control plane for AI agents across the estate. Learn frames it as observe, govern, and secure — extending Entra, Purview, and Defender to agents. If Copilot Agents are how work gets done, Agent 365 is how you stay accountable.

What it is

Learn describes Microsoft Agent 365 as a Microsoft 365 service that provides a centralised control plane to discover, manage, govern, and secure agents — Microsoft-built and third-party. As of 1 May 2026, Learn states Agent 365 is generally available for the Commercial segment on a per-user basis. It works best with Microsoft E5 as a prerequisite; at least one qualifying Agent 365 licence is required to enable it. It is also included with Microsoft 365 E7 per service description notes on Learn.

Frontier still hosts some early Agent 365 capabilities (for example agents with their own identity) under preview terms — keep GA and Frontier distinct in communications.

What it does

Observe. Central registry and agent map for adoption, activity, and health. Role-specific views for security and business leaders.

Govern. Lifecycle management, access control, and compliance via Agent 365 registry in Microsoft 365 admin centre, Microsoft Entra, and Microsoft Purview. Owner and sponsor patterns for agent identities.

Secure. Risk-based access with Entra; information protection, DLP, and risk signals with Purview; threat detection with Defender. Aims to keep agents on authorised resources and reduce leakage and misuse.

Admin overview surfaces pending approvals, ownerless agents, and usage trends. Partner agents can deploy from admin centre where offered. SDKs and CLI support builders under documented packages.

Why you should care

Board. Agent sprawl is an enterprise risk theme. Ask for registry coverage percentage and ownerless-agent count.

CISO. Agent identities and tool misuse are first-class threats. Use the same muscle as identity governance.

CFO. Per-user licensing and E5/E7 prerequisites affect the cost stack. Tie spend to governed agents that show value.

Adoption. Governance that enables safe use beats blanket bans that drive shadow agents.

How it maps to 12 Panes

  • Pane 03 Horizon: GA vs Frontier feature split.
  • Pane 04 Security: Entra, Defender, least privilege.
  • Pane 05 GRC: registry, evidence, DPIAs.
  • Pane 06 Cost & Value: licence and value of agent estate.
  • Pane 09 Work & Skills: human–agent task split.
  • Pane 12 Frontier: identity-bearing preview agents only in labs.

Suggested actions

  1. Enable Agent overview and inventory; assign owners to every shared agent.
  2. Close ownerless and risky agents before new maker campaigns.
  3. Align Purview DSPM for AI and DLP locations with agent channels.
  4. Separate Frontier agent-identity pilots from GA control-plane rollout in the plan.
  5. Feed registry metrics into Counsel (Guardian + Steward) monthly.

Communication needed

Security and GRC lead. FinOps on licence prerequisites. Adoption on what staff may install. Comms: one definition of “agent” for board and staff.

Benefits and risks

Benefits. Single pane for agent inventory. Familiar Microsoft security stack extended to agents. Clearer audit story.

Risks. Licence complexity. False comfort if inventory is incomplete. Frontier features mistaken for GA controls.

Sources

Back to blog