Do Copilot Studio credits burn when staff already have Copilot seats?

You’re right to challenge the “we bought seats and packs, so we must be double-paying” reflex. The billing story is real — and more nuanced than a sales slide.

Here’s what’s happening. Copilot Studio meters work in Copilot Credits (prepaid capacity packs, pre-purchase plans, or Azure pay-as-you-go). Learn’s billing-rates table is explicit: for employee-facing (B2E) agents, classic answers, generative answers, many agent actions, tenant graph grounding, and qualifying agent-flow runs are no charge when the user holds a Microsoft 365 Copilot licence and the agent runs under that authenticated user’s identity — subject to fair-use limits Microsoft can update. That is why a licensed colleague chatting with an internal agent in Copilot Chat, Teams, or SharePoint often shows zero-rated usage. Credits do still burn for unlicensed users, external/customer-facing channels, autonomous agents without that licensed user identity, Computer-Using Agents (CUA), many non-qualifying flow triggers, and GitHub Copilot harness agents. Unused prepaid capacity does not roll over month to month. At 125% of prepaid capacity, custom agents can be disabled until you buy more, reallocate, or attach pay-as-you-go.

This is First Law for money: don’t pour budget into packs until you can see how usage comes back out — who is licensed, which agents are internal vs external, and which features are never included. 12 Panes puts Cost & Value in Steady before maker freedom becomes an open meter.

Practical options:

1. Map agents to licence cohorts. Internal employee agents aimed at Microsoft 365 Copilot–licensed staff: design for zero-rated paths; still keep a small credit buffer for makers, tests that bill, and spillover. External or unlicensed audiences: size packs or PAYGO honestly. Best balance for most organisations.
2. Prepaid packs + PAYGO safety net. Packs for predictable floor; Azure meter so agents don’t die at 125%. Monitor in Power Platform admin centre (Licensing → Copilot Studio) and set per-agent monthly caps where available.
3. Assume “everyone has Copilot so Studio is free.” Politically neat; false for guests, contractors without seats, public web agents, autonomous jobs, and CUA. I’d avoid this assumption in any board pack.
4. Refuse Studio until every user has a Copilot seat. Clean story; slow for Chat-only or metered SharePoint-agent paths. Fine if Wave 0 already decided seats-only.

The caution: Product names and inclusion tables move — verify against the current Licensing Guide and the billing-rates footnotes (especially agent-flow triggers and CUA). Capacity-pack views and Azure invoices don’t always match day-to-day dashboards; reconcile on the monthly bill. Chat vs Premium licensing for users is a separate decision from Studio credits for agents.

I’d suggest one FinOps worksheet: agent → audience (licensed B2E / unlicensed / external / autonomous) → expected credits → owner. Buy packs for the non-zero rows, not for the marketing slogan. That keeps Steady Cost ahead of sprawl.

You’re asking the right question before renewal theatre. You’ll have a calmer story when the invoice matches the architecture.

DIGITAL SKILL WORKS LTD / 12 PANES · You ask, we answer