Microsoft Copilot Licensing & Credits: Costs, Usage, and Billing Explained
Microsoft Copilot licensing and Copilot Credits cover different types of usage.
A Microsoft 365 Copilot license provides access to Copilot capabilities for an individual user at a fixed subscription price. Copilot Credits measure certain usage-based AI agent activities, including actions, data grounding, and automated workflows.
This article explains the pricing model so you can plan for the cost of a Copilot rollout.
What Is the Difference Between Microsoft Copilot Licenses and Copilot Credits?
A Copilot per-user license is a seat. You pay a flat monthly price for a person. For reference, Microsoft 365 Copilot lists at $30 per user per month paid yearly on the enterprise plan (US list price). Smaller organizations on a Microsoft 365 Business plan, up to 300 seats, can buy Microsoft 365 Copilot Business instead. It lists for $21 per user per month and has the same Copilot experience as the Microsoft 365 apps.
Copilot Credits are a meter. Think of your electricity bill. The connection to the building is the subscription. The kilowatt-hours are the credits, and they only move when something is actually running.
In Copilot, that something is an agent. When an agent answers a question, takes an action, or pulls in your company data, Microsoft counts that work in credits.
So the planning question has two parts. How many people need a license? That sets your seat cost. Which agents will you run, who will use them, and where? That sets your meter.
Key Copilot Billing Terms Explained
These are the words you will run into in Microsoft’s documentation and on your bill.
| Term | What it means |
| Zero-rated | Eligible agent usage that does not consume Copilot Credits. Whether usage qualifies depends on the user’s license, how the agent is used, where it runs, and Microsoft’s fair-use limits. |
| Fair-use limits | Microsoft-defined usage thresholds that apply to zero-rated agent activity. Usage beyond these limits may consume Copilot Credits or be subject to other restrictions. |
| Usage-based billing | Charging by what you use instead of by user. An admin must set up a billing policy for this billing type. |
| Billing policy | An admin setting that says how usage is paid for and which services can spend credits. |
| Tenant | Your organization’s Microsoft 365 account. Credits are pooled at this level. |
| Tenant graph grounding | When an agent uses permitted content from your organization’s Microsoft 365 environment, like SharePoint files, Teams content, or email, to answer a question. |
| Environment | A container in Copilot Studio where agents live. You assign credits to each environment. |
| Harness | The runtime framework that hosts and directs an agent. Copilot Studio has three types: GitHub Copilot harness for reasoning-heavy, multistep work; standard harness for rule-based, predictable agents and flows; and Copilot chat harness for extending Microsoft Copilot Chat with organizational knowledge. |
Important note: Beginning December 1, 2026, new Microsoft 365 Copilot Business licenses purchased through Cloud Solution Providers (CSPs) will have usage-based billing enabled by default. The spending limit is 4,000 credits per month at $0.01 per credit, for a potential added cost of $40 per user monthly if all credits are used. Learn the details here (you’ll need to scroll two-thirds down the page).
When Do Microsoft Copilot Agents Use Copilot Credits?
A Microsoft 365 Copilot license does not come with a monthly bucket of credits. What it gives you is free use in the right scenarios. This table shows where the line sits. Zero-rated use is subject to fair-use limits, so check Microsoft for the current limits.
| Scenario | Credits needed? |
| Licensed employees use an internal agent, such as an HR benefits agent, inside Teams | No. Zero-rated, draws no credits. |
| A licensed person chats with Copilot themselves | No. That is covered by the subscription. |
| The same HR agent is opened to people outside your company, such as job candidates on your public careers site | Yes |
| Unlicensed staff use the internal agent | Yes |
| An agent runs on its own, without a person starting it (for example, on a schedule), even for internal work | Yes |
| An agent uses the computer use feature, which lets it operate a screen the way a person would (clicking and typing in an app) | Yes, even for licensed users. It is billed at the agent action rate. |
| An agent flow (an automated workflow) that is not started by an agent trigger | Yes |
| An agent built in Copilot Studio on the GitHub harness | Yes, from the time you start building |
Credit usage varies based on what an agent needs to do to complete a task: which AI model it uses, how much information it processes, which tools it calls, and how long it runs. To estimate usage for a specific agent, use Microsoft’s Copilot Studio agent usage estimator.
How Much Do Copilot Credits Cost per Action?
“One chat equals one credit” is the wrong mental model. Each billable activity an agent performs – generating an answer, accessing company data, or taking an action – has its own credit charge, so answering one question can trigger multiple charges. These are the published US rates as of October 2026.
| Action | What it means | Example | Copilot Credits |
| Classic answer | A predefined response delivered through a scripted conversation, rather than generated by AI. | A customer asks about business hours, and the agent returns a prewritten reply: “We’re open Monday–Friday, 9–5.” | 1 |
| Generative answer | An AI-generated response based on the user’s question and the agent’s available knowledge sources. | A customer asks whether weekend pickup is available, and the agent composes an answer from the store’s published pickup policy. | 2 |
| Agent action | A task an agent performs using a tool or connected system, such as updating a record or submitting a request. | A customer requests a callback, and the agent creates a callback request in the company’s CRM. | 5 |
| Tenant graph grounding (answering from your Microsoft 365 data) | Using permitted organizational content, such as SharePoint files or email, to inform an agent’s answer. | An employee asks about the company’s travel policy, and the agent uses a SharePoint policy document the employee has permission to access to inform its answer. | 10 |
| Agent flow actions | Individual steps in an automated agent flow, such as retrieving data, checking a condition, or sending a notification. | A service-request flow retrieves the request, checks its priority, and sends a notification. These are individual steps within the flow. | 13 per 100 actions |
| AI tools: basic, standard, premium | Prompt-based AI tasks, such as summarizing or generating text, grouped into tiers based on the model used. | An AI prompt summarizes a customer’s support request before it is routed to the service team. The selected model determines the tool tier. | 1, 15, and 100 per 10 responses |
| Reasoning models | AI models that work through complex problems with additional reasoning before producing an answer. | An agent uses a reasoning model to compare delivery schedules, inventory, and staffing constraints before proposing a fulfillment plan. | The feature rate, plus 10 per 1,000 tokens (premium AI tools) |
| Content processing | AI tools that read and extract information from document pages, such as invoice fields. | An agent extracts the vendor name, invoice number, and total from an uploaded invoice. | 8 per page |
| Voice: classic, generative, premium generative | Spoken interactions with an agent, using scripted conversations or generative AI at standard or premium voice tiers. | A caller asks about store hours. Classic voice delivers a scripted reply; generative voice composes a spoken answer. The configured voice tier determines the rate. | 10, 35, and 75 per minute |
Takeaway: Budget for the billable activities an agent performs, not just the number of questions it answers. One request that generates an answer, accesses company data through tenant graph grounding, and takes an action uses an estimated 17 credits, or $0.17 at the rates above.
Copilot Credits Cost Example: 32,000 Credits per Month
Suppose your company has 50 employees with Microsoft 365 Copilot licenses. Using the enterprise price cited in this article, those licenses cost $1,500 per month. Qualifying employee use of an internal HR agent in Teams adds no credit charges within fair-use limits.
Separately, your public customer-service agent and background agent activity consume 32,000 Copilot Credits per month. At the cited pay-as-you-go rate, that adds $320, bringing the combined monthly budget to $1,820. Use this combined figure as a baseline, then compare prepaid options once usage becomes predictable.
Copilot Credits Pricing: Pay-as-You-Go vs. Prepaid Plans
Microsoft offers three ways to buy credits. The best fit depends on how predictable your usage is and whether you can commit in advance.
| Purchase option | How it works | Best fit | What to watch |
| Pay-as-you-go | Microsoft bills actual usage through a linked Azure subscription at $0.01 per credit. | Pilots, new agents, variable demand, or overage beyond prepaid capacity. | Monthly costs can fluctuate. A billing policy and Azure subscription must be in place. |
| Prepaid capacity packs | A $200 monthly pack provides 25,000 Copilot Credits. | Steady, predictable usage above 20,000 credits per month. | Unused credits expire at the end of the month. Enable pay-as-you-go overage if agents must continue after the pack is exhausted. Packs are billed annually. |
| Copilot Credit Pre-Purchase Plan (P3) | A one-year commitment provides Copilot Credit Commit Units that eligible products draw down over the term. | Larger, predictable deployments that can justify an annual commitment. | Discount tiers and eligible products can vary. Confirm current terms with Microsoft or your reseller before committing. |
Start with pay-as-you-go for a new agent. Move to prepaid capacity only after monthly demand is stable, and define in advance whether the agent should stop or use overage when prepaid credits run out.
How to Manage Copilot Credits and Control Costs
Where you manage billing depends on the agents you use:
- Microsoft 365 agents: Manage supported usage-based billing in the Microsoft 365 admin center.
- Agents built in Copilot Studio: Manage credit capacity and billing in the Power Platform admin center. This is the administrative platform behind Copilot Studio, even if you don’t use other Power Platform products.
Monitor actual spending against your forecast, then confirm whether agents stop, use shared capacity, or continue through pay-as-you-go when prepaid credits are exhausted.
Microsoft Copilot Licensing and Cost Planning Checklist
- Identify who needs a license and calculate the subscription cost. Record existing Microsoft 365 subscriptions, choose the applicable Copilot license, and multiply the seat count by its current price and billing term. Then check which employee-initiated agent interactions qualify for zero-rated use.
- List your agents and who will use them. Note where each agent runs, what it does, and whether it responds to people or works automatically in the background. Use this list to separate included usage from activity that needs credits.
- Estimate how many credits your agents will use each month. Start with how often each agent will run and what it will do. One request may trigger several charges.
- Compare the payment options for your expected credit usage. Use your monthly credit estimate to compare paying for credits as you use them, buying monthly credit packs, or committing to a prepaid plan for a year. Check what each option would cost, including any prepaid credits you might not use or extra credits you might need. Then add employee licenses and any separate tool or resource charges to calculate your total budget.
- Decide how much agents can spend and what happens when credits run out. Set up Microsoft 365 agent billing in the Microsoft 365 admin center, or Copilot Studio capacity and billing in the Power Platform admin center. Set the available spending limits and alerts, then confirm whether agents will stop or keep running with shared credits or additional charges when their credits run out.
- Assign a cost owner and a review schedule. Review consumption and spending weekly for the first few months, compare actual usage with the forecast, and investigate unexpected increases. Agree on who can adjust limits, billing settings, or agent design, then revisit prepaid purchases once demand becomes predictable.
Get More Value from Microsoft Copilot Without Unexpected Costs
JourneyTeam helps organizations evaluate Microsoft Copilot licensing, estimate agent consumption, and plan deployments around real business needs. Explore JourneyTeam’s Microsoft Copilot services to build a licensing, adoption, and cost-management plan that fits your users, agents, and expected usage.
Make sure you’re paying for the capabilities you need and not costs you didn’t anticipate.
