By MD Jehad H.·September 27, 2026·4 min read·Operator playbook

Microsoft Copilot's usage-based billing default is coming

Drafted through my n8n + AI pipeline, edited by me.

Microsoft 365 Copilot Business is switching from a flat per-seat price to a metered add-on by default. New direct purchases get usage-based billing turned on starting October 19, 2026, and new purchases through resellers get it on November 2. Existing subscriptions are not touched, for now.

The base Copilot license still runs about $30 per user per month for the core chat experience. What changes is a second layer: pay-as-you-go credits for a set of newer features, switched on automatically unless an admin turns it off or caps it first.

What usage-based billing actually covers

The metered layer applies to Copilot Cowork, the Work IQ APIs, and the GitHub Copilot Harness, the parts of the product built for agents doing multi-step work rather than a single chat reply. Ordinary Copilot chat inside Word, Outlook, and Teams stays on the flat license. Microsoft sets a default monthly spending limit of $10 per user on the metered features, and that limit is on automatically for new purchases unless someone changes it.

Why this catches businesses off guard

It's opt-out, not opt-in. A new purchase ships with the spending cap already active, so nobody has to request it for it to start billing.
The rollout is staggered by purchase channel. Direct purchases from Microsoft flip on October 19, CSP reseller purchases flip on November 2. If you buy through a partner, your date is the later one.
It only hits new purchases right now. Renewing an existing per-seat license doesn't add this, but any new seat you add after the date does.

$30 per user per month, flat
One predictable line item
No separate credit balance to watch

The base license price doesn't move. What's new is a second, metered bill that starts pre-activated.

What to check before your next Copilot purchase or renewal

1
Find your purchase channel
Ask whoever buys your Microsoft licenses whether they come direct from Microsoft or through a CSP reseller. That decides whether October 19 or November 2 applies to you.
2
Check the admin center spending limit
The setting lives under billing in the Microsoft 365 admin center. Confirm whether it's set to the $10 default, a different cap, or turned off entirely.
3
Decide who actually needs the metered features
Copilot Cowork and the agent-style tools are the ones that rack up usage. If most of your team only needs chat inside Word and Outlook, they don't need the metered layer switched on at all.
4
Put a calendar reminder on the rollout date
Set a reminder for your specific date so someone checks the bill the following week instead of finding a surprise charge at month end.

If you're not ready, set the cap to zero

You can set the spending limit to $0 while you decide who needs metered access. That blocks the metered features from running at all until you raise it, which is safer than leaving the default cap active and finding out later who used it.

Does this change my existing Copilot Business subscription?

No. Microsoft says the rollout applies to new standalone and bundled purchases starting on the two dates above. Existing per-seat subscriptions keep their current billing unless you buy additional seats after the date.

What happens if we go over the $10 per user cap?

Metered features stop working for that user until the next billing cycle or until an admin raises the limit. It doesn't roll over into a surprise invoice on its own, but it does mean an agent-heavy workflow can quietly stop mid-month if nobody is watching the cap.

If you're running Copilot alongside other automation in your business, or trying to work out which AI spend actually needs a seat versus an API call, that's the kind of budget question worth walking through together.

Building something this should run inside?

Book a systems call

Keep reading