Usage-based billing becomes default on new Copilot Business licenses.

Starting November 2, 2026, Microsoft is changing how new Microsoft 365 Copilot Business licenses are configured. Organizations purchasing a new Copilot Business license through a Cloud Solution Provider (CSP), standalone or as part of a bundle, will have usage-based billing (pay-as-you-go) switched on by default. For IT, finance, and procurement leaders looking to keep control over AI spend, this is a change worth reviewing now, not after the first unexpected invoice.

What exactly is changing?

Microsoft announced the change in its September 2026 Partner Center announcements. In summary:

• Effective date: November 2, 2026.
• Applies to: new purchases of Microsoft 365 Copilot Business (standalone and bundles) through CSP.
• What's on by default: pay-as-you-go for "eligible usage-based experiences" currently Copilot Cowork, the Work IQ APIs, and the GitHub Copilot Harness.
• Existing licenses: the announcement makes no mention of existing licenses being automatically converted. For now, the change applies only to new purchases.

In practice, this means consumption of these features can be billed directly, without an administrator having to opt in. What used to be a deliberate choice an admin made to enable pay-as-you-go is, from November onward, the default starting point.

What does this mean for your organization and your costs?

The core risk isn't the functionality itself, it's the lack of visibility upfront. Usage-based billing is not inherently a problem. It becomes one when no one in the organization knows:

• exactly what usage is being billed,
• what preset limit is configured by default on a new license,
• and who within the organization monitors and adjusts that limit.

Microsoft's announcement references a "preset monthly limit" that ships with new licenses, but does not specify the amount in the source announcement itself. That is exactly where organizations need to take action now: verify what that limit is in your specific situation, with Microsoft or your CSP partner, rather than assuming a default setting will line up with your budget.

Why this is more than a technical change

This change doesn't stand on its own. Copilot Cowork itself already moved to usage-based billing via Copilot Credits in mid-2026, and Microsoft is more broadly shifting toward consumption-based models within CSP. The direction is clear: functionality that used to fall within a fixed license price is, step by step, moving to a model where additional usage is billed separately.

For CSP partners, this is also explicitly a revenue opportunity: Microsoft's own announcement references "upsell conversations" and an Copilot Cowork activation incentive as a benefit to partners from early usage. That's a legitimate partner interest but it isn't automatically the same interest as the organization purchasing the license. Organizations buying through a reseller that also benefits from higher usage would do well to have their own cost governance reviewed independently.

What you can do now

Three concrete steps for organizations that will be purchasing new Copilot Business licenses soon, or that do so structurally via CSP:

1. Explicitly ask for the preset limit from Microsoft or your CSP partner before purchasing new licenses after November 2, 2026. Don't assume.
2. Determine who in your organization is responsible for monitoring Copilot usage and adjusting spending limits, before usage actually starts.
3. Build this change into your broader SAM governance around AI licensing as a standing part of how you manage Copilot consumption, not a one-time check.

Geltec advises organizations across the Benelux independently on Microsoft licensing and Software Asset Management with no stake in higher usage or upsell. Want to know what this change means for your specific licensing situation, or how to stay in control of Copilot costs before the first invoice surprises you? Feel free to get in touch for a no-obligation conversation.