3.3. Secure and Govern Agents with Agent 365
💡 First Principle: Agent governance is a continuous loop — observe what agents do, protect the data they touch, assess whether they meet obligations, then adjust policy. Agent 365 doesn't replace Entra, Purview and Defender; it points each of them at agents and brings their signals together in one place.
Why care? An agent with access to sensitive data and no monitoring is the perfect insider risk: it works constantly, never asks questions and leaves only the logs you collect. Regulators are also starting to ask organizations to demonstrate control over AI systems. Agent 365 is how you answer "what is this agent doing, what data has it touched, and is it compliant?"
The licensing split is the key mental model:
| Included in base Microsoft 365 plans | Requires Microsoft 365 E7 or Agent 365 |
|---|---|
| Registry inventory | Policy templates |
| Basic governance — publish, deploy, block, delete, approve, assign users, reassign owner, pin | Observability and activity monitoring |
| Rule-based lifecycle automation | Tool control |
| Registry sync from external platforms | Entra agent controls — access packages, lifecycle policies, Conditional Access, ID Protection |
| All Purview agent features; Defender agent features |
Agent 365 licensing: licensed per user — about $15 per user per month standalone, or included in Microsoft 365 E7 (which bundles Microsoft 365 E5, Microsoft Copilot, Agent 365 and the Microsoft Entra Suite). It isn't included in E3 or E5. Agents, blueprints and agent instances don't need licenses of their own; the users who need licenses are those who delegate to on-behalf-of agents, and the owners, sponsors and managers of agents with their own access.
⚠️ Common Misconception: "Every agent needs its own Agent 365 license" is wrong. Agent 365 is licensed per user, never per agent.