From 2 November 2026, every new Microsoft 365 Copilot Business licence purchased through Cloud Solution Provider (CSP)—whether standalone or as part of a bundle—will include usage-based billing by default.

This change removes a familiar barrier from the adoption journey. New licences will include the Azure subscription setup required for pay-as-you-go billing, giving customers a simpler route to eligible usage-based experiences such as Copilot Cowork, Work IQ APIs, and GitHub Copilot Harness.

How the included Azure subscription works

Microsoft plans to simplify the technical onboarding by including the Azure subscription setup required for usage-based billing with each new eligible Copilot Business purchase. In practical terms, the customer will not need to begin with a separate, multistep Azure billing configuration before eligible experiences can consume Copilot Credits. The Azure subscription acts as the billing vehicle for pay-as-you-go consumption, while the Microsoft 365 admin centre becomes the main operational workspace for controlling access and monitoring how Copilot Credits are used.

This does not mean that all advanced AI usage becomes part of the fixed per-user licence fee. The user subscription licence continues to cover the applicable everyday Copilot capabilities, while eligible advanced experiences consume Copilot Credits according to the work performed. The number of credits can vary based on factors such as the model used, the amount of business context retrieved, the processing time, and the tools called by the experience. Those metered charges flow to the connected Azure subscription and appear on the customer’s Azure bill.

Partners should help customers understand the two management views. The Microsoft 365 admin centre provides detailed operational insight by spending policy, group, user, agent, service, and funding source. Azure Cost Management provides the financial view by subscription, resource, meter, and invoice period. Azure billing data is updated daily, although usage may take up to 24 hours to appear, so neither view should be treated as an instant stop switch.

Why this matters for partners

·        Less setup friction: Customers can begin exploring eligible experiences without a separate, multistep billing configuration.

·        More time for adoption: Partner teams can focus on use cases, activation, governance, and measurable business outcomes.

·        A clearer growth path: Early consumption can open natural conversations about expansion, optimisation, and the Copilot Cowork activation incentive.

Managing spend: policies, limits, and alerts

Usage-based billing should be positioned as controlled flexibility, not uncontrolled spend. Before users access an eligible service, the customer should assign the right administrators and agree who owns the budget. Global administrators and Billing administrators can add or change billing methods and create spending policies. AI administrators and Licence administrators can manage policy settings, limits, and alerts, but cannot create the policies themselves.

·        Create spending policies: Use Copilot > Cost management in the Microsoft 365 admin centre to define which supported agents and services may consume credits and which users or groups may access them.

·        Set organisational and user limits: Start with a conservative monthly ceiling aligned to the customer’s approved budget and pilot scope. Use tighter user-level limits for early adopters or high-cost scenarios, then adjust them using actual consumption data.

·        Configure threshold notifications: Set alerts for administrators and users before a limit is reached. A practical approach is to notify at early-warning, review, and critical thresholds—for example, 50%, 75%, and 90%—so the customer has time to investigate or approve additional capacity.

·        Review automatic coverage: Spending policies are configured to auto-apply to newly supported Copilot services by default. Partners should confirm whether the customer wants future services covered automatically or reviewed before activation.

·        Choose the right funding model: Depending on the service, customers may use pay-as-you-go, capacity packs, a Copilot Credit Pre-purchase Plan, or a supported combination. The right choice should reflect expected consumption and the customer’s preference for flexibility or predictability.

Monitor and optimise: Review consumption regularly during the first month, then establish a monthly FinOps rhythm. Compare spend with the business outcome being delivered, identify the users and experiences driving cost, and decide whether to maintain, restrict, redesign, or expand the scenario. Partners can turn this into a valuable managed service covering policy design, consumption reporting, optimisation, and quarterly value reviews.

What partners should do now

1.       Prepare your teams: Brief sales, technical, licensing, finance, and customer-success teams on the default configuration, the preset monthly limit, and the difference between fixed licence entitlements and metered experiences.

2.       Confirm ownership: Identify the customer’s billing owner, technical administrator, and business sponsor. Agree who may approve limit changes or additional credit requests.

3.       Establish guardrails before activation: Create spending policies, select the relevant services and user groups, configure limits and alerts, and document the review process.

4.       Start with a focused use case: Include Copilot Cowork, Work IQ APIs, or GitHub Copilot Harness only where the scenario supports a clear business need and measurable outcome.

5.       Track value alongside consumption: Report on credits used, cost drivers, adoption, time saved, throughput, or another agreed measure. Use evidence—not activity alone—to guide expansion.

6.       Keep customers informed: Explain that usage data and Azure charges may not appear immediately, and schedule proactive reviews rather than waiting for an invoice or alert.

The opportunity: Turn a billing change into an adoption conversation. Start preparing customer-facing teams now so that, from 2 November, they can confidently explain the model, identify relevant scenarios, and help customers move from licence purchase to measurable value faster. Reach out to our team at channel@4sight.cloud for any assistance required.