Copilot Credits, Explained Without the Confusion

By Kaustubh Giri, Sr Solution Engineer. ~12 min read.

“Why can’t I see the licenses we reserved?” “Will this environment keep spending after its credits run out?” “Why doesn’t the estimator match what we’re seeing?” I get some version of these questions almost every week, from IT admins, from finance, and from makers who just want to build.

If you’re confused, you’re not doing anything wrong. Copilot Studio billing has several moving parts: one currency, three ways to buy it, a tenant pool that must be allocated, and harnesses that consume it differently. Below I go through each part, with an FAQ and my monthly checklist at the end.

A quick caveat: Licensing details change often. Everything below reflects Microsoft Learn as of October 2026. I’ve deliberately left out list prices, because they vary by agreement and region. For numbers you’ll put in a budget, check the current Copilot Studio Licensing Guide and your agreement.

In this post:

What a Copilot Credit is
Three ways to buy credits
Pooled at the tenant, spent in an environment
When an environment runs out
“Our reserved licenses aren’t showing up”
Setting up pay-as-you-go
Estimates and the harness question
AI Builder and document pages
Investigating unexpected spend
Reporting, APIs, and telemetry
FAQ
Monthly cost-governance checklist

1. What a Copilot Credit is

A Copilot Credit is the common currency across Copilot Studio. It replaced “messages” as the unit on September 1, 2025, with no change to pack quantities or the pay-as-you-go rate. Credits measure the work an agent does: retrieving information, answering, and taking actions. Different features cost different amounts.

Feature (standard harness)	Copilot Credits
Classic answer (authored response)	1
Generative answer	2
Agent action (triggers, deep reasoning, topic transitions, computer use)	5
Tenant graph grounding	10
Agent flow actions	13 per 100 actions
Content processing tools	8 per page

A single turn can stack several of these. Microsoft’s own example is a graph-grounded answer costing 12 credits: 10 for grounding plus 2 for the generative answer. Reasoning models add a premium token charge on top of the feature rate. That’s why agent design matters as much as traffic.

The part people miss: When a user with a Microsoft 365 Copilot license uses a standard harness agent in Copilot Chat, Teams, or SharePoint, most of that usage is zero-rated. The same agent used by unlicensed users, or on a website, consumes credits. Agents built on the GitHub Copilot harness and computer use are billed for all usage, regardless of license.

2. Three ways to buy credits

There are three purchase options, and many customers combine them.

Capacity packs (Prepaid) - A monthly subscription from the Microsoft 365 admin center. Credits pool at the tenant, are enforced monthly, and don’t carry over. Required before you can assign the free Copilot Studio user license.
Pay-as-you-go (Consumption) - Billed to an Azure subscription through a billing policy linked to environments. No commitment. You pay at month end for what you actually used.
Prepurchase plan / P3 (Commit) - A one-year prepaid pool of Copilot Credit Commit Units, bought in the Azure portal. It still needs a billing policy in the admin center, and it’s consumed through that billing plan.

Here’s how I approach it. If a customer doesn’t know their volume yet, I start them on pay-as-you-go with limits in place. Once a few months of data show a stable baseline, packs or a prepurchase plan make sense. Committing a year of spend to an agent that’s six weeks old is guessing.

3. Pooled at the tenant, spent in an environment

This is the single most important concept. Prepaid credits land in a tenant-wide pool. Agents don’t consume from “the tenant”, though. They consume in the environment where they run. Credits are charged to that environment, not to the maker or the user.

In the Power Platform admin center, go to Licensing -> Copilot Studio -> Manage Copilot Credits. For each environment you set two things:

An allocation: how many prepaid credits the environment gets.
Draw from the available capacity in my tenant: whether the environment can keep consuming unallocated tenant credits after its allocation is gone.

Two details trip people up. First, for eligible environments with no allocation configured, drawing from the tenant is selected by default. Second, an allocation is only a boundary if both tenant draw and pay-as-you-go are off. Turning off tenant draw doesn’t stop consumption through a linked pay-as-you-go plan. If you manage many environments, the environment groups rule Cost controls - Draw from tenant credit pool sets this consistently, and the Power Platform API can apply allocations in bulk.

From the field: A software company asked me a very direct question: if we allocate credits per environment and don’t have pay-as-you-go, can an environment still go over? And will it quietly pull from unassigned tenant credits? My answer: with pay-as-you-go not linked and tenant draw turned off, usage in that environment stops at the allocation. It won’t pull from the tenant pool even if credits remain there. That’s the guardrail they wanted, and it’s the configuration I recommend for any environment with a fixed budget.

4. When an environment runs out

Situation	What happens
Environment has no available credits	Anything that needs credits stops. Agents stop responding. Makers can’t author with natural language, test, or generate evaluations. Both see a “You need credits to continue” message.
Tenant prepaid capacity fully consumed (agent flows)	New agent flow runs are blocked. Runs already in progress finish. The parent agent keeps working for non-flow interactions. Test runs aren’t blocked.
Tenant reaches 125% of prepaid capacity	Custom agents are disabled after the current conversation ends. Admins get an email and a notice in the admin center.
Environment linked to pay-as-you-go	Usage beyond the allocation is billed to Azure, so enforcement doesn’t apply.

