Microsoft is making pay-as-you-go the default billing model for new Microsoft 365 Copilot Business licences. It covers the usage-based experiences, including Copilot Cowork, Work IQ APIs and GitHub Copilot Harness, and it arrives with a default spending limit of 4,000 Copilot Credits per user per month that administrators can adjust. Existing subscriptions are unchanged. This is a quiet but real shift: a predictable per-seat subscription is becoming a consumption meter.
The date that applies to you is probably not the one you have read
There are two dates, and most coverage conflates them.
For direct purchases, the change is reported to begin October 19. That date comes from Microsoft 365 Message Center notice MC1476200, which sits behind admin sign-in, so publicly we are reading reproductions of it rather than the notice itself.
For CSP purchases, meaning you buy Microsoft licensing through a partner or your IT provider, which is how most small businesses buy it, Microsoft's own Partner Center announcements now say the change begins December 1, 2026, moved from a previously communicated November 2. A number of articles are still printing November 2. If you buy through a provider, December 1 is your date, and you have time to decide rather than discover.
Why a small business should care about a billing model
Because consumption pricing changes the risk profile of encouraging adoption. Under per-seat licensing, the worst case of telling your team to use Copilot more is that you paid for seats nobody used, which we wrote about in the services gap. Under usage-based billing, enthusiastic adoption has a variable cost attached, and the people generating that cost are not the people who see the invoice.
Credits are also an abstraction. Few owners will develop an intuition for what 4,000 credits buys, which means the first real signal is a bill. That is a familiar pattern for anyone who has run cloud infrastructure, and it is new territory for a business whose software costs have always been a fixed monthly line.
To be fair about the upside: metered pricing genuinely suits light and uneven usage, and it lets a small business try agent features without committing to a premium tier for everyone. The problem is not the model, it is inheriting its defaults without deciding.
What to actually do
- Find the control before the date. Microsoft 365 admin center, then Copilot, then Cost management. Look at it once now so you are not finding it in response to a charge.
- Set the spending limit deliberately. The default is 4,000 credits per user per month. Decide what you are willing to spend, per person and in total, and set it there rather than accepting the default.
- Know what opting out costs you. Usage-based billing can be disabled, but that removes access to the experiences that depend on it. That is a legitimate choice; it should be a choice.
- Confirm your date with your provider. If you buy through a CSP partner, ask them to confirm December 1 and what they will do about limits on your behalf. If you buy direct, assume the earlier date.
- Measure before you scale. Pick the one or two workflows where Copilot is genuinely saving time, and put a number on them. Under consumption pricing that measurement stops being a nice-to-have.
- Watch the first two invoices closely, then set a limit you would be comfortable paying every month without checking.
The takeaway
Nothing here is unfair or hidden, but it is a default being set on your behalf, and the gap between an organization that reviewed its spending limit and one that did not will show up as a number. Spend ten minutes in Cost management before your date, decide the ceiling, and tell whoever manages your licensing what you decided.