Microsoft 365 Copilot Business CSP Billing Defaults to 4,000-Credit Cap on December 1, 2026

CRN reports that November 2 still matters. On that date Microsoft will open Partner Center sandbox environments so solution providers can get their systems ready and test the billing flow before it goes live. Microsoft also changed its "Copilot in 30" trial and added more workloads to its Copilot Credits Guide.

What's changing, and for whom​

The core change is simple. Before, an admin had to turn on usage-based billing before anyone could use the metered Copilot features. Now new licenses ship with it already on. Universal Cloud, a CSP that wrote about the original November plan, said that until now, an administrator had to deliberately activate usage-based billing and a spending policy before anyone could use Copilot Cowork.

Microsoft's announcement says the change applies to new purchases of Microsoft 365 Copilot Business licenses, including standalone offers and bundles. CRN cites Microsoft's updated FAQ for more detail. These purchases are covered:

• New Copilot Business subscriptions, including Microsoft 365 Business Premium with Copilot, Business Standard with Copilot, Business Basic plus Copilot Business, and other "B" variants
• Additional seats added to an existing Copilot Business subscription
• Upgrades to Copilot Business licenses
• Subscriptions taken over from a customer's previous solution provider after the start date

Existing seats that you don't touch aren't on that list. Buying more seats or upgrading does pull you in, though.

CRN lists the metered services as Copilot Cowork, Work IQ APIs, GitHub Copilot Harness, Copilot in SharePoint, and other long-running agentic features. Some limited-access Frontier Early Access tools are also metered, including Code and Autopilot (formerly Scout). Microsoft's management documentation says it is adding more services over time, so treat this as a current list, not a final one.

Section summary: For CSP purchases, the default-on date is now December 1. It applies to new purchases, added seats, upgrades and partner transfers. It does not switch every license you already have.

The direct-purchase date is different​

Microsoft's CSP announcement doesn't say this, but consultancy EPC Group does. It reports that Message Center notice MC1476200 (September 21, 2026) makes usage-based billing the default for eligible new Microsoft 365 Copilot Business purchases made directly from Microsoft starting October 19, 2026. If that's accurate, the delay only covers the partner channel. Tenants buying directly from Microsoft would reach default-on about six weeks earlier.

The 4,000-credit cap, and what it isn't​

The biggest new detail is the default limit. Microsoft says the default spending limit will be 4,000 Copilot Credits per user per month, which can be adjusted by admins. CRN puts that at about $40 per user per month. Microsoft didn't give a dollar figure in its announcement, so that conversion is CRN's.

Earlier partner coverage had different numbers. When Schneider IT Management wrote up the November plan, it noted that the change comes with a preset monthly limit, and the announcement does not state its amount. Stoneridge Software reported a smaller figure: a default pay-as-you-go spending limit of $10 per user, per month. Microsoft's official number is now 4,000 credits. If CRN's conversion holds, that's roughly four times what some partners were telling customers. Any budget built on the $10 figure needs a second look.

The cap is a ceiling. Customers are not billed the cap amount. Microsoft's example: a customer with 100 M365 Copilot Business users could consume up to 400,000 Copilot Credits per month under the default spending limit, with UBB charges based on actual usage.

CRN reports that Microsoft gave a sample month of usage that fits within 4,000 credits:

• four weekly Cowork meeting-prep and follow-up sessions
• four weekly inbox-triage sessions
• four weekly commit and pipeline risk reviews
• two RFP responses with compliance matrices
• one branded pitch deck
• PTO backfill documents twice a year

Your usage may look nothing like this, so don't budget from it.

Partners can set the limit to zero to turn off usage-based billing, CRN says. Microsoft hasn't added a way to do that across all customers at once. It's tenant by tenant, although partners can script it through the purchase and spending-policy APIs.

Section summary: The default cap is 4,000 credits per user per month (about $40, per CRN). Billing is for actual use, partners can set the cap to zero, and teams that planned around the earlier $10 figure should recheck their numbers.

Azure setup now happens automatically​

According to the FAQ as reported by CRN, an Azure subscription is now created as part of the Copilot Business purchase. Before, partners set one up only when they wanted metered billing. A customer with no Azure presence gets an Azure plan, subscription, resource group and default spending policy. If a customer already has an Azure subscription, the partner can bill to it. If the partner doesn't pick one, a new subscription is created. The billing subscription can be changed later by editing the spending policy.

For partners, CRN reports:

