New Microsoft 365 Copilot Business purchases will include automatic usage-based billing from 19 October 2026
From 19 October 2026, new Copilot Business licences include default usage-based billing for agentic AI. Admins need to act before then.
Microsoft has issued Message Centre notice MC1476200, flagged as a major change with admin and user impact. From 19 October 2026, any new Microsoft 365 Copilot Business licence purchased directly from Microsoft will automatically include a usage-based billing spending policy, covering agentic AI experiences such as Copilot Cowork. The same change applies to purchases through Cloud Solution Provider (CSP) channels from 2 November 2026.
If your organisation is buying new Copilot Business seats around or after those dates, this affects your billing set-up from day one.
What is actually changing
Until now, accessing usage-based AI experiences like Copilot Cowork required a separate billing set-up. With MC1476200, Microsoft is streamlining that: when you purchase a new eligible Copilot Business subscription, Microsoft will automatically create the required Azure resources and attach a spending policy that enables usage-based billing.
This does not change anything about your existing subscriptions. Licences already in place keep their current benefits and payment terms. If you already have a spending policy configured, it stays as-is.
For brand-new purchases made on or after the relevant dates, the spending policy is simply there by default, ready to go.
What Copilot Cowork is, and why billing works differently
Copilot Cowork reached general availability on 16 June 2026. It is an agentic capability: you describe an outcome, and Cowork executes multi-step work autonomously, sending emails, scheduling meetings, creating documents, posting in Teams, and managing files, all within Microsoft 365’s security and governance boundaries.
Because Cowork is autonomous and can run lengthy tasks, it does not fit neatly into a fixed-seat licensing model. Microsoft bills it using Copilot Credits, a metered unit priced at $0.01 per credit under pay-as-you-go. A light task might consume 100 to 300 credits (roughly $1 to $3), a medium task 300 to 700 credits, and a heavy task more than 700 credits. The exact consumption depends on which AI model runs the task, how much organisational context it retrieves, how many tools it calls, and how long it runs.
Copilot Credits are also the billing currency for Microsoft Copilot Studio, Power Platform workloads, and Work IQ APIs, so this spending policy covers more than just Cowork.
Importantly, no Cowork entitlements are bundled with a standard Microsoft 365 Copilot licence. Your existing licence still covers Copilot Chat and Copilot inside Word, Excel, PowerPoint, Outlook, and Teams. Cowork sits on top of that, billed separately in credits.
The detail admins need to pay attention to
The spending policy is attached automatically, but it does not mean usage is uncapped. Charges apply only when these experiences are used, and admins control the limits. The concern is that the policy also carries a setting called “Auto-apply new services”, which is enabled by default. That means any future Microsoft Copilot services or agents that become eligible for usage-based billing can automatically fall under the existing spending policy without an admin needing to approve each one individually.
That is a reasonable default for organisations that want frictionless access to new capabilities, but it is a risk for organisations that want tighter governance before any new agentic service starts accumulating charges.
The practical recommendation: before 19 October 2026 if you purchase directly from Microsoft, or before 2 November 2026 if you buy through a CSP, your billing administrator should log into the Microsoft 365 admin centre, navigate to Copilot > Cost Management, and review the spending policy settings. Specifically:
- Confirm or set organisational and per-user spending limits.
- Decide whether “Auto-apply new services” should remain on or be turned off for policies where you want manual review before new services are added.
- Set up threshold notifications so you are alerted before limits are approached, not after they are exceeded.
If you do not act, the policy will exist with whatever defaults Microsoft applies, and your organisation will be billed for any usage that occurs.
How to manage spending once the policy is in place
The Cost Management section of the Microsoft 365 admin centre gives admins a reasonably complete picture. From there you can monitor Copilot Credit consumption broken down by spending policy, group, user, agent, service, and funding source. You can also configure custom approval routing for credit requests, which is useful if you want employees to request access rather than having it open by default.
One nuance worth noting: the admin centre shows daily usage figures that can include non-billable consumption. The Azure bill reflects finalised, billable amounts at month close. Small discrepancies between the two views are expected. Use the monthly billing record for reconciliation, not the real-time dashboard.
On purchasing options, Microsoft offers two routes. Pay-as-you-go bills at $0.01 per credit based on actual consumption each month, with no upfront commitment. The Copilot Credit Pre-Purchase Plan is a one-year, pay-upfront option offering volume discounts and a prepaid pool of credits. Unused prepaid credits expire at the end of the annual term, so over-buying carries its own cost.
Who needs to do something before the dates
If your organisation will not be purchasing any new Copilot Business licences on or after 19 October 2026 (direct) or 2 November 2026 (CSP), this notice does not require any immediate action. Existing licences are unaffected.
If you are planning new seat purchases around those dates, the billing administrator and whoever owns AI governance in your organisation should review Cost Management settings before those purchases are made. The spending policy will be created automatically; what you control is the limits and rules that govern it.
The required admin roles are straightforward: Global administrators and Billing administrators can set billing methods and change how credits are funded. AI administrators and Licence administrators can create spending policies and configure limits and alerts.
Getting this in place before the first new licence lands is considerably easier than trying to reconcile unexpected charges after the fact.