Entra ID Governance for agent identities is not covered by Microsoft 365 E3 or E5. It requires either Microsoft 365 E7, which bundles Agent 365 and the Microsoft Entra Suite, or a standalone Microsoft Agent 365 licence paired with at least Microsoft Entra ID P1 or Microsoft 365 E3 . Agent 365 lists at $15 per user per month and Microsoft 365 E7 at $99 per user per month, both paid yearly . If you are on E3 or E5 today and you have agents in production, you have agents running without lifecycle governance, sponsorship, or access reviews, and no licence entitlement to fix that.
Most organizations discovered agents before they discovered agent licensing. Makers built in Copilot Studio, business units installed third-party agents, and IT assumed the governance story was already covered because Entra ID Governance was already paid for.
It is not. The line is hard: the governance capabilities you already own apply to human identities. Governing agent identities is a separately licensed capability set .
This is the same pattern we documented in our breakdown of Microsoft Purview Licensing Explained: E3 vs E5 vs Add-Ons. Teams designed a control model, built the policy, and then discovered halfway through deployment that the entitlement did not exist at their tier. The cost of finding out late is not the licence. It is the stalled rollout, the re-scoped programme, and the credibility hit with your security and audit stakeholders.
Entra Agent ID introduced four new object types into the directory: the agent identity blueprint, the agent identity blueprint principal, the agent identity, and the agent user . These are not service principals with better branding. They are first-class directory objects designed so an agent can be joined, moved, and retired like an employee, with a named human accountable for it throughout.
Agent identity governance is the set of Entra ID Governance capabilities applied to those objects:
The governance point is simple and uncomfortable: access should not persist longer than it is needed . Nearly every agent estate we assess fails that test today, because nobody defined who owns the agent when the builder changes roles.
If you are still mapping your agent estate before you touch licensing, start with our Your AI Agents Went Autonomous. Did Your Governance?
There are exactly two licensing paths for Entra ID Governance for agent identities :
Note what is absent from that list. Microsoft 365 E5 alone does not qualify. Entra ID Governance standalone alone does not qualify. Entra ID P2 alone does not qualify. You need Agent 365 in the mix, either standalone or via E7.
Your current positionGoverns human identitiesGoverns agent identitiesWhat you must addIndicative list priceMicrosoft 365 E3Partial (Entra P1 level)NoAgent 365$15 per user per monthMicrosoft 365 E5YesNoAgent 365$15 per user per monthEntra ID P1 standalonePartialNoAgent 365$15 per user per monthEntra ID Governance standaloneYesNoAgent 365$15 per user per monthMicrosoft 365 E7YesYes, includedNothing$99 per user per month, or $90.45 without Teams
Microsoft 365 E7 became generally available on May 1, 2026, alongside Agent 365, bundling Microsoft 365 E5, Microsoft 365 Copilot, Agent 365, and the Entra Suite into one SKU with up to 15 percent savings versus buying the components separately . We broke down the full contents of that suite in Microsoft 365 E7 (The Frontier Suite): What You Get and Why Agents Change Everything.
Technically, Agent 365 with Entra P1 or Microsoft 365 E3 satisfies the governance capability set . Commercially, that door narrowed.
Effective June 1, 2026, a licensing prerequisite applies to new Agent 365 purchases :
Customers without those prerequisites will not have key Agent 365 capabilities enabled . The capabilities at risk are not peripheral. They include advanced classification and auto-labelling of grounding data through Purview, threat protection for local and cloud agents through Defender, policy enforcement on Windows endpoints through Intune, and network and identity protection controls through Entra .
Microsoft 365 E7 is unaffected, because it already contains E5 and Agent 365 .
My read: the documented E3 path is now a technical minimum, not a commercial one. If you are an enterprise buying Agent 365 new, plan for E5 underneath it. Anyone telling you E3 plus Agent 365 is a supported enterprise landing zone in 2026 is quoting the docs and ignoring the purchase rules.
This is precisely the kind of gap a structured readiness review surfaces before procurement, not after. Our Secure Copilot Adoption in 8 Weeks: A Purview Governance Case Study shows what that sequencing looks like in practice.
Per person. Each Agent 365 licence covers an individual who manages or sponsors agents, or uses agents to perform work on their behalf .
That counting model has three practical consequences most licensing conversations miss:
1. Your licence count tracks agent consumption, not agent creation. If 400 people use an HR agent, the sponsorship model does not save you. Model your count from the population that interacts with agents, not the handful of makers who built them.
2. Sponsorship is a real job, not a checkbox. There are Lifecycle Workflows tasks built specifically to transfer agent sponsorship to a manager when a sponsor moves or leaves . If you have not named sponsors, the leaver workflow has nothing to transfer, and the agent quietly outlives its owner.
3. Visibility features have their own licence gate. Viewing an end user's agent activity and risky-agent insights requires an Agent 365 licence assigned to that user . Partial licensing produces partial observability, which is arguably worse than none because it creates a false sense of coverage.
Effective May 1, 2026, the Agent registry and Agent collections blades were retired in the Entra admin center, consolidating agent discovery, visibility, and management into Agent 365 as the single source of truth, with agent inventory visible in the All agents view in the Microsoft 365 admin center . Entra continues to provide the identity foundation through Agent ID .
The existing agent registry Graph API is also being retired and replaced by a new Agent 365-powered API, and agents registered under the current API will need re-registration . If you built any custom inventory tooling against that API, it has a shelf life.
Agent 365 CLI setup was also simplified through a managed Agent 365 CLI enterprise application, removing the need for administrators to create and maintain a tenant-owned client application. Existing customer-owned configurations continue to work, and Conditional Access and Security Defaults remain enforced .
Multi-tenant agent management is now in public preview in the Microsoft 365 admin center, giving administrators a consolidated agent inventory across managed tenants, which matters for CSP partners operating under GDAP .
For the broader shift from assistant to governed agent, see our analysis of From Assistant to Agent: The Agentic AI Shift Reshaping Microsoft 365.
I am not going to pretend this is a clean upgrade decision. Here is what actually goes wrong.
Risk 1: You discover the gap during an audit, not during planning.You already have agents. They already have access. What you do not have is a licence entitlement to review, time-bound, or attest to that access. An auditor asking "who owns this agent and when was its access last reviewed" has no good answer at E5.Mitigation: run an agent inventory now using the All agents view in the Microsoft 365 admin center , and map each agent to a named human sponsor before you buy anything. That inventory is your licence sizing input and your audit evidence.
Risk 2: You buy Agent 365 on an E3 base and lose half the capability.Data protection, threat protection, endpoint control, and identity protection for agents all depend on the prerequisite stack .Mitigation: treat the June 1, 2026 prerequisites as your actual floor. Model E5 plus Agent 365 against E7 before you decide.
Risk 3: Partial licensing creates blind spots that read as coverage.Agent activity and risky-agent insight require the licence on the individual user .Mitigation: licence by business population, not by pilot group. Define which units are in scope for agent use and licence them fully rather than sprinkling licences across departments.
Risk 4: Sponsorship is assigned once and never maintained.Movers and leavers break the accountability chain silently.Mitigation: configure the agent sponsor Lifecycle Workflows tasks as part of your existing mover and leaver templates, not as a separate project .
Risk 5: Your promotional window closes.Microsoft 365 E7 promotional offers retire on October 1, 2026, while Microsoft 365 E3 promotions were extended through December 31, 2026 .Mitigation: if E7 is on your roadmap for this fiscal year, your commercial conversation is this week, not next quarter. Confirm current offer availability with your licensing partner.
If this describes youYour realistic pathWhyE3, no agents in production, no near-term agent plansStay on E3, revisit at pilotYou are not paying for governance you cannot yet useE3, agents already appearing via Copilot Chat or third partiesReadiness assessment first, then E5 base, then Agent 365The June 2026 prerequisites make an E3-only landing zone commercially fragileE5, no Copilot, agents emergingAdd Agent 365You already meet the enterprise prerequisiteE5 with Microsoft 365 Copilot, scaling agentsEvaluate E7 seriouslyE7 adds Agent 365 and Entra Suite with up to 15 percent integrated-suite savingsAgents outnumber your governance capacity todayE7 and a governance operating model in parallelLicensing without an operating model just buys you better dashboards of the same chaos
The last row is the one I care most about. A licence does not govern anything. It grants you the ability to enforce a model you still have to design: who can create agents, in which environments, with which connectors, under whose sponsorship, reviewed on what cadence, retired under what trigger.
Shadow AI is already testing that model whether or not you have written it down. Our analysis of Shadow AI in Microsoft 365: What OpenClaw Reveals About the Agent Governance Gap covers the detection and blocking side of that problem.
For a deeper look at how autonomous agents change the governance and identity conversation, see our From Copilots to Autonomous Agents: Why Microsoft Build 2026 Redefines the Enterprise AI Playbook.
Does Microsoft 365 E5 include Entra ID Governance for agent identities?No. E5 covers governance of human identities. Agent identity governance requires Microsoft 365 E7, or Microsoft Agent 365 paired with at least Entra ID P1 or Microsoft 365 E3 .
How much does Microsoft Agent 365 cost?Agent 365 is listed at $15 per user per month, paid yearly, with an annual commitment. Microsoft 365 E7 is $99 per user per month, or $90.45 for the no-Teams variant .
Is Agent 365 licensed per agent or per user?Per user. Each Agent 365 licence covers an individual who manages or sponsors agents, or who uses agents to perform work on their behalf .
What is included in Microsoft 365 E7?Microsoft 365 E5, Microsoft 365 Copilot, Agent 365, and the Microsoft Entra Suite, generally available since May 1, 2026, with up to 15 percent savings versus buying the components separately .
Do I need Microsoft 365 E5 before I can buy Agent 365?For new enterprise purchases since June 1, 2026, yes. Frontline workers need Defender and Purview at the F5 level, and SMB customers need Microsoft 365 Business Premium. Without these, key Agent 365 capabilities are not enabled. E7 customers are unaffected .
Where do I manage agent inventory now that the Entra blades are gone?The Agent registry and Agent collections blades were retired in the Entra admin center effective May 1, 2026. Agent inventory now lives in the All agents view in the Microsoft 365 admin center, with Agent 365 as the single source of truth and Entra Agent ID providing the identity foundation .
Licensing is the easy part to fix and the expensive part to get wrong. 2toLead helps CIOs, IT leaders, and Power Platform governance teams inventory their agent estate, size the right licence mix, and stand up the sponsorship, lifecycle, and access-review model that makes the licence worth paying for.
If agents are already in your tenant and you are not sure your SKU covers governing them, Your AI Agents Went Autonomous. Did Your Governance?
Join Our Newsletter
