Microsoft 365 Copilot Usage-Based Billing: Nov 2 Checklist

Microsoft 365 Copilot Usage-Based Billing Starts November 2, 2026: Cost Controls for Small Business

From November 2, 2026, any new Microsoft 365 Copilot Business license purchased through a Cloud Solution Provider comes with usage-based billing enabled by default and an Azure subscription attached. The seat price stays fixed, but agent usage and extended features now bill separately through that Azure subscription. Defaults determine who sees those charges and when, so the settings you configure before the first metered session matter.

  • From November 2, 2026, new Microsoft 365 Copilot Business licenses bought through a CSP have usage-based billing on by default.
  • Usage charges land on an attached Azure subscription, not the Microsoft 365 invoice.
  • Standard Copilot Chat in Microsoft 365 apps is covered by the seat; Copilot Studio agents and extended features consume metered credits.
  • Pay-as-you-go Copilot Credits bill at $0.01 each, and reasoning-model responses use far more credits than standard answers.
  • Spending caps, alert recipients, and agent publishing rights should be set before the first metered usage, not after the first invoice.

What changes on November 2, 2026

Microsoft notified CSP partners on September 16, 2026 that the billing model for Copilot Business was changing. Before November 2, usage-based billing was opt-in. After November 2, it is the default state for every new Copilot Business license purchased through a CSP channel. Partners and customers do not have to take any action to activate it; it arrives active.

The change applies to new purchases. Existing licenses are not automatically converted on that date, but any renewal or new seat added after November 2 falls under the new default. If your business works with a CSP for Microsoft integration services, your partner should already be aware of this change and should be reviewing your account configuration ahead of the deadline.

What the Copilot seat covers and what bills as usage

The Copilot Business seat is priced at $21 per user per month on an annual commitment. That seat covers standard Copilot Chat inside Microsoft 365 apps: summarizing emails, drafting documents, searching across Teams conversations, and similar in-app assistance. These interactions do not consume metered credits.

What does consume credits is anything that runs through Copilot Studio agents or uses extended capabilities. Building and deploying an agent, enabling tenant graph grounding, or invoking a reasoning model all trigger metered billing. The seat is the floor; agents and extended features are the variable layer on top. Understanding this boundary is the first step in controlling costs, and it fits naturally into office productivity planning for any team rolling out Copilot.

How Copilot Credits are metered

Copilot Credits are the unit of account for metered usage. Each credit costs $0.01 on a pay-as-you-go basis. Different actions consume different numbers of credits. The table below shows the rates documented by Microsoft.

ActionCredits consumedCost at $0.01 per credit
Generative answer from an agent2 credits$0.02
Tenant graph grounding (added per query)10 credits$0.10
Reasoning-model use (per 1,000 tokens)10 credits$0.10 per 1,000 tokens

A single agent query that uses tenant graph grounding and a reasoning model can therefore consume significantly more than a plain generative answer. A query that triggers all three layers costs at minimum 22 credits, or $0.22, before token volume is factored in. Volume across a team adds up quickly, which is why the metering structure deserves attention before deployment rather than after.

Who owns the Azure subscription when you buy through a CSP

When usage-based billing is enabled by default, an Azure subscription is attached to the Copilot environment. Understanding what a Microsoft CSP is clarifies who holds that subscription. In a CSP arrangement, the partner typically manages the Azure relationship on the customer’s behalf, which means the partner may be the billing owner unless the subscription is explicitly transferred or configured otherwise.

This matters because the entity that owns the Azure subscription receives the usage invoices. If your CSP partner holds the subscription, they see the charges first. If your business holds it directly, the charges appear on your Azure invoice. Confirm with your CSP partner which model applies to your account before November 2. Ambiguity here leads to billing surprises, not because the charges are hidden, but because the wrong person is watching the meter.

Admin settings that control the bill

Three admin settings have the most direct effect on metered spending: who can publish agents, whether usage-based billing is active for a given environment, and who receives credit alerts.

