Microsoft moved default usage-based billing for new Microsoft 365 Copilot Business subscriptions bought through the Cloud Solution Provider (CSP) channel from 2 November to 1 December 2026, according to trade coverage of the delay . Reporting attributes the move to partners needing time in sandbox environments that open on 2 November. Those sources date the announcement to the first week of October.

Those extra weeks belong to IT. Copilot now has a metered side, and the people who hold the admin controls decide how that meter runs.

What changed

Futurum’s analysis of 30 September 2026 describes a split pricing model:

  • Everyday AI runs on a per-user licence. It covers tasks such as document summaries and meeting-transcript bullet points, with fair-use limits that Microsoft says “the vast majority” of users never reach.
  • Advanced AI runs on usage-based billing (UBB) in Copilot Credits. It covers long-running agents, unsupervised workflows and frontier models. UBB requires the per-user licence.

Pay-as-you-go credits cost $0.01 each, billed monthly in arrears, per Universal Cloud’s guide to Copilot Business credits . Pre-purchase plans start at 300,000 credits and carry a 5% to 20% discount, with unused credits expiring at year-end.

Reporting on the new CSP defaults adds two details: a default cap of 4,000 credits per user per month and an Azure subscription that Microsoft sets up automatically at purchase. At $0.01 a credit, 4,000 credits works out to $40 per user per month of potential consumption on top of the licence. Treat that arithmetic as a ceiling to compare with your own budget. Trade press describes the rollout as excluding some markets, so confirm with your CSP partner how it applies to your tenant.

Why defaults deserve your attention

Universal Cloud lists the settings that decide your exposure. Each sits in the Microsoft 365 admin center:

  1. Organisation monthly limit. Microsoft presets it and the amount is unpublished. When a policy reaches its limit, users lose access to credit-consuming services until the first of the next month.
  2. Per-user limit. Optional. It stops one heavy user from consuming the whole budget.
  3. Credit consumption scope. The spending policy applies to all users by default. Restrict it to security groups.
  4. Auto-apply new services. On by default. New services and agents that Microsoft adds fall under your policy automatically.
  5. Cowork installation. Available to all users by default, under Copilot > Agents > All agents.
  6. Alerts. Set a threshold in credits or as a percentage so administrators receive an email before the limit arrives.

Futurum adds that, for enterprise customers, UBB services stay off until an admin creates a spending policy. New CSP Copilot Business purchases follow a different default, which makes the policy you write before 1 December the one that governs your spend.

An admin checklist for November

==================================================================
COPILOT FINOPS: BEFORE 1 DECEMBER
==================================================================
1. OWNERSHIP
[ ] Name a budget owner for Copilot credits (IT and finance)
[ ] Give finance the AI Reader or Global Reader role
2. POLICY
[ ] Create a spending policy scoped to named security groups
[ ] Set a per-user limit below the 4,000-credit default
[ ] Review the auto-apply toggle for new services and agents
3. ACCESS
[ ] Decide who may use Cowork and other advanced agents
[ ] Route extra-credit requests to your ITSM portal
4. ALERTS
[ ] Set an alert threshold at 50% and 80% of the monthly limit
5. PARTNER
[ ] Ask your CSP partner for invoice currency, billing date
    and the Azure subscription arrangement in writing
==================================================================

Futurum also notes that Microsoft is adding Graph API management of spending policies and consumption insights. Treat those as your route to scripted reporting as they reach your tenant.

The South African angle

Credits are priced in dollars. A South African organisation therefore carries exchange-rate exposure on every metered credit, in addition to the licence cost. Raise three questions with your CSP partner now: the currency and exchange rate used on invoices, the billing date of the monthly invoice in arrears, and how the automatically created Azure subscription is invoiced. Budget in the currency you pay in, and review the rate assumption each quarter.

Credits measure effort

A credit records the compute a task consumed. It carries no information about the value that task produced. Universal Cloud notes that the /cost command in Copilot Cowork shows estimated credit usage for the current task, which gives users a direct view of effort.

Decide which workflows earn advanced AI by pairing each with an outcome you can measure: hours saved on a monthly report, tickets resolved per analyst, turnaround on a recurring document. Unlock advanced agents for the groups that hold such a workflow, and review the numbers after one billing cycle.

A monthly Copilot FinOps report

Universal Cloud’s guide does not describe a dedicated usage dashboard. Visibility comes from alerts, reader roles and the monthly invoice. A one-page monthly report fills the gap:

LineSourceQuestion it answers
Credits consumed vs. monthly limitAdmin center and invoiceIs the budget on track?
Top 10 users by consumptionAdmin centerWho needs a conversation or a higher cap?
Spend per workflow groupSecurity group scopeWhich teams earn their advanced access?
Extra-credit requestsITSM portalWhere does demand exceed policy?
Invoice amount in randCSP invoiceWhat did exchange rates do?

Share the report with the budget owner, review it in the same meeting as your cloud spend, and adjust caps once a month.

FAQ

When does usage-based billing become the default?

Per the trade coverage cited above, 1 December 2026 for new Microsoft 365 Copilot Business subscriptions bought through CSP. Confirm the date for your tenant with your partner, since market exclusions are reported.

Does the 4,000-credit figure mean a fixed $40 charge?

The figure is a default per-user monthly ceiling, and reporting describes it as adjustable. Customers pay for credits consumed.

Who should own the controls?

IT holds the admin center permissions, so IT proposes the policy. Finance owns the budget and reads the reports through a reader role.

The delay gives you a month. Write the spending policy, name the budget owner and agree the invoice terms with your partner before 1 December.

Sources: MSSP Alert, October 2026 ( https://www.msspalert.com/brief/microsoft-delays-usage-based-billing-for-copilot-business); Futurum, 30 September 2026 ( https://futurumgroup.com/insights/microsoft-splits-the-copilot-pricing-model-into-everyday-and-advanced-ai/); Universal Cloud ( https://universal.cloud/en/blog/article/copilot-credits-copilot-business-november-2026/); TIKR ( https://www.tikr.com/blog/microsoft-caps-copilot-business-at-4000-credits-per-user-by-default) . Facts as reported in trade and partner coverage; no primary Microsoft document was reviewed.