On 1 December 2026, Copilot usage-based billing switches on by default for new Microsoft 365 Copilot Business licences bought through CSP. Each user gets a default spending limit of 4,000 Copilot Credits a month, and Microsoft’s own worked example is that a hundred users could consume up to 400,000 credits.
Which raises the only question that matters, and the one almost nobody is answering: what is a credit worth in money?
Transputec has run Microsoft licensing for UK organisations for 40 years, and this is the first Copilot change where the answer is not on a price list. What follows is what Microsoft has actually confirmed, what it has not, and the four things to settle before the date.
A spending limit expressed in credits is not a budget. Until you can convert credits into pounds, a 4,000-credit default is a number you have accepted rather than a number you have chosen.
What Changes on 1 December
Microsoft’s wording in its October Partner Center announcement is direct: “Starting December 1, 2026, usage-based billing will be enabled by default for new Microsoft 365 Copilot Business licenses purchased in Cloud Solution Provider (CSP).”
Three details from the same announcement are worth having exactly.
- The date moved. It was previously 2 November. If your supplier briefed you on Copilot usage-based billing a month ago, their date is wrong.
- The default limit is 4,000 Copilot Credits per user per month, and Microsoft is clear it “can be adjusted by admins”. The adjustment is the whole game.
- The UK is in scope. The change is not available at launch in Australia, Belgium, Brazil, France, Germany, India, Italy, Korea, the Netherlands, Poland and Spain. Britain is not on that list, so UK buyers get this on day one.
Partner Center sandbox environments opened on 2 November, which is how your provider should be testing this rather than discovering it on your invoice.
Which Licences This Actually Touches
This is where most of the coverage has been loose, and getting it wrong means worrying people who have nothing to worry about.
Copilot usage-based billing defaults on for new purchases of Microsoft 365 Copilot Business licences, standalone or bundled, through CSP. That is the scope. It is not every Microsoft 365 tenant, it is not Business Premium or Business Standard on their own, and it is not Microsoft 365 Copilot in its enterprise form.
So the test is narrow. Are you buying new Copilot Business licences, through a CSP partner, on or after 1 December? If any of those three is no, nothing changes for you on that date.
Existing subscriptions are explicitly unaffected. Microsoft states that no action is required for them and that product IDs, pricing, renewal terms and auto-renew settings remain unchanged.
There is a second change on the same date that has had almost no attention. From 1 December, Copilot and Copilot Business can be bought without a qualifying Microsoft 365 base subscription, and the current “(add-on)” versions reach end of sale in CSP. End of sale is not end of life, and existing customers can still renew and adjust seat counts. But if your renewal paperwork says “add-on”, it is describing a product that is no longer being sold to new buyers.
Buying Copilot Business Seats Before December?
The spending limit should be set before the first seat is assigned, not after the first invoice. Book an initial session with a Transputec Microsoft specialist and we will set it with you.
Book a consultationWhat a Copilot Credit Costs, and Why That Is Hard to Answer
Here is the uncomfortable part. Microsoft has published the limit, the example and the mechanism. It has not published the rate where an administrator would look for it.
Its own documentation on Copilot usage-based billing and cost management runs to several thousand words on dashboards, policies, alerts and reporting without naming a price. The Cost Management API is explicitly scoped away from it: Microsoft says the API “does not include pricing, invoices, currency costs, or purchasing forecasts”.
The rate reported consistently across the partner community is one US cent per Copilot Credit. We have not been able to confirm that figure in Microsoft’s own public documentation, so treat it as the working assumption it is rather than a quoted price. On that assumption the arithmetic is simple, and it is the arithmetic that should be in front of whoever signs the order:
| At the default limit | Credits | At one cent per credit |
|---|---|---|
| One user, one month | 4,000 | about $40 |
| 100 users, one month | 400,000 | about $4,000 |
| 100 users, one year | 4,800,000 | about $48,000 |
That is a ceiling, not a forecast. Charges follow actual usage, and a tenant where nobody touches a metered feature consumes nothing. But the ceiling is what you have agreed to by default, and on a hundred seats it is a number most finance teams would want to have approved rather than inherited.
So the single most useful thing you can do this month is ask your CSP partner, in writing, what a Copilot Credit costs in sterling. If they cannot tell you, that is worth knowing before 1 December rather than after. Microsoft also publishes a Copilot Credit Estimator for modelling likely Cowork consumption, which is the right tool for turning a ceiling into an expectation.
What Is Still Included, and What Now Meters
Your Copilot seat still buys the Copilot you already know. Chat, the experiences inside Word, Excel, PowerPoint, Outlook and Teams, and the rest of the seat-based functionality are unchanged by this. Nothing you use today starts costing extra on 1 December.
Copilot usage-based billing applies to a specific and growing list of features. The Partner Center announcement names three: Copilot Cowork, Work IQ APIs and GitHub Copilot Harness. Microsoft’s admin documentation lists more:
- Cowork
- Advanced work in SharePoint
- Advanced work in OneDrive
- Work IQ API for custom apps and agents
- Copilot Managed Runtime
- Teams Phone Agent
- Code, currently in Frontier
Note the direction of travel. Microsoft says plainly that it “will add more agents and services over time”, which brings us to the setting that deserves more attention than the credit limit itself.
The Default That Matters More Than 4,000
Inside spending policies there is a setting called Auto-apply new services, and Microsoft confirms it “is enabled by default”.
What that means in practice: when Microsoft adds a new metered agent or service to the platform, your existing spending policy automatically covers it. No decision, no review, no change request. The service arrives already inside your billing arrangement.
Microsoft flags this itself with an Important callout telling administrators to “review existing spending policies to determine whether automatic coverage is appropriate”. That is unusually plain language for a product note, and it is worth taking at face value.
For most organisations the right answer is to turn it off and review each new service on arrival. The cost of doing so is a few minutes per service. The cost of leaving it on is that your exposure can grow because of a Microsoft roadmap decision rather than one of yours. If you run anything resembling change control, this setting belongs inside it.
This is the governance half of Copilot usage-based billing, and it is the half that does not appear in any announcement headline.
How to Set a Limit Before Anyone Needs One
The controls for Copilot usage-based billing live in the Microsoft 365 admin center under Copilot, then Cost management. The order below is the one that avoids rework.
- Connect the billing method deliberately. Pay-as-you-go needs an Azure subscription attached. There are also prepaid capacity packs and a Copilot Credit Pre-purchase Plan. Which you choose changes your exposure profile, so decide rather than accept.
- Create an identity-based spending policy covering the users or groups who should have access at all. Not everyone with a Copilot seat needs metered features.
- Set the policy and per-user spending limits to a number you have arrived at, not 4,000 because it was there.
- Turn off Auto-apply new services unless you have a reason to want automatic coverage.
- Configure alerts and user-level threshold notifications, so somebody hears about consumption before the invoice does.
- Give finance a reader role. Microsoft supports reader-based roles that can review consumption dashboards without permission to change policies or billing. Finance should be able to see this without being able to break it.
Step six is the one most organisations skip, and it is the one that makes the rest sustainable. A cost control that only the Microsoft administrator can see is a cost control that gets reviewed once. If your estate is managed for you, this is also the point at which managed IT services should be doing it rather than briefing you to do it.
A Question Worth Asking Your Provider
One thing to be aware of when your supplier raises this with you.
Microsoft’s framing of this change to partners is openly commercial. The announcement describes “less setup friction”, “greater growth opportunity” and the observation that “early usage can create a natural path to expanded consumption, upsell conversations”. There is also a Copilot Cowork activation incentive available to partners who drive adoption of the metered features.
None of that is improper, and we are a CSP partner ourselves, so this applies to us as much as anyone. It is simply useful context. The channel has a financial reason to encourage you to switch these features on, and no corresponding reason to encourage you to set a low limit first.
So the question is a fair one to ask anybody, including us: before you enable a metered feature in my tenant, will you have set the spending limit with me and told me what a credit costs in sterling? A provider who has thought about this will have an answer ready.
How Transputec Handles Copilot Usage-Based Billing
Transputec sets the spending limit and the policy scope as part of deployment rather than as a follow-up, because the only moment this is genuinely cheap to get right is before the first seat is assigned.
In practice that means three things on every Copilot engagement. The limit is a number you approved, not a default you inherited. Auto-apply new services is a decision you made, recorded, rather than a setting nobody looked at. And finance gets a reader role from the start, so consumption is visible to the people who care about it without a monthly request to IT.
The wider work sits in Copilot for Microsoft 365 and Microsoft 365 services, and if the question behind the billing one is whether Copilot is earning its licence at all, our note on measuring Copilot ROI works through that calculation. The cost discipline is the same one we apply to cloud cost optimisation generally: attribute the spend, establish the unit cost, then decide.
What to Do Before 1 December
Four things, and none of them takes long.
Work out whether you are in scope at all. New Copilot Business licences, through CSP, on or after 1 December. If that is not you, close the tab with a clear conscience.
Ask your CSP partner in writing what a Copilot Credit costs in sterling. You cannot set a budget in a currency you do not have a rate for, and the answer tells you something about the supplier either way.
Decide the spending limit before you buy, not after. Four thousand credits per user per month is Microsoft’s starting position, not a recommendation tailored to you.
Check Auto-apply new services. It is on by default, and it is the setting that lets your exposure grow without a decision.
Copilot usage-based billing is not a trap and it is not a price rise. It is a change in who has to pay attention, and when. If you want help setting the limits before the date rather than reconciling an invoice after it, talk to our team about the Microsoft licensing work behind our modern workplace practice.
Frequently Asked Questions
What is Copilot usage-based billing?
It is Microsoft charging for certain Copilot features by consumption rather than by seat, measured in Copilot Credits. From 1 December 2026 it is enabled by default on new Microsoft 365 Copilot Business licences bought through CSP, with a default limit of 4,000 credits per user per month that administrators can change. Your existing seat-based Copilot experiences are not affected; the metered list covers Cowork, Work IQ APIs, advanced work in SharePoint and OneDrive, Copilot Managed Runtime, Teams Phone Agent and Code.
Does this affect my existing Copilot licences?
No. Microsoft states that no action is required for existing subscriptions, and that product and SKU IDs, pricing, renewal terms, auto-renew settings and service all remain unchanged. The default applies to new Copilot Business purchases through CSP from 1 December 2026. Separately, the current add-on versions of Copilot and Copilot Business reach end of sale on the same date, but end of sale is not end of life and existing customers can continue to renew and adjust seat quantities.
What does a Copilot Credit cost?
Microsoft has not published a per-credit rate in its administrator documentation, and its Cost Management API explicitly excludes pricing and currency costs. The rate reported consistently across the partner community is one US cent per credit, which would put the 4,000-credit default at roughly $40 per user per month as a ceiling. Treat that as an unconfirmed working figure and ask your CSP partner for the sterling rate in writing. Of everything about Copilot usage-based billing, this is the detail most likely to catch a finance team out, because the limit is published in credits and the invoice arrives in pounds.
Is the UK affected on 1 December?
Yes. Microsoft lists the markets where the change is not available at launch as Australia, Belgium, Brazil, France, Germany, India, Italy, Korea, the Netherlands, Poland and Spain. The United Kingdom is not among them, so UK buyers of new Copilot Business licences through CSP are in scope from 1 December 2026.
How do I cap Copilot spending?
In the Microsoft 365 admin center under Copilot, then Cost management. Connect a billing method, create an identity-based spending policy covering who should have access, then set policy-level and per-user spending limits to a figure you have chosen. Two further steps matter: turn off Auto-apply new services, which is enabled by default and would otherwise extend your policy automatically to future metered services, and give finance a reader role so they can see consumption without being able to change policies. Doing all four before you buy is the cheapest version of Copilot usage-based billing governance there is.
This article was drafted with AI assistance and reviewed by the Transputec team. Featured image: AI-generated.
