Copilot Business Usage-Based Billing: What Microsoft's CSP Guidance Confirms

Why this matters for SMB admins and CSP partners

If your organization buys Microsoft 365 Copilot Business through a Cloud Solution Provider (CSP) partner, a change is underway that affects how consumption-based AI features — like Copilot Cowork — get billed. Instead of requiring a partner to manually set up Azure billing infrastructure before a customer could use consumptive Copilot experiences, Microsoft’s Partner Center documentation describes new Copilot Business CSP purchases as including usage-based billing (UBB) automatically, with a default spending policy created at the time of purchase.

For SMB decision makers, this matters because it changes how Copilot consumption gets enabled and controlled from day one, and it introduces default spending limits that affect cost exposure if left unreviewed. This article looks specifically at what Microsoft’s supplied documentation confirms — and doesn’t confirm — about the rollout date, the default limits, who can change them, and where they’re configured.

What the Microsoft documentation actually confirms

Usage-based billing is on by default for new CSP purchases

According to Microsoft’s Partner Center documentation, new Microsoft 365 Copilot Business licenses purchased through the CSP program include usage-based billing by default. When a partner completes a qualifying purchase, Partner Center automatically provisions the required Azure artifacts (an Azure Plan, subscription, and resource group) and creates a default spending policy, rather than requiring the partner to manually wire up Azure Cost Management afterward.

This applies specifically to the Copilot Business segment (so-called “B-SKUs”), not Microsoft 365 Copilot (Enterprise). It’s also limited to the commercial segment — education, nonprofit, and government community cloud (GCC) low offers are explicitly out of scope at launch. The SKUs covered include Microsoft 365 Copilot Business on its own, as well as several bundled offers that combine a Microsoft 365 base plan (Business Basic, Business Standard, or Business Premium) with a Copilot Business add-on.

The December 1, 2026 date — and what isn’t confirmed

The Partner Center documentation references an earlier Microsoft announcement through a link whose text reads: “usage-based billing is default on for new Microsoft 365 Copilot Business licenses starting December 1, 2026.” This is the only place December 1, 2026 appears in the supplied source material.

Importantly, the supplied sources do not mention November 2, 2026 at all, and they do not describe this as a postponement, delay, or date change from an earlier default. The content brief’s premise — that the default date moved from November 2 to December 1, 2026 — is not confirmed by the documentation reviewed for this article. SMB admins and partners should treat December 1, 2026 as the date referenced in Microsoft’s current guidance, but should not assume a prior date was officially announced and then pushed back unless they can verify that directly against Microsoft’s original announcement content.

Practical recommendation: If the exact rollout timing affects your budgeting or your partner’s customer communications, confirm the current effective date directly with your CSP partner or against Microsoft’s official announcement page before making decisions based on a specific calendar date.

Default spending policy: limits and scope

Microsoft’s documentation describes the default spending policy created automatically at purchase time with the following documented default values:

• Tenant limit: 1,200,000 credits per month, by default
• User limit: at least 4,000 credits per user, per month, by default
• Scope: the default policy created through Partner Center targets all users and the services it’s configured for (for example, Copilot Cowork)

A spending policy is the mechanism that controls who can consume Copilot Credits, how much an individual user or the tenant as a whole can spend per month, and which services the policy covers. According to the documentation, a policy can enforce a monthly cap at the tenant level, a per-user level, or both — whichever limit is reached first takes effect. When a user is covered by more than one applicable policy, the least-restrictive one applies, and if any policy covering that user is unlimited, the unlimited policy wins.

It’s also worth understanding how these policies can be stopped. Microsoft’s documentation states that usage-based billing can’t be fully turned off once configured — instead, the applicable spending limit can be set to zero to halt further spend, or the policy can be deleted. Deleting a policy stops future billing immediately, but the tenant remains liable for usage already accrued before deletion.

Who can adjust the limits — and where

The supplied sources describe two different places where usage-based billing can be managed, depending on whether you’re a CSP partner or a tenant administrator.

For CSP partners: Partner Center

Partners manage usage-based billing for a customer from a dedicated Consumption > Manage usage-based billing area within the customer’s subscription management experience in Partner Center, available through both the user interface and equivalent APIs. From there, partners can:

• Create a spending policy if the customer doesn’t already have one (specifying the consumption subscription, resource group, reseller MPNID, policy name, tenant limit, user limit, and applicable services)
• Change the consumption target (Azure Plan, subscription, or resource group)
• Adjust tenant-level and per-user spending limits, subject to platform-enforced minimums
• View an Active Spending Policy list and a separate Usage metrics view showing configured limits against current- and prior-month consumption

