Microsoft Delays Default Copilot Business Usage-Based Billing for CSP Partners to Early 2027

Microsoft's explanation was short: it said it had heard partner feedback and was moving the dates "to give you extra time to prepare for these upcoming changes and support your customers." It did not say what the feedback was. CRN, which first reported the delay, places it in a channel that is still working out which AI use a seat license covers, which use is metered, and how to explain that difference to a small business customer.

How the date has moved​

The original effective date was November 2, 2026. MSSP Alert, summarizing CRN's earlier reporting, noted that the original start date of Nov. 2 has been pushed to Dec. 1. At the time, the extra month was supposed to give solution providers new sandbox environments set to be released on Nov. 2.

That sandbox date has now slipped as well. Microsoft says it has moved the November 2 Partner Center sandbox date and has not set a new one. It promises to announce the date in advance, publish readiness guidance, and give partners at least 30 days of sandbox testing before default UBB reaches general availability.

Section summary: Nothing changes in December. The CSP default-on switch is now expected in early 2027, and the testing sandbox has no date at all.

Markets that were excluded are now included​

The geography of the rollout has quietly changed too. In the earlier plan, MSSP Alert reported, usage-based billing will initially roll out to supported markets, excluding countries like Australia, Belgium, and Germany.

The November 3 announcement reverses that. Microsoft now says the new sandbox and GA timelines apply across all markets. It names Australia, Belgium, Brazil, France, Germany, India, Italy, Korea, the Netherlands, Poland and Spain as places where these features were previously not expected at first. Partners in those countries had planned on a later start. They should now plan for the same early-2027 window as everyone else.

What changes when it does arrive​

The basics have not changed, only the timing. Once the rollout starts, new Microsoft 365 Copilot Business purchases through CSP will have pay-as-you-go UBB enabled by default. That includes standalone offers and bundles. Microsoft's announcement adds a detail that is easy to miss: a new purchase also turns on UBB by default for existing Copilot Business licenses in the same tenant. Some third-party explainers have said existing subscriptions are untouched. That holds only until someone buys new seats.

Specifics from Microsoft's Partner Center announcement and its preliminary documentation:

• Default spending limit: 4,000 Copilot Credits per user per month across eligible services. Admins can change it in Partner Center or the Microsoft 365 admin center. Microsoft's own example: a customer with 100 Copilot Business users could consume up to 400,000 credits a month under the default, but charges are based on actual use.
• Services covered: "eligible usage-based experiences" currently Copilot Cowork, the Work IQ APIs, and the GitHub Copilot Harness. Microsoft's documentation says more usage-based agents and services are expected over time.
• Automatic plumbing: Partner Center will create the required Azure Plan, subscription, resource group and a default spending policy at checkout. Partners currently do this by hand, with GDAP requests and admin center sign-ins. Microsoft's documentation estimates that about three in four Copilot Business customers sold through CSP have no Azure footprint today.
• Scope: Only Copilot Business B-SKUs in the commercial segment. Microsoft 365 Copilot (Enterprise), education, nonprofit and GCC Low are out of scope.

This is a real change from how things work today. According to Universal Cloud, until now, an administrator had to deliberately activate usage-based billing and a spending policy before anyone could use Copilot Cowork. The same publication notes that for larger organizations on full Microsoft 365 Copilot, Microsoft has not announced default pay-as-you-go. Microsoft's general Copilot pay-as-you-go documentation also still says pay-as-you-go billing is disabled by default.

Section summary: In early 2027, buying Copilot Business through a partner will also switch on metered AI spending for the whole tenant, capped by a default limit that you can change.

Spending controls: the fine print​

Microsoft's Partner Center documentation describes features that have not shipped yet. Its API details are labeled preliminary and could change before GA. Treat what follows as the current plan:

1. No duplicate policies. The default spending policy is created only if the tenant has no spending or billing policy from any channel or partner. If you already have one, Partner Center leaves it alone.
2. Two caps, first one wins. A policy can set a tenant-wide monthly cap, a per-user cap, or both. Whichever cap is hit first applies. The documented defaults for a new policy are 1,200,000 credits per tenant and 4,000 per user.
3. Least restrictive wins when policies overlap. If several policies apply to one user, the most generous one applies, and an unlimited policy always wins. Admins who layer policies should keep this in mind.
4. Stopping spend. Microsoft's announcement says partners can set the limit to zero to stop UBB spending. The documentation also says UBB can't be fully turned off once configured. One passage says limits can't go below a platform minimum and that deleting the policy is the only way to stop spend entirely. Those statements don't fully agree. Expect Microsoft to clarify this before GA, and don't build a runbook on either version yet.
5. Deleting a policy doesn't erase charges. Deletion stops future billing, but the tenant still owes for usage already accrued.
6. Advanced policies live in the admin center. Partner Center will only handle the default policy shape. Policies scoped to specific users or groups are managed in the Microsoft 365 admin center under Copilot > Cost management.

