Microsoft 365 Copilot Business: Usage-Based Billing Defaults for New CSP Purchases on December 1
Microsoft has updated its Partner Center announcement: from 1 December 2026, usage-based billing (UBB) will be enabled by default for new Microsoft 365 Copilot Business subscriptions purchased through CSP. The sandbox is scheduled to be available on 2 November for partner testing.
What changed
The default billing configuration for new Copilot Business purchases—including standalone offers and bundles—will include the Azure subscription setup needed for usage-based billing. Microsoft says the change is intended to reduce setup friction for eligible usage-based experiences such as Copilot Cowork, Work IQ APIs, and GitHub Copilot Harness.
The effective date was updated from the previously communicated 2 November to 1 December 2026. Microsoft also states that the default spending limit will be 4,000 Copilot Credits per user per month; customer administrators can adjust that limit. Initial rollout excludes Australia, Belgium, Brazil, France, Germany, India, Italy, Korea, the Netherlands, Poland, and Spain, with availability to expand later.
Why CSP partners should care
- Provisioning is now a billing decision: a new Copilot Business order can introduce consumption billing without the multi-step setup your current workflow may expect.
- Customer expectations must be explicit: explain the default 4,000-credit monthly limit, actual-usage charging, supported scenarios, and market availability before the customer accepts a quote.
- Portals and invoices need a new path: reseller portals, approval flows, invoice descriptions, payment collection, and reconciliation must distinguish license charges from Copilot Credit consumption.
- Timing matters: sandbox testing begins 2 November, but production default-on behavior starts 1 December. Do not treat sandbox results as evidence that every production market is enabled.
Operational checklist
- Map affected orders. Identify every standalone and bundled Copilot Business SKU, new-sale workflow, renewal flow, and reseller portal path in your catalog.
- Test the sandbox. When available, exercise order creation, Azure subscription association, UBB configuration, credit-limit changes, cancellation, and failure handling. Record request and response evidence.
- Version market rules. Add an explicit market-availability rule and a 1 December effective-date boundary. Keep excluded markets from being presented as ready by default.
- Rework customer consent. Update quotes, terms, approval screens, and reseller guidance to state that charges are based on actual Copilot Credit usage and that administrators control the monthly limit.
- Close the reconciliation gap. Confirm how usage-based charges arrive in Partner Center data, how they map to customers and resellers, and how exceptions are held for review before invoicing.
- Prepare support runbooks. Give service desks a path for questions about credit consumption, limits, market availability, and disputes without confusing UBB with the underlying seat license.
How Tagydes helps
Tagydes gives CSP operators a controlled path from Microsoft offer data to reseller quoting, ordering, customer billing, and reconciliation. Deterministic pricing rules can keep SKU, market, effective date, billing model, and credit-limit guidance explicit instead of scattering assumptions across portal code and spreadsheets.
- Controlled catalog rules: apply versioned offer and market logic across provider and reseller portals.
- Billing separation: keep recurring license charges and usage-based consumption visible in customer-facing workflows and invoice review.
- Operational evidence: retain rule traces and reconciliation context so a disputed charge or failed provisioning step can be investigated.
Source
Microsoft Partner Center announcements — Update: Usage-based billing is default on for new Microsoft 365 Copilot Business licenses
Microsoft Learn announcement dated 1 October 2026; effective date updated to 1 December 2026.