Microsoft now plans to start default-on usage-based billing for eligible Microsoft 365 Copilot Business subscriptions bought through the Cloud Solution Provider (CSP) program in FY27 Q3, January–March 2027. The November 3, 2026 update replaces the previous planned start of December 1, 2026. Microsoft said partner feedback prompted the extra preparation time in its Partner Center announcement. The change builds on NeoTeo’s earlier coverage of planned usage billing for new CSP licenses.
Which Copilot Business purchases are covered
Microsoft’s documented model applies to commercial Microsoft 365 Copilot Business B-SKU offers bought through CSP. The listed exclusions are Microsoft 365 Copilot Enterprise, education and nonprofit offers, and GCC Low offers. Eligible CSP routes include direct partners, indirect resellers and distributors, and Partner Center APIs, according to Microsoft’s billing documentation.
The default-on change is tied to a new eligible purchase, whether it is a standalone offer or part of a bundle. Microsoft says that purchase will also enable usage-based billing by default for existing Copilot Business licenses in the same tenant. The initial usage-based experiences Microsoft names are Copilot Cowork, Work IQ APIs, and GitHub Copilot Harness.
Credits, spending controls, and billing records
Microsoft’s announced default limit is 4,000 Copilot Credits per licensed user per month. Administrators can adjust it. Microsoft describes the credits as a usage limit; the announcement does not assign them a dollar amount.
Microsoft’s Partner Center documentation describes spending controls that are still unreleased. Under those planned controls, setting the applicable limit to zero stops further usage spend. Deleting a spending policy stops future usage billing, but charges already incurred remain payable. Partner Center creates a default policy only if the customer has no existing spending or billing policy from any channel or partner. Microsoft says some API designs may change before general availability.
Usage charges are based on actual eligible consumption and appear in Azure CSP usage records, distinguishable from the Copilot Business seat subscription charge. The purchase and consumption setup are separate steps: Azure resources are provisioned asynchronously, so a qualifying license order can succeed while usage-based billing is still pending. If provisioning fails, it remains pending and can be retried. Microsoft’s unreleased documentation says Partner Center may create the Azure Plan, subscription, and resource group, or ask the partner to select or confirm the consumption destination, depending on the customer’s existing Azure relationship with that partner.
