Microsoft Agent 365 licensing guide. A $15 user license, and a separate meter for the agents.

Agent 365 is a $15 per user governance license, bundled only in Microsoft 365 E7, with no per agent charge. The cost that grows is the separate Copilot Credit meter autonomous agents draw on, where one nightly agent can pass $180,000 a year.

What is Microsoft Agent 365, and what does it license?

Agent 365 is Microsoft's control plane for AI agents, the place where IT inventories, secures and governs the agents working in a Microsoft 365 tenant. It became generally available on May 1, 2026, and it is licensed per user at $15 a month standalone, or inside Microsoft 365 E7 at $99.

It covers Copilot agents, custom agents built in Copilot Studio or Microsoft Foundry, third party agents from the Agent Store and platform agents. Registry sync, a paid feature in public preview at launch, also pulls in agents built on AWS Bedrock and Google Cloud.

What every tenant gets without buying a license

All Microsoft Cloud subscription customers receive a foundational tier at no extra cost. Check how much of your governance requirement it meets before you buy:

• Agent Identity. Each agent gets an identity in Microsoft Entra.
• Agent Registry. A central inventory of the agents in the tenant.
• Basic usage insights and admin actions. Enough to see which agents run and to act on them.
• Audit logs and eDiscovery. Agent activity is logged and searchable for legal holds and investigations.

What the $15 license adds

The paid tier adds advanced observability, identity governance, lifecycle management, Purview data security controls, insider risk management, Defender threat detection and conditional access for agents. This is where identity, lifecycle, sensitivity labels, DLP and data loss boundaries are enforced across every agent. Audit logging is already free, so the case for paying rests on lifecycle and data protection.

How many separate bills does a Microsoft agent program create?

A Microsoft agent program creates three bills, bought in different places. Agents working inside one person's context ride on the Microsoft 365 Copilot user license. Autonomous agents draw Copilot Credits from a tenant pool. Agent 365 adds governance per user, and buying one line covers neither of the others.

The seat lines and the credit packs sit in the M365 section of the Enterprise Agreement, and pay as you go overflow bills to an Azure subscription. Credits were called Copilot messages until September 1, 2025, when Microsoft renamed the unit and kept the pack quantity and rate unchanged.

Is there a per agent charge in Agent 365?

No. Microsoft's licensing FAQ says there are no per agent or per instance charges within Agent 365, and agents themselves are not licensed. One licensed user can sponsor any number of agents, so the cost that grows with agent volume lands on the credit meter.

The same FAQ says Agent 365 has no consumption based costs "yet". Treat the per user model as current policy that can change, and fix it in the contract for your term.

How does the Copilot Credit meter price agent activity?

Copilot Credits price each event an agent performs, at a fixed weight per event type. A scripted reply costs 1 credit, a generated answer 2 and an agent action 5. Microsoft counts triggers, reasoning steps, topic transitions and tool calls as agent actions, and grounding a response on your tenant's Microsoft Graph costs 10.

A run costs the sum of its events, and a scheduled agent repeats that sum for as long as the schedule exists. See our Copilot Studio pricing page, or apply the weights to your own volumes in the Copilot Credits cost calculator.

Which runs the Copilot user license covers

When a Microsoft 365 Copilot user runs an employee facing agent under their own identity, none of the events in the table bill. Agent flows are covered only when the "When an agent calls the flow" trigger starts them. An agent on a schedule or event trigger, with no licensed user present, bills every event.

What happens when the pool runs dry?

Packs are enforced monthly and unused credits do not roll over. At 125 percent of prepaid capacity, Microsoft disables custom agents once the current conversation ends. Attaching pay as you go keeps agents running, but overflow bills at $0.01 per credit against $0.008 inside a pack.

What does one autonomous agent cost to run for a year?

A single agent can cost six figures a year. Take a hypothetical nightly compliance agent reviewing 2,000 records, with three reasoning steps and two tool calls each. That is roughly 10,000 steps a night and about 3.6 million a year. Many forecasts stop there, five times too low, because each step is an agent action at 5 credits.

The pack line is sized for a 31 day month, which needs 1.55 million credits, exactly 62 packs. In February 150,000 of them lapse. Size to the average month and every long month spills into pay as you go or enforcement. Five agents of this shape pass $900,000 a year at pay as you go rates.

How to forecast an agent before it ships

1. Count runs per month from the trigger: the schedule, the event volume or the unlicensed users who will call it.
2. Walk one test run through the activity map in Copilot Studio and count each event type.
3. Apply the weights, including grounding and flow actions.
4. Multiply by runs and add a margin for retries and prompt changes.
5. Size packs to the longest month and name who approves overflow.

Is Agent 365 included in Microsoft 365 E5 or Copilot?

No. Only E7 includes Agent 365. Where buyers assumed the rights sat inside Copilot or E5, the correction added 10 to 25 percent of unbudgeted cost. E5, or E3 with the Defender and Purview suites, is the prerequisite for enterprise users. The E7 guide covers the full suite.

When E7 is cheaper than buying the parts

