Usage-based billing becomes the default for Copilot Business

In a Partner Center announcement dated 3 November 2026, Microsoft confirmed a significant change to how Microsoft 365 Copilot Business licences are billed. For new Copilot Business purchases made through the CSP (Cloud Solution Provider) channel, usage-based billing will now be switched on by default. Microsoft also pushed back the start date it had previously given as 1 December 2026: the rollout is now planned for the company's FY27 Q3, meaning January to March 2027.

The change does not replace the familiar per-seat subscription, but it adds a second cost layer on top of it. According to the announcement, the default spending limit is set at 4,000 Copilot Credits per user per month, and administrators can adjust that figure. Microsoft's own worked example makes the scale clear: an organisation with 100 Copilot Business users could consume up to 400,000 Copilot Credits per month under the default limit, with charges based on actual usage.

The setting can be turned off, but not without consequence. Microsoft states in the announcement that disabling usage-based billing may limit access to AI experiences. The scope is also wider than it first appears: the rule applies to standalone offers and bundles alike, and the announcement notes that a new purchase within a tenant enables usage-based billing by default for the Copilot Business licences already present in that tenant.

Why this matters

Small and mid-sized companies build their software budgets on predictability: number of seats multiplied by a monthly fee. Usage-based billing changes that equation, turning monthly spend into a variable that depends on how heavily staff use AI features. When a limit is reached, the user loses access to the relevant capabilities until credits reset on the first of the month. Left unmanaged, the arrangement carries two risks at once — an unexpected invoice, and people who cannot work at the end of the month.

Because a large share of Microsoft 365 subscriptions in Turkey is bought through CSP partners, this change lands squarely on local SMEs. November also brought other restrictions across the Copilot family. Under a separate Microsoft announcement dated 4 November 2026, fair-use limits now apply to Copilot Chat for users without a Copilot licence. Those limits took effect on 2 November for organisations with 2,000 seats or fewer and on 9 November for larger ones; Microsoft does not publish the thresholds, and administrators cannot view or adjust them.

What we recommend at Kamer Bilişim

• Set your spending limit before you buy. In the Microsoft 365 admin centre, the Cost Management screen under Copilot lets you define a monthly spending limit per policy and an optional per-user limit. Rather than leaving the default 4,000 credits untouched, run a pilot group for a month, look at real consumption and set your own number from that.
• Configure alert thresholds and decide which subscription pays. The same screen can send an e-mail alert when spend reaches a chosen percentage of the limit, and lets you select the Azure subscription that carries Copilot Credit charges. Making the move without these in place means learning about the overage from the invoice.
• Ask your CSP partner for a quote split into two lines. Licence cost and potential usage-based consumption should be written separately, and the contract should state whether the "auto-apply new services" setting will arrive switched on or off. Annual budgeting needs a known ceiling for that second line.

If you would like to review your current Microsoft 365 setup, your licence allocation and your Copilot rollout plan together, Kamer Bilişim provides on-site and remote support across the Anatolian side of Istanbul. You can reach us through our contact page.

Source: Microsoft Partner Center announcements, 3 and 4 November 2026; Schneider IT Management analysis, 30.09.2026