Microsoft moves M365 Copilot Business CSP usage-based billing default to 1 December 2026 and confirms 4,000-credit spending cap

A quick correction first

A previous post on this blog cited 19 October 2026 as the date CSP partners needed to watch for usage-based billing becoming the default on new Microsoft 365 Copilot Business subscriptions. That date was wrong for the CSP channel. On 1 October 2026, Microsoft published a corrected Partner Center announcement moving the CSP effective date to 1 December 2026. The 19 October date applies only to new purchases made directly through Microsoft, not through the Cloud Solution Provider programme. This post sets the record straight and adds the confirmed spending limit detail that was missing from earlier communications.

What has actually changed

Microsoft’s original September 2026 announcement (Message Center post MC1476200) introduced the concept: from a certain date, new eligible Microsoft 365 Copilot Business subscriptions would arrive with usage-based billing switched on by default, an Azure subscription automatically attached, and a default spending policy applied. The October update corrects two things.

First, the CSP effective date moves from 2 November 2026 to 1 December 2026. Partners and IT administrators who had been preparing for a November deadline now have an extra month.

Second, the default spending limit is now confirmed: 4,000 Copilot Credits per user per month. This was an open question after the September announcement. CRN’s reporting puts that figure at roughly $40 per user per month based on the pay-as-you-go rate of $0.01 per credit, though Microsoft has not published a dollar figure directly in the announcement itself.

What usage-based billing actually means here

It is worth being precise, because “usage-based billing is now the default” sounds more alarming than it needs to be.

Microsoft 365 Copilot Business is a fixed per-user licence covering what Microsoft calls everyday AI: Copilot in Word, Excel, Teams, Outlook, and so on. That does not change. What usage-based billing covers is a separate tier of more advanced AI workloads, specifically Copilot Cowork, the Work IQ APIs, and GitHub Copilot Harness. These consume Copilot Credits rather than being included in the flat licence fee.

From 1 December 2026, any new M365 Copilot Business subscription purchased through CSP will arrive with:

usage-based billing already enabled
an Azure subscription automatically created and linked
a default spending policy set to 4,000 Copilot Credits per user per month

The 4,000-credit figure is a ceiling, not a charge. A customer who never touches Copilot Cowork or the Work IQ APIs will not be billed anything under this mechanism. The cap simply limits how much metered usage can accumulate before further consumption is blocked.

For a customer with 100 licensed users, the default cap works out to 400,000 Copilot Credits per month across the tenant. At $0.01 per credit, that is a maximum exposure of $4,000 per month before the ceiling kicks in, assuming those third-party rate figures hold.

What this means for CSP partners

Partners selling M365 Copilot Business through the CSP programme should take note of a few practical points.

Existing subscriptions are not affected. Only new purchases made on or after 1 December 2026 will have usage-based billing enabled by default.

The limit is adjustable. Admins can raise or lower the spending limit per user in the Microsoft 365 admin centre under Copilot > Cost Management. It can also be set to zero, which effectively turns usage-based billing off for that tenant.

Partner Center sandbox testing from 2 November 2026. Microsoft has confirmed that Partner Center sandbox environments will support usage-based billing testing from 2 November 2026, giving partners a full month to get familiar with the mechanics before the December change goes live.

The Azure subscription is automatic. Partners do not need to provision anything separately. The Azure resources required for usage-based billing are created at the point of purchase. However, partners and customers should be aware that this means an Azure subscription will appear in the tenant even if the customer has never used Azure before.

What IT admins at customer organisations should do before December

If your organisation buys M365 Copilot Business through a CSP partner and you are planning any new licence purchases after 1 December 2026, there are five things worth doing before or shortly after that purchase.

Decide whether you want usage-based billing active at all. If not, set the spending limit to zero in the admin centre.
If you do want it active, review the default 4,000-credit limit per user and decide whether that is appropriate for your organisation.
Make sure your finance team knows an Azure subscription will be attached. Even a zero-balance subscription can trigger procurement or compliance questions if it appears unexpectedly.
Understand which workloads consume credits. At launch, that means Copilot Cowork, Work IQ APIs, and GitHub Copilot Harness. Everyday Copilot use in Microsoft 365 apps remains covered by the flat licence.
Check in with your CSP partner. They should be able to walk you through the admin centre controls before your next purchase.

The broader direction of travel

This change is part of a deliberate shift in how Microsoft is structuring Copilot billing. The flat per-user licence covers a defined set of AI capabilities. More advanced or compute-intensive workloads sit on top, billed by consumption. Microsoft is not hiding this: the October announcement describes pay-as-you-go as the intended default “to help customers access eligible usage-based experiences with less billing setup, while also providing flexibility to expand usage over time.”

That framing is accurate as far as it goes. The flexibility is real. So is the need to actively manage the spending controls if you want predictable costs. The default is not the configuration a cautious finance team would choose, so a brief admin centre review before or after any new purchase in December is time well spent.