On invoices, Copilot UBB charges will appear in the existing Azure usage reconciliation files with Product, SKU and Meter IDs, separate from the seat charge. Because one seat purchase can enable UBB for the whole tenant, partners may see consumption charges they didn't expect for that tenant. The reconciliation identifiers are how you trace a charge back to the purchase that triggered it.

Inconsistent reporting on triggers​

Earlier reporting doesn't fully match the current documentation. One explainer citing CRN said additional seats added to an existing subscription, upgrades to Copilot Business, and subscriptions transferred from a prior solution provider will also arrive with usage-based billing on by default. Microsoft's current Partner Center documentation is narrower:

• Seat additions trigger UBB only through the Partner Center portal. Seat count changes made through the API do not.
• Upgrades to UBB-enabled SKUs don't automatically get the Azure resources or spending policies.
• After a partner-to-partner transfer, the new partner creates fresh spending policies.
• A Copilot trial that converts to a paid UBB-enabled SKU enables UBB at conversion.

Since the documentation is official but explicitly preliminary, partners should check trigger behavior in the sandbox once it exists.

Why Microsoft wants this, and why partners pushed back​

The commercial motive is clear. CRN reported from Microsoft's fiscal Q1 2027 earnings call that Satya Nadella said the number of Copilot customers actively using credits through UBB grew more than 75 percent in the quarter, and that agentic credit consumption at GitHub more than doubled. These are Microsoft's own figures, not independently audited. Nadella argued that consumption tied to agent work creates "business-funded demand." According to CRN, CFO Amy Hood expects customers to adopt consumption pricing more slowly than coding users have.

Microsoft's announcement itself includes a sales angle. It tells partners that early usage creates a natural path to expanded consumption and upsell conversations. It's fair to ask whether a default-on meter mainly helps customers use Cowork without friction, or mainly helps Microsoft's consumption numbers. The honest answer is probably both. Turning a meter on by default for small businesses, which often don't have a FinOps team, is the kind of change that ends in support tickets if nobody explains it beforehand.

That is where partners say they add value. Chris Miller, chief revenue officer of ATB Technologies, told CRN his firm helps clients understand AI consumption bills and works to avoid surprises like a $5,000 bill at the end of the month. He recommends starting with targeted Copilot rollouts to selected users, and argues that in some cases consumption beats licensing, because as many as 80 percent of users could be wasting a license. Miller also said he could imagine license-based AI offers eventually disappearing in favor of purely token-based pricing. That is his prediction, not Microsoft's stated plan.

What to do with the extra time​

Based on Microsoft's readiness guidance and the documented controls, here is a practical checklist for CSP partners and Copilot Business admins:

1. Recheck your dates. Microsoft tells partners to reassess anything scheduled around the November 2 or December 1 dates, including customer emails, training and price sheets.
2. Look for existing spending policies. If a tenant already has one, the default won't be created. Know which policy will actually govern spend.
3. Choose each customer's limit before rollout. The 4,000-credit default is a ceiling, not a recommendation. Decide whether it should be lower, zero, or scoped through the admin center.
4. Assign an owner. Name the person, on the partner side or the customer side, who watches Copilot Credit consumption and adjusts limits.
5. Prepare reconciliation. Make sure your billing team can find Copilot UBB lines in the Azure reconciliation files before the first invoice arrives.
6. Wait for the sandbox before automating. API shapes are preliminary. Hold off on Partner Center API integrations until the sandbox opens and you have at least 30 days to test.

Bottom line: Default-on UBB for new CSP Copilot Business subscriptions is now planned for January–March 2027 rather than December 1, 2026. The sandbox has no date yet, and markets such as Australia, Belgium and Germany are now included from the start. The controls are mostly defined, but parts of the documentation still disagree with each other, so use the extra time to plan and to pin Microsoft down on those details.