Microsoft’s latest update to Microsoft 365 Copilot Business marks an important shift in how AI services will be purchased, activated and managed. Starting December 1, 2026, usage-based billing will be enabled at the tenant level when customers purchase new Microsoft 365 Copilot Business licenses.
At first glance, this may look like a billing configuration change. In practice, it signals something larger: Microsoft is moving toward a hybrid model in which the core Copilot license covers everyday productivity, while advanced and agentic experiences can scale through consumption.
Generally available examples include Copilot Cowork, Work IQ APIs, GitHub Copilot Harness and long-running agentic capabilities such as Copilot in SharePoint. Code and Autopilot are also included through Microsoft’s Frontier Early Access Program.
For MSPs, the opportunity is not simply to explain a new charge. It’s to help customers adopt AI with the right guardrails, financial visibility and business outcomes in place.
What Microsoft is changing
The change applies to more than a first-time purchase. Usage-based billing will also be enabled when customers:
- Add Copilot Business seats to an existing subscription
- Upgrade to a Copilot Business SKU
- Receive a new subscription as part of a partner-to-partner transfer
Microsoft will automatically set up an Azure subscription with a default spending policy capped at 4,000 Copilot Credits, approximately $40 USD, per user per month. Billing is pay-as-you-go, so customers are charged for their actual usage within that policy. Usage can exceed the default amount only if an administrator changes the spending policy.
The update covers all B-SKU purchases that include Copilot:
- Microsoft 365 Copilot Business
- Microsoft 365 Business Premium with Copilot
- Microsoft 365 Business Standard with Copilot
- Microsoft 365 Business Basic with Copilot
Microsoft’s goal is to remove the separate Azure billing setup that previously stood between customers and usage-based Copilot products. Customers that only want seat-based capabilities can have an administrator turn off usage-based experiences, such as Cowork, in the Microsoft 365 admin center so they are not discoverable by end users.
What this means for MSPs
1. Copilot conversations now need to include consumption governance
A licensing discussion is no longer complete if it stops at seat count and subscription price. MSPs should distinguish seat-based capabilities from usage-based experiences, explain which common purchasing events enable the billing model and confirm whether the customer wants those experiences discoverable to end users.
2. Customer onboarding becomes easier, but responsibility increases
Automatic Azure subscription setup removes technical friction and helps customers reach advanced AI experiences faster. It also means MSPs need a repeatable process to review the default 4,000 Copilot Credits per-user monthly cap, confirm who needs access and decide whether any usage-based experiences should be disabled before they become discoverable.
3. Managed services can expand beyond licensing
Usage monitoring, budget reviews, policy optimization, adoption guidance and business-value reporting can become part of an ongoing Copilot service. The MSP’s role evolves from reseller to AI operations and governance partner.
4. Forecasting will require a different mindset
Fixed licensing offers predictability; consumption introduces variability. MSPs should help customers build usage assumptions, decide whether the preset cap is appropriate and connect any decision to raise it with measurable business outcomes.
5. Early adoption can create a broader growth opportunity
Initial usage can provide a natural path to expanded consumption, more informed upsell conversations and eligibility for the Copilot Cowork activation incentive. MSPs that help customers start with the right use cases can turn early value into a longer-term adoption and growth motion.
How MSPs should talk about the change
The way you introduce this change matters. Starting with the billing details before explaining what customers gain access to can create hesitation before they’ve seen the full picture.
Here’s how I’d frame it:
“Microsoft is simplifying access to advanced Copilot experiences by setting up the required Azure subscription when eligible Copilot Business licenses are purchased. Your organization will pay only for actual usage within a default cap of 4,000 Copilot Credits per user per month. The limit only increases if your administrator changes the spending policy. If you only want the capabilities included with the seat license, usage-based experiences can be turned off. We will help you choose the right model, set appropriate controls and monitor value over time.”
You should lead with four principles:
- Clarity: Separate included seat-based capabilities from metered experiences such as Cowork, Work IQ APIs, GitHub Copilot Harness and long-running agents.
- Control: Explain that administrators can keep the default limit, adjust the spending policy or disable usage-based experiences entirely.
- Value: Introduce consumption for defined use cases, not as an open-ended experiment.
- Accountability: Agree on who will monitor usage, review spend and measure outcomes.
What MSPs should do next
1. Review Microsoft’s partner resources
Review the UBB for SMB partner opportunity presentation and the UBB Default On FAQ to prepare sales, technical and customer success teams for the change.
2. Update sales and onboarding motions
Add the automatic Azure subscription setup, pay-as-you-go model, default credit cap, usage-based feature choices, spending policy options and ownership of monitoring to discovery calls, proposals, implementation checklists and customer success plans.
3. Create a governance baseline
Before enabling broad adoption, decide whether usage-based experiences should be available, review whether the default 4,000 Copilot Credits per-user monthly cap is appropriate, define approved user groups, establish a review cadence and escalation path and confirm how usage and spend will be reported.
4. Start with measurable use cases
Select a small number of scenarios with clear business value, then expand based on results rather than availability alone.
5. Build a recurring optimization motion
Review adoption, consumption, cost and outcomes with customers regularly. Adjust policies as usage matures.
Insights on usage-based billing from Sherweb’s Microsoft experts
Nikhil Fernandes, Product Manager for Microsoft 365, Copilot and Google Workspace at Sherweb, on what this shift means for partners.
Usage-based billing is a natural step in the evolution of business AI. As Copilot expands from individual assistance into longer-running, autonomous and agentic work, a single fixed-price model cannot represent every type of value or resource consumption.
The real risk is not consumption itself. It is unmanaged consumption without clear ownership, guardrails or outcome measurement. MSPs are well positioned to close that gap. Those that combine licensing expertise with governance, adoption and cost optimization will be more valuable to customers than those that treat this as another product update.
Need help preparing your customers?
If you have questions or need support navigating this change, get in touch with the Sherweb team. We would be happy to help assess the impact, establish the right controls and prepare you for the transition.