According to the documentation, Partner Center’s UI and APIs only support creating and managing the default policy shape — a tenant-wide and per-user limit structure. Roles noted as appropriate for this Partner Center experience are Admin agent, Billing admin, and Sales agent.

For more advanced policies: Microsoft Admin Center (MAC)

If a business needs something more granular than the default tenant/user-limit shape — for example, a policy scoped to specific users or specific groups rather than everyone — the documentation directs partners and admins to the Microsoft Admin Center (MAC), under Copilot > Cost management. Microsoft’s documentation notes that Partner Center is expected to converge further with this Cost Management experience over time, but until then, MAC is where anything beyond the basic default policy shape is configured.

For tenant admins: Microsoft 365 admin center roles

Separately, Microsoft’s admin-facing documentation for setting up usage-based billing describes specific administrative roles and what each can do within the Microsoft 365 admin center’s Copilot > Cost Management dashboard:

• Global administrator and Billing administrator can add, select, and change billing methods, and can create and configure spending policies.
• AI administrator and License administrator can edit existing spending policies, manage limits and alerts, and manage billing methods — but according to the documentation, they cannot create new spending policies.
• AI Reader, Global Reader, License Administrator, and other supported reader-based roles have read-only access to consumption dashboards and reports; they cannot create or change policies, limits, alerts, or billing methods.

Microsoft’s documentation also recommends using roles with the fewest permissions necessary, reserving Global administrator for situations where no more limited role fits, rather than as a default working role for this task.

Setting up the default policy in the admin center

For organizations managing their own setup rather than relying entirely on a CSP partner’s defaults, Microsoft’s documentation describes an activation flow in the Microsoft 365 admin center:

1. Sign in with a Global administrator or Billing administrator role and navigate to Copilot > Cost Management.
2. Select Get Started to begin activating the default spending policy.
3. Choose a billing method (the Azure subscription used for billing Copilot credit usage).
4. Set a monthly spending limit for the policy as a whole — either unlimited or a defined monthly credit cap.
5. Optionally set a per-user monthly limit. The documentation notes this step is optional but recommends reviewing and setting it to avoid one person consuming all available credits.
6. Configure alert recipients and thresholds for usage notifications.
7. Review the Auto-apply new services setting, which is turned on by default and automatically adds future supported Copilot services to the policy.
8. Optionally customize the policy’s scope (for example, specific groups) before activating.

Practical recommendation: Given that the per-user limit step is optional but directly affects cost exposure, SMB admins should treat setting a per-user limit as a priority task during initial setup rather than leaving the policy unrestricted at the user level — this is a practical governance suggestion, not a documented Microsoft requirement.

How billing shows up

For CSP-purchased licenses, Microsoft’s documentation states that Copilot usage-based billing consumption doesn’t introduce a new billing artifact — it appears within the same unbilled and billed usage reconciliation files that CSP partners already use for Azure consumption, identifiable by Product ID, SKU ID, and Meter ID. Copilot UBB charges are billed separately from, and remain distinguishable from, the Copilot Business seat-based subscription charge on the invoice. The documentation also notes that because adding seats to an existing subscription can trigger tenant-level UBB enablement, consumption charges might appear even when only a subset of seats triggered that purchase event.

What this means for your organization

If you purchase Copilot Business through a CSP partner, it’s worth confirming with that partner whether your tenant already has — or will soon have — a default spending policy in place, and what its tenant and per-user limits are set to. Since the default per-user limit (at least 4,000 credits) and tenant limit (1,200,000 credits) are generous starting points rather than fixed ceilings decided by your organization, reviewing and adjusting them to match your actual usage patterns is a sensible operational step.

Equally, if you manage Copilot licensing partly or fully through the Microsoft 365 admin center rather than solely through a CSP partner, understanding which roles can create versus merely edit spending policies helps you assign the right level of access to the right people, consistent with the principle of using the fewest permissions necessary for a given task.

Conclusion

Microsoft’s supplied Partner Center and Copilot documentation confirms that new Copilot Business CSP licenses include usage-based billing by default, with a default spending policy featuring a tenant limit of 1,200,000 credits and a per-user limit of at least 4,000 credits. Partners configure and adjust the default policy through Partner Center, while more advanced or granular policies — and ongoing tenant-level management — happen through the Microsoft 365 admin center’s Cost Management area.

What the documentation does not confirm is a postponement of this default from November 2 to December 1, 2026; only December 1, 2026 appears in the reviewed source material, referenced through an announcement link. SMB admins and partners who need precise timing confidence should verify the current effective date directly against Microsoft’s official announcement rather than relying on a specific prior date that isn’t present in the documentation reviewed here.

As with any usage-based billing change, this article is a starting point for discussion with your CSP partner or internal IT team — not a substitute for reviewing your own tenant’s actual configuration and reconciliation records. This draft requires human review before publication.