• Purchase APIs don't change. Catalog APIs get a new property showing whether a Copilot product has usage-based billing on.
• A new API lets partners enable and edit the spending policy created at purchase.
• Partners who aren't ready with API changes can still sell. They can edit policies in the Partner Center portal after the purchase.
• The partner carries the financial risk. Metered charges appear on the CSP invoice, and the transacting partner is responsible for all charges on that account, including usage nobody expected.

That last point is the one partners should take to their finance teams. If a customer runs up an unplanned Cowork bill, the partner who transacted the sale is billed first.

How admins control spending today​

The controls are already documented. Administrators manage usage-based billing in the Microsoft 365 admin center under Copilot > Cost Management. Microsoft Learn describes the process to add a spending policy:

1. Go to Copilot > Cost Management and open the Configuration tab.
2. Select + Add spending policy and name it.
3. Set the scope. It defaults to All users. Individual users have to be added through security groups.
4. Pick the agents and services the policy allows. Auto-apply new services is on by default. Turn it off if you don't want future services added to the policy automatically.
5. Set limits and alerts. Choose an unlimited or limited monthly budget. You can also set an optional per-user limit and alert thresholds for admins and users.
6. Pick a model profile (only for Cowork right now) and a billing method. Global or Billing admins can choose a different Azure subscription or capacity packs.
7. Review the settings and select Create spending policy. It applies to the scoped users right away.

Microsoft labels the per-user limit optional but recommends it: review and set this option for your organization to prevent runaway spending of Copilot Credits by one individual user. Universal Cloud also points out that Cowork itself by default it is available to all users. Restricting who can install the agent and who can spend credits are separate settings. Ideally both point at the same security groups.

A few details from Microsoft's documentation:

• Users in more than one policy get the policy with the highest per-user limit. Ties go to the larger total limit, then to the newest policy. Settings from different policies are never combined.
• Moving a user to another group mid-month doesn't reset their usage. Credits already used count against the new policy's limit.
• When a limited budget runs out, users lose access to the covered services until credits reset on the first of the month. Prepaid credits are always used before pay-as-you-go.
• Users can type /cost in Cowork to see roughly how many credits they've used. Microsoft says this is an estimate, not a billing record, so reconcile against the invoice.

CRN also reports that users who hit their limit can request more from inside the app, and an admin approves or denies the request. To keep metered features off entirely, the FAQ says admins can leave Copilot Credits off in the admin center, skip creating spending policies for these services, and check Cost Management regularly.

Which countries are left out at first​

Microsoft says the rollout starts in "supported markets" but hasn't published that list. It did name the exceptions. Default-on billing initially won't reach Australia, Belgium, Brazil, France, Germany, India, Italy, Korea, the Netherlands, Poland or Spain. Microsoft says it will share more as availability expands. A partner with customers in Germany and the U.S. could end up running two different billing setups for a while.

Copilot in 30 trial: new customers only​

CRN reports that Microsoft changed the "Copilot in 30" trial, which gives 25 users 30 days of Copilot access, so that only customers new to Microsoft 365 Copilot qualify. The updated document says customers with existing Copilot seats are not eligible. The September 23 version had said both new and existing customers might be eligible. It only asked partners to prioritize new ones.

Microsoft's Copilot Credits Guide now also covers Copilot Code, Copilot in SharePoint and Teams Phone Agent. It already covered Cowork, Work IQ APIs, Copilot Studio, Copilot Managed Runtime and business applications.

Analysis: a little more time, a lot more to configure​

Microsoft frames this as making setup easier for partners. CRN notes the change fits Satya Nadella's stated plan of a license plus consumption pricing model. That's not unreasonable. Cowork was hard to try when billing had to be set up first. Chris Regan of B&R Business Solutions told CRN that teaching clients about consumption pricing is "definitely a new revenue stream for us."

The counterpoint: once billing is on by default, someone has to deliberately turn it off. A $40-per-user ceiling across 100 seats is $4,000 a month in possible spend that nobody signed off on, and the transacting partner is liable for it. Whether that's acceptable depends on how carefully partners use the extra four weeks.

Before December 1:

• Test in the sandbox from November 2, especially automated purchase and policy scripts.
• Decide your default stance for each customer: zero cap, the 4,000-credit default, or a custom limit.
• Turn off Auto-apply new services wherever newly metered features need sign-off first.
• Line up Cowork access and spending policies to the same security groups.
• Check market eligibility for customers in the excluded countries.
• Update trial pipelines. Existing Copilot customers no longer qualify for Copilot in 30.

Bottom line: For CSP sales, default-on billing now starts December 1. The default cap is 4,000 credits per user per month, and the partner is billed for any overage. Use the extra month to set policies so unexpected charges don't land on the invoice.