Agent 365 Pricing: What $15 per User Actually Buys

The short answer

Agent 365 is not included in E3 or E5. It is included in E7. Everywhere else it is a separate purchase.

Two numbers matter here and they are not the same number. If your users are already eligible, Agent 365 adds $15 per user per month on the licence line. If they are not eligible, you pay to become eligible first, and that is the bigger line: for an E3 estate it is at least the $21 step up to E5, or the two suites, on every user you want to cover. Agent runtime is separate again and is not included in either figure. Most of this page is about working out which of those two situations you are in.

“Standalone” means you can buy it on its own. It does not mean you can use it on its own.

Two Microsoft pages, both current, say different-sounding things.

The add-ons pricing page badges Agent 365 Standalone, next to Microsoft 365 Copilot which is badged Add-on, eligible Microsoft 365 subscription required.

The Agent 365 licensing FAQ sets out prerequisites, and they differ by customer class. For an enterprise customer you need Microsoft 365 E5, or Microsoft 365 E3 (or Office 365 E3 plus EMS E3) plus both the Defender Suite and the Purview Suite. Frontline needs F1/F3 plus the Defender and Purview Suite FLW. Education needs A5 for Faculty, or A3 for Faculty plus the two Education suites. Small and medium business needs Business Premium, and Microsoft notes that the SMB Defender and Purview suites unlock the functionality but are not formal prerequisites.

Both statements are true. The badge describes how you buy it. The FAQ describes what has to already be in your tenant for the thing to function, because Agent 365 is largely an orchestration layer over Entra, Purview, Defender and Intune. It does not carry those capabilities, it lights them up for agents.

The useful version for a budget conversation: $15 is the sticker, and the sticker is not the cost of entry. If you are an E3 estate, the real question is not $15, it is what E5 or the two suites cost you.

One thing the badge does get right, and it surprises people: neither product is a licensing prerequisite for the other. Agent 365 does not require a Microsoft 365 Copilot licence, and Copilot does not require Agent 365. Plenty of teams assume the governance layer is gated behind the AI product; it is not. Be clear about what that does and does not mean. It is a statement about entitlement, not about coverage: Microsoft's own FAQ answers “do we still need Agent 365 if we already have Copilot” with a flat yes, on the argument that Copilot governs Copilot while agents run well beyond it. That is Microsoft's commercial position and you can weigh it yourself, but it is not a licence gate in either direction.

The part that actually catches people out is the other half: buying Copilot does not satisfy Agent 365's prerequisites. An E3 estate that bought Copilot is no closer to being eligible than it was before.

The mixed-estate trap

The FAQ works a scenario that will land badly in a lot of organisations. Take 5,000 E3 users who also have Copilot, 1,000 E5 users, and 2,500 frontline users with the Defender and Purview FLW suites.

You can license Agent 365 for the 1,000 E5 users and the 2,500 frontline users. The 5,000 E3 plus Copilot users are not eligible, because E3 with Copilot but without the two suites does not meet the prerequisite.

Read that again if you run an E3 estate that bought Copilot. The population most likely to be deploying agents is the population that cannot govern them under this SKU without another purchase first.

Microsoft also notes that signed contracts are not affected by the prerequisite change and stay valid until renewal. So this is a renewal-cycle problem, which is the cycle you can actually plan for.

The eligible combinations, for reference

Straight from the FAQ, these are the permitted paths. Find yours, or find the gap:

1. Microsoft 365 E7
2. Microsoft 365 E5 / A5 / Business Premium + Agent 365
3. Microsoft 365 + Defender Suite + Purview Suite + Agent 365
4. Office 365 E3 + EMS E3 + Defender Suite + Purview Suite + Agent 365
5. Microsoft 365 + Defender Suite Edu + Purview Suite Edu + Agent 365
6. Office 365 A3 + EMS A3 + Defender Suite Edu + Purview Suite Edu + Agent 365
7. M365 F1/F3 + Defender and Purview Suite FLW + Agent 365
8. Office 365 F3 + EMS E3 (K) + Defender and Purview Suite FLW + Agent 365

If your estate is not on that list, you are not eligible yet.

You are licensing people, not agents

This is the part that saves money, and it is counterintuitive enough that it is worth being precise.

Agent 365 is licensed per user. Agents do not get their own licences. Blueprints, agents and agent instances are explicitly not licensing units, and there are no per-agent or per-instance charges. One licensed user can create, sponsor and manage many agents: asked whether a single licensed sponsor can run a fleet, the FAQ answers yes, “including at fleet scale”. It does not state a cap, which is not the same as stating there is none, so do not plan on an unlimited entitlement without it in your agreement.