Microsoft allows some overage, similar to a grace period, so business processes aren’t cut off at exactly 100%. I’d temper expectations, though. Don’t plan around the grace period. Plan for agents to stop, and decide in advance which environments are allowed to overflow into pay-as-you-go.

My tip: Use agent-level monthly limits for granular control. Under Licensing -> Copilot Studio -> Manage Agents, you can set a monthly credit limit, a notification threshold, and optionally stop usage when the limit is reached. This contains one runaway agent without starving the rest of the environment.

5. “Our reserved licenses aren’t showing up”

This is a common point of confusion, and it usually comes from mixing two different things: the Copilot Studio user license and Copilot Credits.

The Copilot Studio user license is free, but per Microsoft Learn you need a tenant prepaid Copilot Credit pack subscription before you can get it. In my experience, a license reservation under Volume Licensing doesn’t immediately appear as an assignable license in the Microsoft 365 admin center. It shows up once a paid tenant-level entitlement backs it. If you’re on pay-as-you-go, there’s no per-user license object to assign at all. Makers get access through the Copilot Studio authors setting in the admin center, which you assign to an Entra security group, plus the right environment role.

From the field: A payments company reserved Copilot Studio user licenses, set up a pay-as-you-go billing plan, and then waited days for the licenses to appear. They never did, because the tenant had no paid prepaid entitlement behind the reservation. Pay-as-you-go was the right path for them. Once we confirmed the billing plan was attached to the environment and gave the maker the right role there, they were building the same day. If you’ve reserved licenses and see nothing, check what’s actually backing the reservation before you open a ticket.

When a purchase doesn’t appear, I first confirm which tenant ID the order was placed against. More than once, that alone explained everything.

6. Setting up pay-as-you-go

Pay-as-you-go links an environment to an Azure subscription through a billing plan. It’s available for production and sandbox environments. Setup is short when the right people are in the room, and slow when they aren’t.

Step 1: Permissions

Power Platform admin, Dynamics 365 admin, Global admin, or Environment admin (for their own environments)
Rights to create resources and register providers in the Azure subscription (usually Owner or Contributor)

Step 2: Create the plan

PPAC -> Licensing -> Pay-as-you-go plans -> New billing plan
Pick the subscription and a resource group
Select the product and the environments

Step 3: Control it

Tag the Power Platform account resource in Azure
Create Azure budgets and alerts
Add agent limits with Stop usage

Keep two things in mind. Azure budgets and alerts notify you, but they don’t stop Copilot Studio consumption. And unlinking an environment stops future billing, while usage already incurred is still charged.

My tip: When a billing plan fails to create, it’s almost always Azure permissions, an Azure Policy, or an unregistered resource provider. The quickest fix I’ve found is to get someone with full rights on both sides, often a Global Admin, on a 30-minute call. It’s much faster than raising permissions one request at a time.

7. Estimates and the harness question

Microsoft’s Copilot Studio agent usage estimator lets you model consumption by agent type, traffic, orchestration, knowledge, and tools. It’s useful, but it’s built around the standard harness billing model.

The GitHub Copilot harness is billed differently. Building, testing, evaluating, and running those agents can all consume credits, and that usage isn’t covered by a Microsoft 365 Copilot license. On the standard harness, test chat runs aren’t billed. Developer and trial environments moved to usage-based billing for this harness on September 1, 2026.

From the field: A financial services firm was forecasting a GitHub Copilot harness agent with the estimator and noticed its guidance pointed to standard harness features. They were right to question it. The estimator wasn’t designed for that harness. What I do instead is build and test the agent with realistic scenarios, look at the credits it actually consumed, and use that as the baseline. It’s the closest estimate you’ll get, because it reflects the exact tools and configuration you’re shipping.

You can find which agents use which harness in the admin center under Manage -> Copilot Studio, using the Harness column. Only agents marked GitHub Copilot use consumption-based billing for all activity.

8. AI Builder and document pages

AI Builder causes many surprise bills, because it often runs in flows nobody associates with Copilot Studio.

In Copilot Studio, AI Builder features always consume Copilot Credits. Content processing is billed per page.
In Power Apps and Power Automate, AI Builder features use AI Builder credits first, then Copilot Credits. If both are exhausted, they fail.
There’s no automatic conversion of AI Builder credits into Copilot Credits.
From November 1, 2026, new and renewed Power Platform and Dynamics 365 licenses no longer include seeded AI Builder credits. Check the End of AI Builder credits calendar for how your contract is treated.
AI Builder consumption is computed periodically and can lag by several days, so overage can build before anything is blocked.

In one case, a tenant consumed roughly two and a half times its monthly AI Builder allocation. Almost all of it came from one user’s scheduled flows. The fix was simple once they found it, which is exactly why I recommend reviewing AI Builder usage by user each month, especially now that the seeded credits are going away.

