Copilot Usage Billing Starts 1 December: First Bill in January

Microsoft has moved the date. Usage billing for Copilot Business now switches on by default on 1 December, for new CSP purchases, rather than 2 November. What hasn't moved is the money. The default limit is 4,000 Copilot Credits per user a month, and a credit costs a cent. Do the sum, and it's up to $40 per user every month on top of the license.

That's a ceiling, not a forecast. But it's the number a customer's finance team will quote back at you.

What changes on 1 December?

Any new Microsoft 365 Copilot Business license purchased through CSP, whether alone or in a bundle, will arrive with pay-as-you-go usage billing already enabled. Microsoft sets up the Azure subscription it needs at the time of purchase. The seat license doesn't change, and neither do existing subscriptions: this is for new purchases only. At launch, it isn't available in 11 markets, among them Germany, France, the Netherlands, Belgium, Italy, Spain, and Poland. Same day, the current "(add-on)" Copilot offers reach the end of sale, and new offers, with their own SKU IDs, take over.

If you read our June post on Copilot Cowork, this is that usage billing, now at the point of sale. The same usage billing also covers Work IQ APIs and GitHub Copilot Harness. In dollars:

Ceilings, not forecasts. Credits multiplied by $0.01, Microsoft's pay-as-you-go price. Partners can lower both limits in Partner Center. The tenant limit is reached at 300 users on the default limits.

Why does the first bill catch people out?

Three reasons, and the first is the one that bites.

• It arrives a month late. Usage is billed after the month closes, so December's usage is billed in January. By the time finance sees a charge, the spending is done.
• Most customers have never had an Azure bill. Microsoft's own figure: roughly three in four Copilot Business customers sold through CSP have no Azure footprint today. They'll now get an Azure subscription at purchase, and a meter running on it.
• It comes as its own line. Microsoft's usage reconciliation files show it separately from the seat charge.

What should a CSP partner do before 1 December?

• Set the limit on purpose. You can change the defaults in Partner Center, and zero stops the spend altogether. Worth having for the customer who doesn't want usage billing.
• Decide what you charge for credits: Microsoft's price, a margin on top, or an allowance inside the seat price. Decide once, not customer by customer.
• Tell the customer's admin and their finance contact. Admins can set alerts and see who is close to a limit in the Microsoft 365 admin center. Finance needs to hear that the first charge turns up a month late.
• Test the line before it matters. Microsoft opens the Partner Center sandbox for this on 2 November. Check the usage shows up in your billing, and on your customer's invoice.

What is Cloudmore doing about it?

Copilot usage is billed on an Azure plan, and today Cloudmore bills that kind of usage only for organizations that have the Azure service with us. Most Copilot Business customers are in the other camp, so that isn't good enough, and we're changing it.

The usage lines will be treated as part of the customer's Microsoft 365 service in Cloudmore. You won't need to add Azure to bill them. You'll be able to set a price for Copilot Credits, much as you do for Azure consumption now. We don't expect ordering to change, and we'll confirm that in Microsoft's sandbox once it opens.

On timing: we're aiming to have the billing foundations in place around the start of December. Usage is billed in arrears, so the first Copilot usage should be reflected in the invoices you receive in January. Microsoft has published little technical detail so far, so expect some of this to shift once the sandbox opens. One gap for now: spending limits are set in Partner Center or the Microsoft 365 admin center, not in Cloudmore.

Please tell us how you want to price it. If you're a Cloudmore partner, tell your account manager two things: how you plan to price Copilot Credits, and roughly how many Copilot Business licenses you expect to sell after 1 December. Both decide what we build first.

Frequently asked questions

When does usage-based billing become the default for Copilot Business in CSP?

On 1 December 2026, for new purchases of Microsoft 365 Copilot Business through CSP. Microsoft originally set 2 November and has since moved it. The Partner Center sandbox for the change opens on 2 November.

What is the default Copilot usage limit?

4,000 Copilot Credits per user per month, and 1,200,000 per tenant. At $0.01 a credit, that is up to $40 per user and $12,000 per tenant. Partners can lower the limits in Partner Center, including to zero.

Does a customer need to buy Azure to use Copilot Business?

No, the seat license does not need Azure. For usage billing, Microsoft sets up the Azure subscription it needs at the point of purchase.

Sources and further reading

• Partner Center announcements, October 2026, Microsoft Learn: the 1 December date, the default limit, the 2 November sandbox, the markets not available at launch, and the Copilot offer changes
• Usage-based billing for Copilot Business in Partner Center, Microsoft Learn: tenant and per-user limits, setting a limit to zero, the reconciliation files, and the three-in-four figure
• Copilot Credits, Microsoft licensing guidance: $0.01 per credit, billed after the month closes
• Understand usage-based billing and cost management for Copilot Credits, Microsoft Learn: spending limits and alerts for admins
• Related reading: Copilot Cowork Is Live. For CSP-Managed Customers, So Is a Billing Wall.

Dates, limits, and prices taken from Microsoft Partner Center announcements, Microsoft Learn, and Microsoft licensing guidance as of 21 October 2026. Dollar figures are Copilot Credits multiplied by $0.01 and are ceilings, not forecasts. Cloudmore roadmap items and timings are indicative and may change.