For CSP partners, Microsoft’s upcoming usage-based billing for new commercial Microsoft 365 Copilot Business licenses separates the license purchase from Azure consumption setup, according to an October Partner Center announcement scheduling the default-on model for new B-SKU purchases for December 1, 2026. The workflow begins at the Review Order screen, which discloses that an eligible SKU purchase creates and configures required consumption artifacts and a default spending policy. Without an existing Azure footprint with the purchasing partner, checkout automatically creates and configures the Azure Plan, subscription and resource group needed for consumption; with an existing partner Azure footprint, the partner is prompted to select or confirm the reseller MPNID, Azure subscription and resource group, and the existing Azure Plan is reused rather than duplicated. Partner Center creates a default spending policy only if none already exists, and does not create a duplicate policy or duplicate consumption artifacts if a spending or billing policy exists from any channel or partner. Provisioning happens asynchronously after checkout, so order confirmation can show a usage-based billing status such as Pending; if creation of the Azure Plan, subscription, resource group or spending policy fails, the license purchase still succeeds while consumption provisioning enters a pending, retryable state.