What a Copilot Credit is
A Copilot Credit is the unit Microsoft uses to measure agent usage across Copilot Studio and the pay-as-you-go surfaces of Microsoft 365 Copilot. On September 1, 2025, Microsoft renamed the old "messages" currency to Copilot Credits. The quantities did not change: a prepaid pack still holds 25,000 units and the pay-as-you-go rate is still one cent per unit.
The word "credit" hides the important part: credits are consumed per feature, not per conversation. One user question can burn 1 credit or over 100 depending on how the agent answering it was built.
What consumes credits
Microsoft's current billing rates, per the Copilot Studio billing documentation:
| Agent feature | Rate |
|---|---|
| Classic answer (scripted response) | 1 credit |
| Generative answer | 2 credits |
| Agent action (triggers, deep reasoning, topic transitions) | 5 credits |
| Tenant graph grounding for messages | 10 credits |
| Agent flow actions (per 100 actions) | 13 credits |
| Text and generative AI tools, basic (per 10 responses) | 1 credit |
| Text and generative AI tools, standard (per 10 responses) | 15 credits |
| Text and generative AI tools, premium (per 10 responses) | 100 credits |
| Content processing tools (per page) | 8 credits |
Two rates deserve special attention. Tenant graph grounding costs 10 credits, five times a generative answer, so an agent that reads your Microsoft Graph pays a premium on every grounded response. And reasoning models bill on two meters at once: the feature rate for the action, plus the premium AI tools rate (10 credits per 1,000 tokens) for the reasoning itself. That is how the same agent design can cost 2 credits per answer with a standard model and an order of magnitude more with a reasoning model.
One more asymmetry that changes budgets: when an agent is used by an employee who holds a Microsoft 365 Copilot license, and the agent runs under that user's identity, these feature charges are included in the license under fair-use limits. The meter is for everyone else: unlicensed employees, external users, and agents that run autonomously under their own identity. The full picture is in the agents licensing guide.
The three ways to pay
| Option | Price | Effective rate | Fits |
|---|---|---|---|
| Capacity packs | $200/month per 25,000 credits | $0.008 | Predictable volume; pooled tenant-wide; packs stack |
| Pay-as-you-go | $0.01 per credit, billed via Azure | $0.01 | Unpredictable or low volume; no commitment; needs an Azure subscription |
| Pre-Purchase Plan (P3) | 1-year upfront, tiers from $2,850 | 5-20% off | Known annual volume you can commit to; bought in the Azure portal |
The break-even is simple arithmetic: a $200 pack beats pay-as-you-go once you use more than 20,000 credits a month. Below that, the meter is cheaper. Above it, packs win, and the Pre-Purchase Plan wins again once you have a year of usage data you trust enough to commit against. Two behaviors matter for planning: unused pack credits do not roll over at month end, and if you pair packs with pay-as-you-go, overflow beyond the prepaid amount bills to the meter automatically with no service interruption.
The 125% rule: what happens when you run out
Without pay-as-you-go as a safety net, Microsoft allows overage consumption as a grace buffer, then enforces: when a tenant reaches 125% of prepaid capacity, custom agents are disabled. An ongoing conversation is allowed to finish; every attempt after that is rejected until you add capacity, reallocate it, or enable the meter. Your admin gets an email and a notice in the Power Platform admin center, and your users get "This agent is currently unavailable."
Agent flows enforce differently and earlier: when prepaid capacity is fully consumed (100%, not 125%), new flow runs are blocked while the parent agent keeps answering normally. In-progress runs complete, test runs are exempt, and the block resets when credits renew monthly.
The unglamorous control that prevents both: the Power Platform admin center lets you cap monthly consumption per agent (Licensing → Copilot Studio → Manage Agents) and allocate credits per environment. A cap on every production agent turns a potential outage into a visible budget line.
Five planning moves
For where credits fit in the wider agent bill (seats, Agent 365, Cowork and Work IQ metering), see the full M365 Copilot agents cost model reference. For Studio-specific pricing scenarios with worked math, see Copilot Studio pricing.