From 2 November 2026, new purchases of Microsoft 365 Copilot Business through the Cloud Solution Provider, or CSP, programme will include usage-based billing by default. Pay-as-you-go will be the default billing configuration for eligible AI experiences that consume Copilot Credits. The change applies to new standalone and bundled Microsoft 365 Copilot Business purchases through CSP.
For organisations planning to adopt Microsoft 365 Copilot Business, this does not mean that the traditional per-user subscription is being replaced. It means that subscription licensing and consumption-based billing will increasingly operate alongside each other.
The practical question is no longer only, “Which Copilot licence do we need?” Organisations must also consider how they will control access, set budgets, monitor consumption and decide which AI experiences employees should be permitted to use.
What exactly is changing on 2 November 2026?
According to Microsoft’s September 2026 Partner Center announcement, new Microsoft 365 Copilot Business licences purchased through CSP will include the Azure subscription setup needed for usage-based billing. Pay-as-you-go will be the default billing configuration.
Microsoft identifies the initial eligible experiences associated with the announcement as:
- Copilot Cowork
- Work IQ APIs
- GitHub Copilot Harness
Microsoft describes the purpose of the change as reducing the billing setup required before customers can access eligible consumption-based experiences. It also gives customers a way to expand their usage according to business requirements instead of purchasing all capacity through a fixed commitment in advance.
The scope is important. Based on Microsoft’s announcement, the change applies to:
- New purchases from 2 November 2026
- Microsoft 365 Copilot Business
- Standalone licences and bundles
- Licences purchased through CSP
Organisations should not automatically assume that the announcement applies in exactly the same way to existing licences, other Copilot products or purchases made through different commercial channels. Those arrangements should be checked separately against the applicable agreement and Microsoft licensing guidance.
What are Copilot Credits?
Copilot Credits are Microsoft’s common consumption currency for eligible AI services using usage-based billing. Instead of charging only through a fixed per-user subscription, supported services can consume credits based on the work performed.
The number of credits consumed by a task can vary according to factors such as:
- The AI models used
- The amount of context retrieved
- The time required to plan and complete the task
- The tools called during the task
- The complexity of the workflow
This means that consumption is not necessarily a fixed amount for every prompt or request. More complex, multi-stage or agentic tasks may consume more credits than straightforward interactions.
Depending on the service and configuration, organisations may use fixed licensing, prepaid capacity, Copilot Credit pre-purchase plans, pay-as-you-go billing or supported combinations of these purchasing methods. When pay-as-you-go is enabled, eligible consumption can be charged to the Azure subscription connected to the billing method.
Does this mean customers will automatically face unlimited AI charges?
Not necessarily.
Default usage-based billing should not be interpreted as unrestricted or unlimited spending. Microsoft provides administrative controls for governing which users, groups, agents and services can consume Copilot Credits. Administrators can also establish organisation-level and user-level spending limits, configure alerts and select the relevant billing method.
However, organisations should not assume that the default configuration will automatically match their internal budget or governance requirements.
When configuring a spending policy, Microsoft allows administrators to choose between unlimited and limited monthly budgets. Per-user monthly limits are available but optional, and administrators can define alert thresholds to notify relevant stakeholders when consumption approaches configured levels.
Microsoft also specifically advises partners to familiarise themselves with the upcoming change and the preset monthly limit. Because product configurations and commercial arrangements can change, administrators should check the actual default policy and billing configuration presented in their tenant rather than relying on assumptions.
Why AI cost governance now matters
Traditional Microsoft 365 licensing has generally been predictable. An organisation purchases a certain number of user licences and knows the recurring subscription cost.
Usage-based AI introduces another cost dimension. The organisation may still pay a fixed subscription fee for licensed Copilot users, but selected AI experiences can also generate consumption charges based on the Copilot Credits used.
This makes governance a shared responsibility across several teams:
- IT administrators control access and technical configuration.
- Finance teams monitor actual charges and budgets.
- Procurement teams review commercial commitments and purchasing methods.
- Security and compliance teams assess data access and acceptable use.
- Business owners determine which AI scenarios justify additional consumption.
Microsoft’s Cost Management dashboard in the Microsoft 365 admin center is designed to support this governance model. It provides controls for spending policies, service access, limits, alerts, billing methods, credit requests and consumption monitoring.
Pay attention to “Auto-apply new services”
One setting deserves particular attention: Auto-apply new services.
Microsoft states that this option is enabled by default for spending policies. When enabled, future supported Microsoft Copilot services and agents can automatically be added to the policy as they become available. Administrators can turn the option off if they want to review new services individually before including them.
This does not necessarily mean that every new Microsoft AI feature will immediately generate charges. A service must be supported by the relevant usage-based billing framework and covered by the policy.
Nevertheless, organisations with strict budget, regulatory or internal approval requirements should carefully review this setting. A conservative approach may be to disable automatic inclusion for sensitive departments or controlled environments, then assess each new service before allowing it to consume credits.
How spending policies work
Spending policies can be assigned across the organisation or scoped to specific groups. Administrators can use them to control:
- Which users or groups can access eligible services
- Which agents and services can consume credits
- The monthly policy-level spending limit
- Optional monthly per-user limits
- Administrator alert thresholds
- User notification thresholds
- The Azure subscription or supported capacity used for billing
- Whether future services are added automatically
Microsoft notes that the default setup can target the entire organisation and all users. Administrators can customise the scope to specific groups and services before activating it.
Where users belong to more than one spending policy for the same service, Microsoft applies a defined policy-selection order. The policy settings are not combined. This is another reason to design group membership and spending policies carefully rather than creating overlapping policies without a clear structure.
Where administrators can monitor consumption and cost
Organisations should understand the difference between the Microsoft 365 administration view and the Azure billing view.
Microsoft 365 admin center
Under Copilot > Cost Management, administrators can review Copilot Credit consumption by areas such as:
- User
- Group
- Spending policy
- Agent
- Service
- Funding source
This view is intended for operational governance. It helps administrators understand who is consuming credits, which policy applies and whether usage is approaching a configured threshold. Values are displayed in Copilot Credits rather than currency.
Azure Cost Management
Azure Cost Management and Azure invoices provide the billing-oriented view. Administrators can analyse costs by subscription, resource, meter and invoice period. Azure billing information may not provide the same user-level or policy-level detail available in the Microsoft 365 admin center.
Microsoft also notes that Copilot Cowork, Copilot Studio and Work IQ API consumption may appear under the Microsoft Copilot Studio service in Azure Cost Management rather than as separate service entries. This is relevant when finance teams are trying to reconcile an Azure bill with activity visible in Microsoft 365.
For internal reporting, organisations may therefore need both views:
- Microsoft 365 admin center for users, policies and consumption activity.
- Azure Cost Management for accrued charges and invoice reconciliation.
A practical readiness checklist
Before 2 November 2026, organisations planning to purchase Microsoft 365 Copilot Business through CSP should consider the following actions.
1. Identify the billing owner
Determine which team owns the Azure subscription associated with usage-based billing. Confirm who is responsible for reviewing charges, receiving alerts and approving budget changes.
2. Define an initial monthly budget
Set an initial organisation or policy-level limit based on a controlled rollout. Avoid using an unlimited budget unless the business has deliberately approved that approach.
3. Configure per-user limits
A user-level limit can help prevent one person from consuming a disproportionate share of the available budget. Microsoft specifically recommends reviewing this option to reduce the risk of runaway individual consumption.
4. Configure alerts
Establish thresholds that notify IT, finance or procurement before the policy reaches its limit. User notifications can also help employees understand when they are approaching their individual allowance.
5. Review eligible services
Decide whether Copilot Cowork, Work IQ APIs and other supported services should be open to all users or limited to selected groups and approved scenarios.
6. Review Auto-apply new services
Decide whether newly supported services should inherit the policy automatically. Organisations with formal approval processes may prefer to disable this setting and review additions individually.
7. Establish a monitoring schedule
Review consumption regularly during the initial deployment. This can reveal high-usage users, unexpected cost drivers and legitimate scenarios that may justify a higher budget.
8. Document acceptable use
Provide employees with clear guidance on when to use standard licensed Copilot capabilities and when consumption-based or agentic experiences are appropriate.
The wider shift in Microsoft AI licensing
The November 2026 change reflects a broader evolution in how AI services are purchased and managed.
Per-user licensing remains important, but it is becoming only one part of the cost model. As organisations adopt more advanced agents, APIs and multi-step AI workflows, consumption-based billing provides flexibility but also requires more active financial governance.
For Microsoft 365 administrators, procurement teams and business leaders, the priority should not simply be switching off usage-based features. The better approach is to establish controlled access, realistic budgets, monitoring and clear business justification.
Used properly, pay-as-you-go billing can allow an organisation to test and expand AI scenarios without making a large capacity commitment at the beginning. Without appropriate governance, however, teams may struggle to understand which services are being used, who is driving consumption and how the resulting costs should be allocated.
Conclusion
From 2 November 2026, new Microsoft 365 Copilot Business purchases through CSP will include pay-as-you-go usage-based billing by default. This applies to new standalone and bundled purchases and is intended to simplify access to eligible consumption-based AI experiences.
The change should not be presented as automatic unlimited spending. Microsoft provides spending policies, limits, alerts, group-based access controls and consumption reporting. However, customers and their CSP partners must still review and configure those controls according to the organisation’s budget, security requirements and AI adoption strategy.
The most important preparation is therefore not simply licensing. It is putting in place a practical AI cost-governance framework before users begin adopting more consumption-based and agentic AI services.
