How to Master Agent 365: The Governance Layer for AI Agents

Most enterprises now have AI agents scattered across Copilot Studio, Foundry, AWS Bedrock, and Gemini - and nobody knows who built what, what data they touch, or when one goes rogue. Shadow agents bypass IT entirely. Agent 365, generally available since May 2026, is the control plane that pulls every agent into one registry and governs them with the Entra, Defender, and Purview stack you already run for people. Think of it as the Microsoft 365 admin centre, but for AI agents.

Want the hi-res version? It's free in the Powercademy Success Kit.

Why is Agent 365 significant?

Three shifts, each bigger than it sounds.

• Every agent gets an Entra Agent ID - agents stop being apps acting on a user's behalf and become first-class identities with their own permissions, lifecycle, and Conditional Access. Identity is the new perimeter for AI.

• Agent 365 wins even if you skip Copilot - Microsoft already runs your identity and security, and Agent 365 extends those controls to agents from any vendor, giving you flexibility inside the estate you already pay for. And shadow AI just became visible - approved or not, custom or third-party, every agent in the tenant shows up in the registry. The audit trail starts existing whether IT registered the agents or not.

How production-ready is each capability?

Agent Registry - the most mature piece: the complete inventory of every agent in your tenant, in the Microsoft 365 admin centre under Agents → All Agents. Viewing needs no licence (just the AI Reader role); applying governance policies needs Entra Agent ID licensing.

Defender + Purview protection - GA and built on mature security stacks: threat detection, DLP, and information protection extended to agents, with agent insights surfacing directly in each product's portal.

Conditional Access for agents - GA for delegated-access agents; still public preview for own-identity agents (the AI-teammate kind). An important nuance when you plan enforcement.

Agent Map - visual exploration of the registry with filters for status, publisher, platform, and data source. Usage and observability filters currently only work for tenants under 4,000 agents.

Cross-cloud registry sync - pulls agents from AWS Bedrock and Google Vertex AI into the registry. Preview, manual sync, explicitly flagged not-for-production - promising, not yet load-bearing.

How do you set it up?

1. Activate Agent 365 from the M365 admin centre: sign in as Global Admin, go to Agents → Overview, accept the Terms of Service. No data flows until you do; Foundry resources need a separate per-resource opt-in.

2. Licence for the controls you want: Entra P1/P2 or Suite plus Purview DLP aren't strict prerequisites, but they unlock Conditional Access for agents, Defender threat protection, and DLP on agent data flows.

3. Get agents registered: Copilot Studio, Foundry, and Agent Builder auto-register; Bedrock and Vertex AI use Registry Sync (preview); custom agents register via the Agent 365 SDK and CLI.

4. Apply governance: Conditional Access on agent identities or blueprints, approve activation requests, assign owners to ownerless agents, and group high-risk agents for tighter controls.

FAQ

The hi-res version of this guide is in the Powercademy Success Kit - free, along with hundreds of other cheat sheets, roadmaps, and guides for Microsoft professionals.