TL;DR: Microsoft has split Copilot billing into two tracks — your flat per-user subscription covers everyday tasks, while a new usage-based system called “Copilot Credits” handles heavy frontier model workloads. Usage-based billing goes default-on for new licenses starting October 19, 2026. If your organisation has not set spending limits yet, now is the time.
For the past year, budgeting for Microsoft 365 Copilot was straightforward. You paid a fixed monthly amount per licensed user, and every feature was included.
That model is changing.
Microsoft has introduced a hybrid billing architecture that separates routine AI assistance from compute-intensive frontier model tasks. For most everyday users, nothing changes. But for administrators managing large tenants, understanding these new billing layers is now a governance priority.
If you are an IT administrator, a finance lead, or an operations manager responsible for Microsoft 365 costs, here is exactly what changed and what you need to configure before the October 19 deadline.
Official Website: Set up usage-based billing for Copilot Credits — Microsoft Learn
What are Copilot Credits and why do they exist?
How did Copilot billing work before?
Until mid-2026, Microsoft 365 Copilot used a single pricing model: one flat subscription fee per user per month. Every Copilot feature — from meeting recaps to document drafts — was included in that seat license.
As Microsoft added more compute-intensive capabilities (like multiple frontier AI models, long-document reasoning, and Autopilot background tasks), a flat pricing model created a problem. Running GPT-6.1 Sol or Claude Sonnet 5.5 for hours at a time costs significantly more to serve than a quick email draft. A fixed price per seat cannot accommodate both scenarios without either overcharging light users or restricting heavy users.
The solution is a two-track billing model.
What is the new two-track billing structure?
| Track | What it covers | How it is billed |
|---|---|---|
| Everyday AI | Standard chat, email drafts, meeting recaps, document summaries, basic Copilot in Office apps | Flat per-user subscription license (USL) — no change |
| Advanced AI / Frontier | Frontier model sessions (GPT-6.1 Sol, Claude Sonnet 5.5), Copilot Cowork, Code, Autopilot agents, Copilot Studio agent runs | Usage-based billing via Copilot Credits |
In plain terms: your seat license pays for Copilot as a productivity tool. Copilot Credits pay for Copilot as a reasoning engine running extended, compute-heavy tasks.
When does usage-based billing go live?
What is the October 19 deadline?
Starting October 19, 2026, Microsoft is enabling usage-based billing as the default configuration for new Microsoft 365 Copilot Business license purchases made directly through Microsoft.
For organisations that purchase through Cloud Solution Providers (CSP), the default-on date is December 1, 2026.
This does not mean credits will be charged immediately by default. Enterprise tenants still need an administrator to create a spending policy before advanced AI features are activated and credits can be consumed. But the billing infrastructure is being enabled in the background.
Microsoft recommends that administrators configure spending controls before that date — not after.
How do Copilot Credits work?
What is a Copilot Credit?
A Copilot Credit is the billing unit for advanced AI compute. When a user invokes a frontier model session or runs an Autopilot background task, the system draws against a credit balance associated with their account or security group.
Microsoft has not published a fixed “credits per action” conversion rate publicly, as consumption varies by task complexity, model selected, and context length. The admin dashboard shows credit consumption in real time, so you can observe patterns over your first few weeks.
What experiences draw from Copilot Credits?
Based on Microsoft’s published guidance, the following features draw from the Copilot Credits balance:
- Frontier model sessions — Switching to GPT-6.1 Sol or Claude Sonnet 5.5 in Copilot Chat.
- Copilot Cowork — Delegated background tasks that work on objectives while the user is away.
- Copilot Code — Generating, testing, and debugging solutions using the embedded coding environment.
- Copilot Autopilot — Persistent agent tasks running independently in the background.
- Copilot Studio agent runs — Autonomous agents built and deployed in Copilot Studio with generative orchestration.
- Advanced SharePoint and OneDrive operations — Large-scale document grounding and multi-file analysis at scale.
Standard features — daily chat, Office app assistance, meeting recaps, basic email drafts — remain covered by the seat license.
What admin controls are available?
How do I manage Copilot Credits in the admin centre?
All FinOps controls for Copilot Credits live in the Microsoft 365 Admin Center under Billing → Cost Management.
The dashboard provides:
- Real-time consumption monitoring — See credit usage by user, security group, feature type, and date range.
- Spending policies — Define which users or groups can access specific advanced AI features, and set a hard monthly credit cap per group.
- Spending limit alerts — Set automated email alerts when consumption hits 75% or 90% of a group’s monthly allocation.
- Model profile assignment — Assign specific billing methods (pay-as-you-go credits or prepaid credit packs) to different user segments.
How do I create a spending policy step by step?
- Open the Microsoft 365 Admin Center → go to Billing → Cost Management.
- Select Spending policies → click Create policy.
- Name the policy (e.g., “Finance Team — Advanced AI”).
- Choose the security group or individual users this policy applies to.
- Select which Copilot experiences this group can access (e.g., allow frontier models, restrict Autopilot agents).
- Set a monthly credit limit for the group.
- Configure alert thresholds (75% and 90% of allocation recommended).
- Click Save — the policy activates immediately.
What should different groups in your organisation do?
What does this mean for IT administrators?
- Act before October 19 — If you have not created any spending policies, advanced AI features remain restricted even if the billing infrastructure is enabled. But it is better to be prepared with defined policies than to scramble after the date.
- Start with a pilot group — Assign a generous credit allocation to a small team (e.g., your IT or innovation team), monitor usage for 2 weeks, and use that data to set realistic limits for the broader organisation.
- Check CSP agreements — If your organisation purchases Microsoft 365 through a Cloud Solution Provider, confirm with your partner when the default-on date applies (December 1, 2026 for CSP channels).
What does this mean for business users?
Most users will not notice a change day-to-day. Standard Copilot chat, meeting recaps, and document drafting continue without interruption under the seat license.
If you select a frontier model in Copilot Chat (GPT-6.1 Sol or Claude Sonnet 5.5) and see a message that your group has reached its credit limit, you will automatically fall back to the standard balanced model. Core Copilot features will not stop working — only frontier compute calls will pause until the limit resets or is increased by your administrator.
FinOps for Copilot Credits — Summary
| Item | Detail |
|---|---|
| Everyday AI | Covered by flat Microsoft 365 Copilot seat license |
| Advanced AI / Frontier | Billed via Copilot Credits (usage-based) |
| Default-on date (Direct) | October 19, 2026 |
| Default-on date (CSP) | December 1, 2026 |
| Admin controls | M365 Admin Center → Billing → Cost Management |
| Policy type | Spending policies per security group, with monthly credit caps |
| Alert options | Automated email at 75% and 90% of group limit |
| What happens at limit | Users fall back to standard model — core Copilot continues |
What to do next (admin checklist)
Before October 19, complete these three steps:
- Review your licence count — In the Admin Center, confirm how many users hold Microsoft 365 Copilot licenses. This determines the scale of credit allocation planning needed.
- Create at least one spending policy — Even a broad, generous policy applied to all licensed users is better than none. It establishes the governance framework you can refine later.
- Run a 2-week pilot — Enable frontier model access for a defined pilot group, monitor credit consumption in the Cost Management dashboard, and use that data to set proportionate limits for the wider rollout.
You do not need to have everything perfect on day one. Start small, measure, and adjust.
FAQs: Microsoft 365 Copilot Credits
Do existing Microsoft 365 Copilot subscribers need to do anything immediately?
Only if you want frontier model features to be available to your users before the October 19 default-on date. You need to create a spending policy in the Admin Center to enable access. Otherwise, frontier compute features will remain restricted until a policy is created.
What happens if we do not create a spending policy before October 19?
Advanced AI features will remain inaccessible for your users even after the default-on date, because a spending policy must exist before credits can be consumed. However, Microsoft recommends acting before the deadline to avoid disruption if you do want these features available.
Can I set a zero credit limit to completely block frontier model access?
Yes. Creating a spending policy with a zero credit allocation effectively blocks all advanced AI feature consumption for that group while keeping standard Copilot features fully functional.
Will credit consumption affect our existing Microsoft 365 invoice?
Yes. Copilot Credits appear as a separate line item on your Microsoft 365 or Azure invoice, distinct from your seat license charges. This separation makes it straightforward to track AI compute costs independently of standard software licensing.
Do Copilot Studio agents also draw from Copilot Credits?
Yes. Autonomous agents with generative orchestration deployed through Copilot Studio draw from the usage-based Copilot Credits balance. Microsoft is rolling out FinOps support for Copilot Studio agents specifically in October 2026.
What is the default monthly credit cap for new licenses?
Microsoft has indicated a default monthly spending cap of approximately 4,000 Credits (or \$10 per user, depending on the offer type) for new Microsoft 365 Copilot Business licenses purchased after the default-on date. Enterprise plans may have different defaults — confirm with your Microsoft account team.