Who has to be licensed, and this qualifier does most of the work: a licence is required only for users who interact with, manage or sponsor agents that use Agent 365 premium capabilities. Within that scope it catches any user who delegates their access to an agent (on-behalf-of agents), and the owner, sponsor or manager of an agent that runs with its own access. Microsoft separately recommends broad coverage, including all Copilot users, as adoption scales. Recommended is not required, and the two should not be conflated in a quote.

So a fleet of forty back-office agents sponsored by one platform owner is one licensed user, not forty licences, provided no other user falls inside the rules above. A single agent using premium capabilities that a thousand employees each invoke on their own behalf is a thousand licences. An agent that touches nothing premium is not what this SKU is counting.

Two constraints stop this becoming a loophole. Enforcement is contractual, not technical: if an agent is tied to an unlicensed user, the activity is simply not entitled, and Microsoft calls that an out-of-compliance scenario. And multiplexing, pooling access to cut licence counts, is not permitted.

Microsoft says this outright, and it tells you how mature the counting is:

“Microsoft recognizes that this guidance can be difficult to operationalize today, as there is limited visibility into user-level agent interactions during policy configuration.”

Translation: they are asking you to license a population that their tooling cannot yet show you. Budget with a margin, and write down your counting assumptions, because you will be asked to defend them.

What you get without paying for Agent 365

Some of this is free with any Microsoft 365 subscription, and a surprising amount of governance sits in that free tier. Per the service description, four of its twenty-six capabilities are included with Microsoft 365 Enterprise, Business, Education and Frontline Worker plans:

• Inventory of every agent in the Agent Registry
• Basic governance actions: publish, deploy, block, delete, approve, assign to users or groups, reassign owner, pin
• Automated agent lifecycle actions using conditions-based rules (disputed: the licensing FAQ puts this in the paid list)
• Synchronising agents and agent metadata into the registry from external platforms not managed by Agent 365 (disputed: the FAQ puts registry sync in the paid list, and the roadmap has not shipped it)

Take the first two to the bank and treat the last two as unsettled, for reasons set out below. Even so, that is a real starting point: you can see your agents and you can kill one. If your immediate problem is “we do not know what is running”, you may not need to buy anything this quarter.

The FAQ also lists three things as free that the service description does not mention in its included column at all: agent audit logs and eDiscovery, blocking unsanctioned local endpoint agents, and discovery of AI on endpoints. Free on one page, absent or paid on another. Do not build a business case on any single one of these four rows.

What the $15 actually adds

Everything else in the matrix. Of the 26 capabilities in the service description, 4 are included and 22 require E7, G7 or Agent 365:

• Observability: agent map, advanced usage insights, registry sync, Graph API access
• Governance: policy templates, tool controls including which MCP servers agents may reach, agent identity governance, Entra access packages and lifecycle policies
• Security: conditional access and identity protection for agents, Defender posture management, threat detection and blocking of tool invocations, threat hunting, shadow AI sync
• Data: Purview DLP for agents, sensitivity label inheritance, data lifecycle management, insider risk, DSPM with AI observability, communication compliance
• Endpoint: Intune device compliance for agent conditional access, policy-controlled runtime, blocking unsanctioned local agents

The pattern is clean. Free tier answers “what agents exist and can I stop one”. The licence answers “what are they doing, what may they touch, and can I prove it to an auditor”.

Two caveats, and in both cases it is Microsoft's sources disagreeing with each other, not with me.

Agent audit logs and eDiscovery. The service description puts them behind the licence. The licensing FAQ lists them in both the free list and the licensed list. Two first-party pages published within a fortnight of each other, contradicting each other on whether agent audit logging costs money.

Registry sync, and lifecycle automation with it. The service description puts both in the free tier, including “Synchronize agents and agent metadata from external platforms that aren't managed by Agent 365 into the registry”. The FAQ lists registry sync and “automate agent lifecycle actions” as capabilities the licence buys. The Microsoft 365 Roadmap still shows Registry sync as “In development”, two months past its stated July 2026 date. So the same capability is described as free, as paid, and as not yet shipped, depending on which Microsoft page you open. It is possible these pages are describing different scopes of the same feature rather than flatly contradicting each other, but Microsoft does not say so anywhere, and you cannot budget against an ambiguity.

If either one sits on your critical path, get the answer in writing from your licensing desk before you plan around it. One Microsoft page is not enough here.

