Skip to main content
Industry Insights6 min read·Verified Jul 6, 2026 against Microsoft Learn licensing docs

Copilot Agents Licensing: Who Needs Which License

Agent licensing questions sound complicated until you ask the only question that matters: who is using the agent? There are four possible answers, and each one has a different bill.

MK
Mathieu Kessler
Founder, Kesslernity

The four audiences

1. Employee with a Microsoft 365 Copilot seat
Covered by the seat

When the agent is employee-facing and runs under the authenticated licensed user’s identity, the credit charges (classic answers, generative answers, actions, graph grounding, flows, AI tools) are included in the Microsoft 365 Copilot license, subject to fair-use limits Microsoft reserves the right to adjust. This is the single biggest lever in agent economics: the same agent is free for this audience and metered for everyone else.

2. Employee without a Copilot seat
Bills in Copilot Credits

Copilot Chat itself is available to Microsoft 365 commercial users at no extra cost, but agent usage by unlicensed employees draws Copilot Credits: from a capacity pack, the pay-as-you-go meter, or both. For teams that only need agents occasionally, metered access is often cheaper than seats; the crossover math depends on usage per person.

3. External user (customers, partners, public website)
Bills in Copilot Credits

External-facing agents always consume credits. No seat covers someone outside your tenant, so this is pure consumption economics: rate per interaction times traffic. Design choices (grounding, model tier) set the rate.

4. No human: autonomous agents
Bills in Copilot Credits

Autonomous agents run on triggers under their own identity, not an authenticated user’s. That means the licensed-user inclusion cannot apply, whoever the eventual beneficiary is. Every triggered run consumes credits, which is why autonomous patterns deserve per-agent consumption caps before they deserve production traffic.

What the builder needs (nothing, mostly)

The Copilot Studio maker license, the one that lets someone build agents, is free; an admin assigns it in the Microsoft 365 admin center. Costs attach to agent usage, pooled at the tenant level, not to building or to seats for builders. Testing an agent in the designer does not draw from prepaid flow capacity either.

The pieces around the license

Three adjacent line items complete the agent bill. Copilot Credits are the consumption currency for audiences 2 through 4: $200 per month per 25,000-credit capacity pack, or $0.01 per credit pay-as-you-go, with mechanics (enforcement at 125%, no rollover, per-agent caps) covered in the credits and capacity packs guide. Agent 365 is the governance layer: identity, security, and observability for agents at $15 per user per month, and it covers governance only, not agent runtime. And the June 2026 wave added Cowork and Work IQ as consumption-metered capabilities on top of the flat seat, which is a budgeting change more than a licensing one.

One date worth flagging to finance: on July 1, 2026, Microsoft’s broader pricing update took effect (base suite increases and permanent Copilot bundle SKUs). It did not change the agent-side economics above, but it changed the totals on the same invoice, so agent budget conversations in H2 2026 happen against a bigger baseline.

The decision in one paragraph

Count your audiences. If an agent serves only licensed employees under their own identity, the seat you already bought covers it within fair use. The moment unlicensed employees, external users, or autonomous triggers enter the picture, provision credits, pair a capacity pack with pay-as-you-go for continuity, and cap each production agent in the admin center. Then re-count quarterly, because audience drift, not feature drift, is what quietly moves agent bills.

For tier-by-tier M365 Copilot licensing (E3/E5, Wave 3, model choice), see the 2026 licensing reference. For the complete agent cost model with scenarios, see the cost model reference.