For CSP partners, the transition to usage-based billing (UBB) for new commercial Microsoft 365 Copilot Business licenses introduces a critical operational distinction: the license purchase and the Azure consumption setup are separate events. According to the October Partner Center announcement, this default-on model for new B-SKU purchases is scheduled for December 1, 2026. The Partner Center mechanics article describes unreleased features, and some purchase and management API shapes may change before general availability.
The workflow begins at the Review Order screen, which discloses that an eligible SKU purchase creates and configures the required consumption artifacts and a default spending policy. The specific Azure path depends on whether the customer already has an Azure footprint with the purchasing partner.
Without that footprint, checkout is described as automatically creating and configuring 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 for Copilot consumption. The existing Azure Plan is reused rather than duplicated; if needed, the partner can select a different reseller’s Azure Plan from the one used for the Copilot license. That is the operational fork: an automatic setup for one customer can require an explicit destination choice for another.
The policy path has its own check. Partner Center creates a default spending policy only if none already exists. If a spending or billing policy exists from any channel or partner, it does not create a duplicate policy or duplicate consumption artifacts. The documented distinction is narrow: the system avoids creating another default policy and associated artifacts in that case.
Then there is the timing of completion. Provisioning happens asynchronously after checkout, so the 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. The described process is all-or-none for the consumption artifacts: they are either created and wired correctly, or none are until a retry succeeds.
That makes the license result and the UBB status separate facts to read. A completed license order, by itself, does not show whether the consumption artifacts have finished provisioning. The practical distinction for a partner is not a new pricing calculation; it is knowing which Azure target the documented flow attaches and whether the order confirmation reports UBB as Pending. As of Nov. 3, the default-on policy is announced for Dec. 1, while the mechanics page says the described features are unreleased and some API shapes are preliminary.