The meter is next door

Agent 365 itself has no consumption charge. The FAQ is direct: “There are no consumption-based costs for Agent 365 yet.” Keep the “yet”.

The consumption sits in the product beside it. Windows 365 for Agents is not included in Agent 365 and is not bundled with Copilot Studio. It is a separate purchase, billed pay-as-you-go on hourly usage, and Microsoft positions it as what you add when agents need a full desktop or browser runtime to complete tasks.

Microsoft has not published an hourly rate for it. The licensing FAQ describes the billing model and stops there, and the product is still in US-only public preview. If you see a per-VM-hour figure quoted anywhere, including in vendor decks, ask where it came from. Carry this as a line with no number against it, which is uncomfortable but honest, and get the rate from your licensing desk before you commit to a desktop-runtime design.

So the shape of an agent bill is a per-user governance licence, plus whatever runtime and model consumption the agents generate elsewhere. A per-user price on the governance layer does not make the agent estate a fixed cost. The consumption side is covered in the credits and capacity packs guide.

Is E7 worth it

At list, on the per-user arithmetic: E5 + Copilot + Agent 365 = $60 + $30 + $15 = $105. E7 = $99, and it also includes Entra Suite.

E7 wins by $6 per user per month against that stack, before counting Entra Suite. That $6 only exists if you were buying Copilot anyway. If you are not, the comparison reverses: E5 + Agent 365 is $75, and E7's extra $24 buys Copilot and Entra Suite whether you wanted them or not.

And E7 does not remove the prerequisite problem. It prepays it. E7 contains E5, so eligibility comes in the box, which means part of what looks like a bundle discount is you buying an entry ticket you needed regardless. Whether $99 is worth it depends on how much of that bundle you would have bought separately, and that is arithmetic only your estate can settle.

Public sector should read the GCC column first

Of the 26 capabilities in the service description, 14 are marked not available in GCC, including most of the Purview block (audit and eDiscovery, data lifecycle management, insider risk, DLP, DSPM), most of Defender (shadow AI sync, misconfiguration remediation, suspicious activity detection), the Graph API, and the Intune runtime controls.

Twelve are available at GA. If you are buying Agent 365 in a government cloud specifically for the compliance story, check that column line by line before you sign.

What is announced but not yet shipped

Checked against the Microsoft 365 Roadmap on 25 September 2026. Six Agent 365 entries exist. One is launched: the control plane itself, GA May 2026. The other five all sit at “In development”, and four of those are already past their stated availability month. The fifth is not due until October, so it is listed here for planning rather than as a slip:

Registry sync is the one to watch. It is the same item flagged earlier as free on one Microsoft page and paid on another, and the roadmap adds a third answer: not shipped. Roadmap dates are month-granular and they move. Treat anything not marked Launched as a plan, not a feature.

How to count what you owe

Microsoft points at two reports, both in the Microsoft 365 admin centre, both requiring no Agent 365 licence to run:

1. Active users using agents in Microsoft 365 Copilot (Reports > Usage > Microsoft 365 Copilot > Agents). Unique users using agents in the last 30 days. Exportable.
2. Registry agent owners (Agents > All agents). Owners of every agent in the registry, including third-party agents brought in through the SDK, the Marketplace or registry sync, and all Microsoft first-party agents. Exportable.

You need both, because they point at different populations: report 1 at the delegators, report 2 at the sponsors. Neither is a billable-seat count, and do not present them as one. Report 1 sees only agents inside Microsoft 365 Copilot, only over 30 days, and Microsoft has already told you its user-level visibility is limited.

So treat the two exports as a starting inventory rather than an answer. Combine them, deduplicate the overlap, map each name against the licensing definitions above, and write down the populations you could not see. Take that to procurement with the assumptions attached, because the gaps are where the compliance argument will happen.

The short version

$15 per user per month buys the observability, governance and security layer over agents, for the users who delegate to or sponsor agents that use its premium capabilities, on top of an estate that already meets the prerequisite for its class: for an enterprise, E5 or E3 with the Defender and Purview suites. It does not buy runtime. It does not charge per agent. It is not enforced by the product, it is enforced by your contract. And a meaningful amount of basic agent governance is already included in what you pay today.

Start by running the two reports. You cannot price this until you know how many people in your organisation are quietly sponsoring an agent.

For the wider agent cost model including credits, capacity packs and a worked 500-seat estimate, see the agent cost and pricing reference. For who needs which licence when an agent serves a given audience, see Copilot agents licensing.