Agent publishing rights are controlled in the Power Platform admin center. By default, any licensed user can create and publish an agent. Restricting publishing rights to a defined group limits the number of agents that can generate metered usage. This is a governance decision, not just a cost decision, and it connects to broader AI policy standards your organization should already have in place.

Environment-level billing settings let admins enable or disable usage-based billing per environment. A development or test environment can be isolated from production billing by configuring it separately. Credit alerts in the Power Platform admin center can be set by credit amount or by percentage of a threshold, and the default recipient is the signed-in admin at the time the alert is configured. Change that recipient to a distribution list or a finance contact so alerts reach someone who can act on them.

How to set spending limits and alerts, step by step

Microsoft surfaces spending controls in two places: the Azure portal for subscription-level budget alerts, and the Power Platform admin center for credit-specific alerts. Use both.

  1. Sign in to the Azure portal and navigate to Cost Management. Set a budget for the subscription attached to your Copilot environment. Configure alert thresholds at 50%, 80%, and 100% of your monthly budget. Add email recipients who have authority to act on the alert.
  2. Sign in to the Power Platform admin center. Navigate to Billing and then Copilot Studio. Select the environment you want to monitor.
  3. Open Credit alerts. Set an alert by credit amount or by percentage of your prepaid capacity. Change the default recipient from the signed-in admin to a shared mailbox or distribution group.
  4. Set a second alert at a lower threshold, such as 75% of your monthly credit budget, to give yourself lead time before the cap is reached.
  5. Document the alert configuration and the recipients in your IT runbook so the settings survive staff changes.

Your vCIO services engagement is the right place to review these settings quarterly, since credit consumption patterns change as teams adopt new agent workflows.

What happens when you hit the cap

Copilot Studio has a defined behavior when consumption exceeds capacity. Agents are disabled when consumption exceeds 125% of prepaid capacity. This applies to capacity pack purchases. On a pay-as-you-go model, there is no automatic shutoff at a fixed percentage; charges continue to accrue until an Azure budget alert fires or an admin intervenes manually.

The 125% threshold means a capacity pack gives a small buffer above the prepaid amount before agents stop responding. Users who hit a disabled agent see an error or no response, depending on how the agent is surfaced. There is no grace period for pay-as-you-go; the meter runs until it is stopped. This distinction is the primary reason to prefer capacity packs if your usage is predictable, and to set Azure budget alerts aggressively if you stay on pay-as-you-go.

Capacity packs vs pay-as-you-go vs pre-purchase

Microsoft offers three ways to pay for Copilot Credits beyond the included seat allowance. Each has a different cost structure and a different risk profile for small business.

OptionPriceCredit volumeOverage behavior
Pay-as-you-go$0.01 per creditUnlimited, meteredCharges continue; no automatic shutoff
Copilot Studio capacity pack$200/month (annual commitment)25,000 credits/monthAgents disabled at 125% of prepaid capacity
Pre-purchase credits[ADD: per-credit rate for pre-purchase credits from Microsoft Learn documentation][ADD: volume and expiry terms from Microsoft Learn documentation][ADD: overage behavior for pre-purchase credits from Microsoft Learn documentation]

For a small business with predictable agent usage, a capacity pack at $200 per month for 25,000 credits provides a known monthly cost and a built-in shutoff. For unpredictable or low-volume usage, pay-as-you-go keeps the baseline cost low but requires tighter alert configuration to avoid unexpected charges.

Your pre-November 2 checklist