Against all four parts, E7 saves $18 a month per user. A user who needs Copilot and Agent 365 but not the Entra Suite would pay $105 for the parts, so E7 still saves $6. Without Copilot, E5 plus Agent 365 costs $75, which is $24 less than E7.

Say all 6,000 of your E5 users need Agent 365 and 1,500 of them need Copilot:

• E7 for everyone. 6,000 users at $99 cost $594,000 a month.
• Split by user group. E7 for the 1,500 and E5 plus Agent 365 for the other 4,500 cost $486,000 a month.
• Difference. $108,000 a month, or $1,296,000 a year, in favor of the split.

E7 excludes Copilot Credits, so agent execution still bills through the meter. It does include Security Copilot, as E5 does, at 400 SCUs a month per 1,000 users, up to 10,000, with more at $6 per SCU. Our Security Copilot pricing guide covers that meter.

Which users need an Agent 365 license?

Microsoft's FAQ names two groups. Users who delegate their own access to an agent that acts for them must be licensed. So must the owner, sponsor or manager of any agent that runs with its own access, such as an HR agent. Microsoft also recommends coverage for everyone who interacts with a managed agent.

Why we would not license every user on day one

The common advice is to follow that recommendation and license the whole tenant. We disagree for most enterprises in their first agent year. The required population is usually small, and the free tier already gives every agent identity, registry, audit logs and eDiscovery. License delegators and sponsors, then expand as usage shows who needs premium controls.

• Whole tenant. A hypothetical 8,000 user tenant at $15 costs $1,440,000 a year.
• Required users only. If 900 users delegate to agents and 60 sponsor them, 960 licenses cost $172,800 a year.

What have we seen in Microsoft agent licensing deals since 2024?

Buyers found the model hard to forecast. Across roughly 15 to 25 Microsoft AI agent and Agent 365 conversations I advised between 2024 and 2025, three patterns repeated:

• Pools overran. Agent consumption ran 20 to 40 percent past the prepaid pool, because the forecast used seat intuition instead of counting actions.
• Seats and pool were sized in opposite directions. Per user licenses went out broadly, while the pool was under sized because the actions on the agent roadmap were never counted.
• Governance came last. Identity and lifecycle controls were scoped after rollout on most tenants, so audit, sensitivity and data loss boundaries were retrofitted around running agents.

An agent on a timer spends credits every night, whether or not anyone reads what it produced.

Scope governance before the first autonomous agent ships

Retrofitting costs more, because licenses get bought in a hurry at list and agents holding broad permissions need rework. Price Agent 365 before production and size the pool from the roadmap.

Our Copilot true cost analysis covers idle seats and cost per active user, and the Now Assist consumption analysis shows the same forecasting failure on ServiceNow's meter.

What will the Microsoft account team say, and how should you answer?

• "E7 covers everything you need for agents." It covers seats and governance. Ask for credit pricing in the same quote.
• "License Agent 365 for every user so governance is complete." Ask which clause requires it. The FAQ requires delegators and sponsors, and the rest can follow at the same price.
• "Start on pay as you go and commit once you know usage." Fine for a pilot, if the pack price and pre purchase discount are held for the term now.
• "Your Copilot licenses already cover agent usage." Only for licensed users in Copilot Chat, Teams or SharePoint. Ask for scheduled agents to be priced separately.

What should you ask for in the Enterprise Agreement?

Put the meter under the same discipline as the seats. These are the terms we request:

• Price hold on credit packs. A fixed pack price and pay as you go rate for the term, so agent growth is not repriced at renewal.
• Pre purchase discount. Microsoft advertises up to 20 percent for upfront Copilot Credit Commit Units, so treat that as the starting point.
• Pack reduction at each anniversary. A pool you cannot shrink turns into lapsed credits when the roadmap changes.
• E7 by user group. The right to split users between E7 and E5 with separate add on licenses, and to move them at each anniversary.
• Agent 365 metric fixed for the term. The per user basis and price written in, since Microsoft has said only that there is no consumption charge yet.
• Agent 365 discount matched to E5. A new SKU should not enter at a weaker discount than the suite it depends on.

Whether pay as you go or pre purchase suits you depends on how steady your agent volume is.

How do you check what your agents actually consume?

• Power Platform admin center. Under Licensing, Copilot Studio, Environments, the Copilot credit consumption details grid lists each consuming agent by feature, including agent flow actions, with billed and nonbillable credits in separate counts. The nonbillable count shows how much use the Copilot user license absorbed.
• Copilot Studio activity map. A test run shows every trigger, reasoning step and action, which gives you credits per run.
• Agent Registry. The inventory lists agents and their owners, which gives you the sponsor count for licensing.

What to do next

1. This month. Open the Agent Registry, list every agent and name an owner or sponsor for each.
2. Before any autonomous agent ships. Forecast its runs, events and weights from a test run.
3. Before you buy Agent 365. Count the delegators and sponsors the FAQ requires.
4. Before the E7 quote. Price E7 against the parts for each user group.
5. When you size the pool. Size packs to the longest month and agree who approves overflow.
6. At the EA table. Cap credit pricing for the term and secure reduction rights. Our Microsoft practice can build the forecast with you.

Frequently asked questions