Key takeaways
- From 2 November 2026, new Copilot Business licences bought through a Microsoft partner come with pay-as-you-go usage billing switched on by default.
- Usage billing pays for the advanced features, such as Copilot Cowork, that consume Copilot Credits on top of the per-user licence.
- Microsoft applies a preset monthly limit, but that is its number, not a budget your business approved.
- Three decisions close the gap: who can use the paid features, what the monthly and per-user limits are, and who receives the alerts.
Most businesses have always paid for Microsoft 365 the same way: a fixed price per user, per month. Copilot is moving part of that onto a meter. For a 15-person accounting practice in Frankston or a consulting firm in the CBD, that means a new line on the Microsoft bill that goes up and down with how your team uses the tool, and nobody in the business has yet decided how high it is allowed to go.
What is changing
In a September notice to its partners, Microsoft said that from 2 November 2026, new Microsoft 365 Copilot Business licences bought through its Cloud Solution Provider program, standalone or bundled, include usage-based billing by default. Pay-as-you-go is the default setting, and the Azure subscription needed to bill it is set up with the licence.
The per-user licence does not change. The meter covers the newer features that Microsoft charges for in Copilot Credits, currently led by Copilot Cowork, which takes on longer multi-step tasks, along with apps built with it and connections used by other software. Microsoft’s own documentation says more agents and services will be added over time.
Why the default is not a budget
Microsoft tells partners there is a preset monthly limit. It has not published that figure in its announcement, and it is Microsoft’s figure, not yours. Three details in Microsoft’s cost management guidance matter more than the number:
- The default policy covers everyone. Unless it is narrowed, every licensed user can spend credits.
- New services join automatically. A setting called “Auto-apply new services” is on by default, so future paid features are added to your policy as Microsoft releases them.
- A limit cuts access, not just spending. When a policy or person reaches its monthly limit, they lose those features until the credits reset on the first of the month. A limit set too low stops work; a limit set too high is a bill.
Three decisions to make before November
None of this needs a technical owner. It needs someone who owns the budget to answer three questions, and your IT provider to configure the answers.
- Who can use the paid features? Start with a named group, perhaps two or three people with a clear use for longer tasks, rather than the whole team. Microsoft’s controls scope access by group, so widening it later is easy.
- What is the monthly limit, and the limit per person? Set a business-wide ceiling you are comfortable seeing on the bill, and a per-person limit so one enthusiastic user cannot spend the lot. Microsoft recommends the per-user limit for exactly that reason.
- Who watches it? Alerts go by email when usage reaches a threshold. Send them to the person who approves the spend, not only to an administrator. A read-only reporting role lets a bookkeeper or practice manager see usage without being able to change settings.
While you are there, decide whether new services should join automatically. For most small businesses, reviewing each new paid feature before it is switched on is the safer default.
Why the timing matters
This lands in a busy buying window. Microsoft’s promotional pricing on standalone Copilot Business runs to 31 December 2026, so plenty of businesses will add Copilot in November and December, exactly when usage billing is on by default. If you are buying or renewing Copilot after 2 November, assume the meter is running until someone has shown you the limits.
It is also worth being clear-eyed about the incentives. Microsoft’s notice describes early usage to partners as a path to expanded consumption and upsell conversations. That is a normal commercial aim, and it is the reason the cap should be your decision rather than a default.
Where we fit
We are based in Mornington and look after businesses across Melbourne and the Mornington Peninsula. For clients whose Copilot licensing we manage through AgileAI, setting who can use these features, the limits and the alerts is part of the licensing and governance work, and it comes up again at each renewal. If you have not yet sorted out what Copilot can see in your files, start with preparing your Microsoft 365 permissions, because a usage cap controls cost, not access to data. If you would rather talk it through, start with a conversation.