Copilot Studio credit (Copilot Credits) optimization
The official basis of Copilot Studio economics: which operation costs how many credits, the 125% overage rule, per-agent monthly caps, and the official usage estimator. The source of this site's 'credits + hours saved' signature.
This is a summary with a canonical link to the original Microsoft resource; up-to-date content lives at the source. — Microsoft Learn.
“How many credits?” is the most miscalculated line item in Copilot Studio projects. The good news: Microsoft publishes the rates openly, so you can design the architecture around credits from day one.
Official credit rates (Copilot Credits):
- Classic answer: 1 credit
- Generative answer: 2 credits
- Agent action (e.g. trigger / deep reasoning; incl. computer use): 5 credits
- Tenant graph grounding (per message): 10 credits
- Agent flow actions (per 100 actions): 13 credits
A single complex prompt can consume several meters at once. Example: a generative answer grounded on the tenant graph = 10 + 2 = 12 credits.
Management and cost control:
- Capacity is pooled across the tenant; it can be allocated per environment.
- Overage rule: when consumption reaches 125% of prepaid capacity, custom agents are disabled. Ongoing conversations aren’t cut off; subsequent calls are rejected.
- Per-agent monthly cap: set limits before overage via Power Platform Admin Center → Licensing → Copilot Studio → Manage Agents.
- Pay-as-you-go: link an Azure subscription to an environment and overage is billed to Azure instead of being blocked.
Official tool: Microsoft’s Copilot Studio Agent Usage Estimator estimates credits by agent type, traffic, orchestration, knowledge and tools — ideal for pre-proposal budgeting.
The numbers are Microsoft’s published official rates; they may change as the product evolves — check the source for the latest. This page underpins every “credits” badge on the site and the upcoming “How Many Credits?” calculator.