Copilot Business is getting a meter. Here's what MSPs should set up before January.

Microsoft 365 Copilot Business has always been a licence: a fixed price per user per month, easy to quote and easy to bill. That is about to change for every client you sell it to through CSP.

In its November Partner Center announcement, Microsoft confirmed that usage-based billing will be on by default for new Copilot Business purchases in CSP from January to March 2027. It was originally due on 1 December, so partners have a few extra weeks to prepare.

What changes

Some Copilot experiences are now charged on usage, on top of the licence fee, measured in Copilot Credits. From the announcement:

• It's on by default. Microsoft creates the Azure resources needed for billing automatically, and pay-as-you-go is the default billing setup.
• One purchase changes the whole tenant. A new Copilot Business purchase also switches usage-based billing on for the Copilot Business licences already in that tenant.
• The default ceiling is high. The default spending limit is 4,000 Copilot Credits per user per month. Microsoft's own example: 100 Copilot Business users could consume up to 400,000 credits a month.
• Turning it off has a cost too. Disabling usage-based billing might limit access to the AI experiences your client is paying for.

Microsoft describes early usage as "a natural path to expanded consumption". That is a fair description from the vendor's side. From your client's side, it is a new variable bill that nobody has been asked to own.

The checklist

Spending limits can be adjusted in Partner Center or the Microsoft 365 admin center, and the spending policies themselves live in the admin center under Copilot > Cost Management (Microsoft Learn). Agree each point with the client before January rather than after the first bill.

1. List the affected clients. Every client buying new Copilot Business seats through you from January, plus any client with existing Copilot Business licences in a tenant where a new purchase is likely.
2. Replace the default limit with a deliberate one. Microsoft currently requires at least 2,000 credits per user per month for user limits and says its recommendations may change. Pick a number with the client rather than inheriting 4,000.
3. Choose limited or unlimited. A policy can have an unlimited or a limited monthly budget. With a limit, users who reach it lose access to the covered agents and services until credits reset on the first of the month. Decide with the client which outcome is worse: an overspend or a pause.
4. Set per-user limits. These stop one enthusiastic user from spending the whole policy's credits.
5. Turn on alerts. Policy-level alerts email the administrators and stakeholders you name when usage passes a threshold, and user notifications warn people as they approach their own limit. Put yourself on the list.
6. Review "Auto-apply new services". It's on by default, so newly supported Copilot services and agents join the policy, and start consuming credits, as Microsoft releases them. Turn it off where you'd rather review each new service first.
7. Decide how it's billed. Prepaid credits from capacity packs or pre-purchase plans are always used before pay-as-you-go. Global and Billing administrators can also bill a policy to a different Azure subscription, which is useful for departmental billing.
8. Plan the reporting. The cost management dashboard shows consumption, but Microsoft's Copilot Cost Management API reports usage in credits and doesn't include pricing, invoices or currency costs (Microsoft Learn). Turning credits into a number on your client's invoice is your job.

Who owns the bill

Microsoft's own next steps for partners include FinOps skilling, and for good reason. A licence was a procurement decision. A meter is an operating cost that needs limits, monitoring and someone to explain it every month.

That is the same job MSPs already do, or should be doing, for Azure. It's the reason we started Cerberus Cloud. Work through the eight steps above with each client now, and the first usage-based bill won't be a surprise in the spring.