Complete these steps before November 2, 2026. Each item includes the admin center and the specific setting name.

  • Confirm Azure subscription ownership — Azure portal, Subscriptions blade: verify whether your CSP partner or your organization is listed as the subscription owner for the Copilot-attached subscription.
  • Set an Azure budget alert — Azure portal, Cost Management > Budgets: create a monthly budget for the attached subscription with alerts at 50%, 80%, and 100%; assign recipients who can act on the alert.
  • Review agent publishing rights — Power Platform admin center, Settings > Governance > Who can create and publish agents: restrict to a named security group rather than all licensed users.
  • Configure credit alerts — Power Platform admin center, Billing > Copilot Studio > Credit alerts: set alerts by amount and percentage; replace the default signed-in admin recipient with a shared mailbox.
  • Choose a billing model — Power Platform admin center, Billing > Copilot Studio: decide between pay-as-you-go and a capacity pack before any agents go live; document the decision.
  • Isolate non-production environments — Power Platform admin center, Environments: confirm that development and test environments have usage-based billing disabled or are on a separate budget.
  • Identify the invoice recipient — Partner Center or Azure portal, Billing account settings: confirm which email address receives the Azure invoice and update it to a finance or operations contact.
  • Document alert recipients and thresholds — Internal IT runbook: record all alert settings, recipients, and billing model choices so the configuration is not lost when admin accounts change.

FAQs

From November 2, 2026, usage-based billing is enabled by default on new Microsoft 365 Copilot Business licenses purchased through the Cloud Solution Provider (CSP) program. Microsoft notified CSP partners of this change on September 16, 2026. The billing requires an attached Azure subscription and applies only to new purchases made on or after that date.

Existing Copilot Business seats retain their current billing terms and are not affected by the November 2, 2026 change. The default usage-based billing applies only to new CSP purchases made from that date forward. If your organization adds new seats after November 2, 2026, those new licenses will be subject to the updated default billing behavior.

On a pay-as-you-go basis, Copilot Credits bill at $0.01 per credit. Alternatively, a Copilot Studio capacity pack provides 25,000 credits for $200 per month on an annual commitment. Credit consumption varies by action: a generative answer costs 2 credits, tenant graph grounding adds 10 credits, and reasoning-model use adds 10 credits per 1,000 tokens. Verify current pricing at Microsoft’s official documentation before purchasing.

Yes, usage-based billing can be disabled, but doing so means metered agent features will stop functioning for your organization. Agents that exceed 125% of prepaid capacity are disabled regardless, so organizations without a capacity pack or pay-as-you-go billing enabled will lose agent functionality when that threshold is reached. Disabling usage-based billing is a deliberate trade-off between cost control and feature availability.

No, standard Copilot Chat prompts used within Microsoft 365 applications by licensed users are not billed as usage-based consumption. Credits apply to agents and extended features such as generative answers, tenant graph grounding, and reasoning-model interactions. Routine prompts in apps like Teams or Word fall within the licensed user entitlement and do not draw from a credit balance.

Before November 2, 2026, review your current Copilot license inventory and identify which seats are under CSP agreements. Confirm who owns the attached Azure subscription, as that account controls billing. Set credit alerts in the Power Platform admin center by amount or percentage—alerts default to the signed-in admin as recipient. Also review which users have permission to publish agents to limit unplanned credit consumption.

IT GOAT Demo

See the power of IT GOAT.
The world’s most advanced cybersecurity platform catered specifically to your business’ needs.

Sign Up

Keep up to date with our digest of trends & articles.

By subscribing, I agree to the use of my personal data in accordance with IT GOAT Privacy Policy. IT GOAT will not sell, trade, lease, or rent your personal data to third parties.

Recent Insights

Table of Contents

Read More

Get a Demo

Mitigate All Types of Cyber Threats 

Experience the full capabilities of our advanced cybersecurity platform through a scheduled demonstration. Discover how it can effectively protect your organization from cyber threats.

IT GOAT

IT GOAT: Threat Intel & Cyber Analysis

We are experts in the field of cybersecurity, specializing in the identification and mitigation of advanced persistent threats, malware, and exploit development across all platforms. 

Threat Detection Experts

Protect Your Business & Operations

Exceptional performance in the latest evaluations, achieving 100% prevention rate and providing comprehensive analytic coverage, unmatched visibility, and near-instant detection of threats.