9. Investigating unexpected spend

When finance asks “why is this number higher than last month?”, here’s how I approach it:

Open PPAC -> Licensing -> Copilot Studio -> Summary. Check the three-month daily trend and the top environments by credit usage.
Download the environment report first to find where consumption happened.
Then download the agent or user report to narrow it down.
On the Environments tab, open the environment and check prepaid versus pay-as-you-go units and whether it’s in overage.
In the consumption details grid, look at the feature names. Agent flow actions often explains a jump.
Compare billed and non-billed credits. Non-billed usage tells you how much licensed users are covering.

A tenant total can hide one agent doing all the damage. Prepaid packs can also fund usage-based Microsoft 365 experiences, so check Copilot -> Cost Management in the Microsoft 365 admin center too.

10. Reporting, APIs, and telemetry

Power Platform role-based access control (in preview) includes a Power Platform Reader role at tenant scope. Assignments are made through the Power Platform API or SDKs, not through the admin center UI. The Reader role gives you tenant and environment totals, which is enough for a high-level trend report.

From the field: While helping an online learning company stand up a costing dashboard, we tested the per-agent cost endpoints from outside the admin center. We tried a user with the Reader role, a service principal, and Global Admin. Every call returned 403 Forbidden. Only the admin center’s own session got data. My advice: build your dashboard on tenant and environment totals from the API, and use the downloadable agent and user reports for per-agent detail until that changes.

Don’t confuse the two: Application Insights is excellent for conversation telemetry: messages, topics, errors, and custom events. It doesn’t report Copilot Credits. Use it to understand why an agent is expensive, such as repeated tool calls or unnecessary grounding, and use the licensing pages for how much. For setup, see my governance toolbox post.

11. FAQ

Do makers need a paid license to build agents?

No. The Copilot Studio user license is free, but it requires a tenant prepaid pack subscription. On pay-as-you-go or a prepurchase plan, use the Copilot Studio authors setting with a security group instead.

Do unused credits roll over?

No. Capacity is enforced monthly, and unused credits don’t carry over.

Are credits charged to the user who ran the agent?

No. They’re charged to the environment where the agent runs. Control spend through environment access, allocations, and agent limits.

Are regular Power Automate cloud flows billed in credits?

No. Cloud flows use Power Automate licensing. Agent flows managed in Copilot Studio are billed in credits, unless they’re triggered by an agent for a Microsoft 365 Copilot licensed user.

Will an Azure budget stop spending?

No. Budgets alert you. To actually stop usage, use agent limits with Stop usage, or cap the environment.

Does testing cost credits?

On the standard harness, test chat and flow designer test runs for agent flows aren’t billed. On the GitHub Copilot harness, building and testing consume credits.

Where should each environment sit?

That depends on your environment strategy. I cover it in Environment Strategy and DLP. As a rule, only allow tenant draw or pay-as-you-go where an owner has signed off on the budget.

12. Monthly cost-governance checklist

Review the tenant summary: purchased, allocated, and consumed capacity, plus the three-month trend.
Check the Environments tab for any environment in overage or with unexpected pay-as-you-go units.
Download the environment report, then the agent and user reports for the top consumers.
Confirm tenant draw is off for every environment that should have a hard cap.
Review agent limits and notification thresholds against actual demand.
Check Agent flow actions and AI Builder consumption, especially from scheduled flows.
Filter the inventory by harness and review any new GitHub Copilot harness agents.
Reconcile Azure Cost Management for each billing plan, and confirm every plan has a business owner.
Reallocate unused credits from quiet environments before month end.

Where I’d start

If you only do three things this month: allocate credits to every environment that runs agents, turn off tenant draw where you need a hard cap, and set monthly limits on your highest-traffic agents. Then download the environment report and look at it with finance. Most of the confusion I see goes away once both sides look at the same numbers.

Happy to go deeper on any of this.

K.G.

Sources

Microsoft Learn: Licensing for agents powered by the standard harness (Copilot Studio)
Microsoft Learn: Billing rates and management (Copilot Studio)
Microsoft Learn: Enforcement policy for agents consuming Copilot Credits
Microsoft Learn: Manage Copilot Credits and capacity for Copilot Studio
Microsoft Learn: Manage costs for agents powered by the GitHub Copilot harness
Microsoft Learn: Manage Copilot Credits allocations programmatically
Microsoft Learn: Set up a pay-as-you-go plan (Power Platform)
Microsoft Learn: End of AI Builder credits; AI Builder overview of licensing
Microsoft Learn: Role-based access control for Power Platform admin center (preview)

Product details and statuses reflect Microsoft Learn as of October 2026 and may change. Customer examples are anonymized.

Kaustubh Giri · Sr Solution Engineer at Microsoft. 22 years in tech, 18 at Microsoft, helping enterprises build and govern AI agents on Copilot Studio and Power Platform.

LinkedIn GitHub About Me