Your new Copilot licences arrive able to do more work. The meter arrives switched on with them.
Microsoft has moved this date twice. It first told partners November 2, then December 1, 2026, and on November 3 it set a new window: usage-based billing becomes the default for new Microsoft 365 Copilot Business subscriptions bought through a Cloud Solution Provider during Microsoft's fiscal third quarter, January to March 2027. The default spending limit stays at 4,000 Copilot Credits per user per month. For most buyers that removes a setup step worth removing. It also means a metered line now exists on an account that had only a fixed per-seat one, and the controls that bound it sit in a dashboard most people have never had a reason to open. The extra months are time to set those controls on your own terms.
What changes when the Copilot Business default arrives in early 2027?
A default changes. Nothing about the price of a Copilot Business seat changes, and no charge appears on its own. What changes is what happens on a new purchase when nobody makes a decision.
Microsoft's announcement to Cloud Solution Provider partners is short and specific. New Microsoft 365 Copilot Business subscriptions purchased through CSP get usage-based billing by default, pay-as-you-go is the default billing configuration, and Microsoft plans to begin the rollout during its fiscal third quarter, January to March 2027. Microsoft first communicated November 2, 2026, moved the date to December 1, 2026 in October, and moved it again on November 3, saying the change gives partners extra time to prepare. The stated purpose is to let customers reach eligible usage-based experiences with less billing setup.
"Usage-based billing is now enabled by default for new Microsoft 365 Copilot Business subscriptions purchased in Cloud Solution Provider (CSP) during Microsoft's FY27 Q3 (January-March 2027), instead of December 1, 2026, as previously announced."
Microsoft Partner Center announcements, November 2026, update dated November 3, 2026The four details that decide whether this touches you
- A new purchase sets it for the whole tenant. Microsoft states the change applies to new purchases of Microsoft 365 Copilot Business licences in CSP, including standalone offers and bundles, and its November update adds: "New purchases enable usage-based billing by default for existing Microsoft 365 Copilot Business licenses in the tenant." One new order during the rollout can change the configuration for licences bought earlier.
- It is the Copilot Business offers. Microsoft 365 Copilot Business is the partner-led product aimed at smaller organizations. Microsoft's Partner Center documentation scopes the change to the Copilot Business offers in the commercial segment and states that Microsoft 365 Copilot (Enterprise) is out of scope, so an institution licensing the enterprise Copilot add-on can read this page as background.
- An Azure subscription comes with it. Microsoft states that new Copilot Business purchases and any existing Copilot Business licences in the same tenant include the Azure subscription setup needed for usage-based billing. That subscription is a real cloud resource, and it is the thing being billed.
- It now covers every market. Microsoft's November update applies the revised timelines across all markets, including Australia, Belgium, Brazil, France, Germany, India, Italy, Korea, the Netherlands, Poland, and Spain, the eleven markets where it was previously expected to arrive later.
What triggers it, according to Partner Center's documentation
Microsoft's Partner Center documentation for the change describes the feature ahead of release and says details can change before general availability, so read it as the current plan. It lists three purchase events that enable usage-based billing for the tenant: a new subscription to an eligible Copilot Business offer, seats added to an existing Copilot Business subscription through the Partner Center portal, and a Copilot trial that converts to a paid eligible offer. It scopes the change to the Copilot Business offers, including the Business Basic, Business Standard and Business Premium bundles with Copilot, in the commercial segment.
One line in that documentation rewards anyone who prepares early: "Default spending policies are only created if one doesn't already exist." A tenant whose administrators have already set their own spending policy keeps it when the purchase goes through, and the default applies where nobody has set one.
Pay-as-you-go is post-paid against actual consumption, so a tenant where nobody uses the eligible experiences consumes nothing and incurs no consumption charge. The exposure sits in the ceiling on that bill, which the default configuration now sets unless somebody makes and records a decision.
The default limit is published: 4,000 Copilot Credits per user per month
Microsoft's November update states: "The default spending limit is 4,000 Copilot Credits per user per month, which admins can adjust." Microsoft's own example is a customer with 100 Microsoft 365 Copilot Business users, who could consume up to 400,000 Copilot Credits per month under the default limit, with charges based on actual usage.
At the published pay-as-you-go price of $0.01 per Copilot Credit, 4,000 credits is $40 per user per month at the default per-user limit, and the 100-user example works out to $4,000 a month. That is ABT arithmetic on two Microsoft figures, and it is a planning figure: the bill follows actual consumption, administrators can change the limits, any additional spending policy carries its own limit, and Microsoft states its published pricing is subject to change. The limit that governs your account is visible in the Cost management dashboard in the Microsoft 365 admin center, which is the number to work from.
Why is Microsoft switching this on by default?
Because the old sequence had a detour in it. Buy the licence, try to do something useful, discover it needs usage-based billing, go configure an Azure billing arrangement, come back. Microsoft's stated reason for the change is to remove that setup step.
The experiences behind the meter are the ones that do work, and they are where the productivity case for Copilot Business now sits. Microsoft names three as eligible usage-based experiences in the announcement.
What the meter actually pays for
- Copilot Cowork. Microsoft describes it as an agentic system that plans, executes and delivers real work: you describe the outcome and it carries out the steps, building apps, sending email, scheduling meetings, creating documents, posting in Teams and managing files, running multi-step work autonomously.
- Work IQ APIs. The programmatic surface that lets agents and AI solutions reach the understanding Microsoft builds from how your people actually work together.
- GitHub Copilot Harness. One of the three harnesses in Microsoft Copilot Studio, the one Microsoft describes as building agents that automate end-to-end business processes.
Those three are the experiences the announcement names as eligible. The services Microsoft currently lists as managed by usage-based billing inside the Microsoft 365 admin center are a different list: Cowork, advanced work in SharePoint and OneDrive, the Work IQ API, Copilot Managed Runtime, Teams Phone Agent, and Code, which Microsoft links to its Copilot Code (Frontier) documentation. GitHub Copilot Harness is named in the announcement and sits outside that list. Microsoft says it will add more agents and services over time, so treat the two lists as related, and check which one you are reading before drawing a conclusion about what your spending policy governs.
Microsoft's licensing guidance adds that usage-based experiences consume Copilot Credits and require a user subscription licence for access.
Microsoft's case to partners is straightforward: less setup friction, more time spent on adoption with less effort on multistep billing configuration, and a path from early usage into wider consumption. For a lender whose processors currently retype data between three systems, an agent that completes the loop is worth reaching without a billing detour in the middle.
That case is sound. It just has a second half, which is that a spending surface arrives with it, and the institution that reads the defaults before the rollout reaches it gets the productivity without the surprise.
Find out what your tenant is configured to do before the default decides for you.
We read the Cost management configuration on your tenant, tell you what limits exist today, and price the usage-based experiences against what your team would actually use them for. No licence purchase required.
Request a free licensing assessmentWhat is a Copilot Credit, and what does one cost?
One cent. Microsoft publishes the pay-as-you-go price of a Copilot Credit as $0.01, which means every dollar of metered spend is 100 credits.
Copilot Credits are the common currency for usage-based billing across Microsoft's AI services. Microsoft states that credits are pooled at the tenant level, so the total is the sum of what every supported experience consumed, and that the number of credits a single response or action costs depends on the complexity of the task.
What drives the count on a single task
For Copilot Cowork, Microsoft names four cost buckets: the models chosen for the task, the runtime that keeps an agent working across long-running jobs, the context drawn from emails, files, meetings and past interactions, and the tools the system uses to actually send the email or update the document. A one-line question and an overnight reconciliation are not the same unit of work, and they are not priced as though they were.
Microsoft publishes representative consumption figures per task type, and labels them rough planning estimates that vary with workflow and usage pattern. Treat them as a planning input. There is also a Copilot Credit Estimator for modelling Cowork consumption, and inside Cowork a user can type /cost to see the approximate credit cost of the task in front of them.
Prepaid credits, and the order money is spent in
Pay-as-you-go is not the only way to buy credits. The Copilot Credit Pre-Purchase Plan, which Microsoft abbreviates as P3, is a one-year pay-upfront pool with tiered discounts running from 5 percent at 300,000 credits to 20 percent at 300,000,000. Microsoft states that unused credits expire at the end of the annual term, which makes the tier choice a forecasting exercise.
Where both exist, Microsoft states the order plainly: a policy always uses prepaid credits first, whether from capacity packs or a pre-purchase plan, before moving to pay-as-you-go. Microsoft's Credits Guide states that its pay-as-you-go and Pre-Purchase Plan constructs both decrement a Microsoft Azure Consumption Commitment, and Microsoft's Learn guidance adds the condition: the benefit applies only when the selected Azure subscription links to the billing account that includes the commitment. An institution already carrying one has a reason to choose where this spend lands.
Microsoft notes that all of its published pricing is in United States dollars and subject to change, so confirm the current figures against Microsoft before building a budget on them.
| The Copilot Business licence | Usage-based billing in Copilot Credits | |
|---|---|---|
| What it pays for | The assigned Microsoft 365 Copilot Business seat | Eligible usage-based experiences, which the Microsoft announcement names as Copilot Cowork, Work IQ APIs and GitHub Copilot Harness |
| How it is priced | Per user, per month, fixed | Per Copilot Credit consumed, published at $0.01 per credit on the pay-as-you-go meter |
| When you are billed | On the subscription term | In arrears, at the end of the billing month, against actual consumption |
| What caps it | Your seat count | The spending policy limit, and the per-user limit if an administrator sets one |
| Where it is governed | Licence assignment in the Microsoft 365 admin center | Copilot then Cost management in the Microsoft 365 admin center. Microsoft currently lists the services managed there as Cowork, advanced work in SharePoint and OneDrive, the Work IQ API, Copilot Managed Runtime, Teams Phone Agent and Code, which is a different list from the eligible experiences named in the announcement |
| What happens at the ceiling | Unassigned users have no seat | Users lose access to agents and services for the rest of the month, and credits reset on the first |
| Who can change it | License administrator and above | Global or Billing administrator for billing methods; AI or License administrator to edit existing policies, limits and alerts |
Which controls actually cap the spend?
Spending policies. They live under Copilot then Cost management in the Microsoft 365 admin center, and for the services they govern they are where a ceiling is set.
The first policy an administrator creates is the default spending policy, and Microsoft is explicit about its reach: the default setup targets your entire organization and all users. That is a reasonable starting point and a poor finishing point for an institution that wants agent work concentrated in one department first.
The four settings worth reading before anyone uses this
Decide these before anyone uses it
- The monthly policy limit. Microsoft offers a choice between not limiting monthly spending and limiting it. One of those is a budget and the other is not.
- The per-user limit. Optional in the interface. Microsoft advises setting it anyway, in its words to prevent runaway spending of Copilot Credits by one individual user, and its policy guidance says to set at least 2,000 credits per user per month.
- Alert thresholds. Policy-level alerts email named people at a credit amount or a percentage, and continue daily until the monthly usage period resets or the policy is adjusted. User-level notifications only appear as an option once a per-user limit exists.
- Scope. All users is the default. Targeting specific groups requires directory security groups, because Microsoft supports individual users only through group membership.
The behaviours that surprise people
- Auto-apply new services is on by default. Future supported Copilot services and agents join the policy automatically as Microsoft releases them, unless an administrator turns the setting off.
- Prepaid credits are spent first. Microsoft states a policy always uses prepaid credits, from capacity packs or a pre-purchase plan, before it moves to pay-as-you-go.
- Moving someone between groups does not reset their consumption. Credits spent under the previous policy still count against the limit in the new one for that billing period.
- Overlapping policies resolve by the most generous. A user in more than one policy for the same service is assigned the one with the highest per-user limit, then the largest overall limit, then the most recently created.
What happens when a user reaches the limit
Microsoft states it directly: when users hit the limit they lose access to agents and services for the rest of the month, until credits reset on the first of the month. For new work that is a stop, with the one exception Microsoft documents below, which is the right behaviour for a budget and the wrong surprise for a loan processor mid-file. It is also why the alert thresholds matter more than they look, and why the credit request queue exists so a blocked user can ask for more.
There is one piece of grace. Microsoft states that if a running task exceeds the per-user limit it can complete without interruption, and that the excess is not billed, at Microsoft's sole discretion. Read that last clause as written: it is a courtesy, not an entitlement, and no budget should be built on it.
Who is allowed to do what
The roles split along a useful line, and Microsoft's own pages describe it slightly differently, so confirm the detail in your tenant. Global administrator and Billing administrator can add, select and change billing methods, and set billing methods in policies. AI administrator and License administrator can edit spending policies and manage limits and alerts, and Microsoft states they cannot create spending policies. One Microsoft page lists billing methods among what AI and License administrators can edit, and another says a Global or Billing administrator is needed to override or set the billing method, so the practical plan is to treat billing changes as a Global or Billing administrator task until your tenant shows otherwise. Microsoft recommends using the roles with the fewest permissions and limiting Global administrator to emergencies, which is ordinary privileged-access practice.
The part worth carrying into a governance conversation is the reader tier. Microsoft supports reader-based roles that can review consumption dashboards and reports without any ability to change policies, limits or billing. That is how finance, audit and compliance get to see AI spend on their own, and it is a cleaner answer to the question of who monitors this spend than a description of an informal arrangement.
The reporting is close to live. The Overview tab refreshes every four hours and the Consumption tab every two, with consumption broken out by policy, user, group, agent and service, and exports for offline review.
What does this mean on a tenant your provider manages?
One extra requirement, and one thing that can happen without anybody asking for it.
Microsoft publishes separate setup guidance for Cloud Solution Provider and partner-managed customers, and the first step is about the Azure subscription: it must be set up and linked to the partner billing account. If the customer already has an Azure subscription, it needs to be associated with that billing account. If the customer has none, one is created through the Azure portal or Partner Center.
Then the usual configuration follows in the Microsoft 365 admin center: connect the Azure subscription associated with the partner billing account, set who can use the services, set spending limits and alerts, and make sure the discovery setting that lets users find and use the usage-based services is turned on.
Partners will be able to rehearse the setup first. Microsoft moved the Partner Center sandbox date, originally November 2, 2026, and states it will announce a revised date through Partner Center with readiness guidance, with sandbox testing available for at least 30 days before general availability.
The subscription that can appear on its own
This is the sentence worth reading twice. Microsoft states that if you do not have access to any Azure subscriptions, the system automatically creates one for you using the billing account linked in the Microsoft 365 admin center, and that a Global administrator is required to create a subscription that way.
For a credit union, bank or mortgage company, a new Azure subscription is not a billing detail. It is a cloud resource that belongs in the inventory, has an owner and carries a resource group. Pay-as-you-go configuration also lets an Owner or Contributor on the subscription choose the billing region and resource group the billing policy is deployed into, and when the subscription has no resource group, one is created automatically. None of that is alarming. All of it is easier to document on the way in than to reconstruct afterwards.
Where ABT sits in this
Access Business Technologies is a Tier 1 Microsoft Cloud Solution Provider working with credit unions, banks and mortgage companies. We manage Microsoft 365 tenants and we host Azure environments, which means both halves of this change land inside work we already do: the tenant where the spending policy lives, and the Azure subscription the meter bills against.
If ABT is your provider, the Azure subscription linkage is ours to get right. If somebody else is, ask them which billing account the subscription is linked to and get the answer in writing before the rollout reaches your tenant.
What to do before the default arrives in early 2027
Seven steps in a recommended preparation sequence. The first three are reading steps, and they decide what the rest should say.
Decide whether you want the usage-based experiences at all
This is a business question. If there is a real task an agent should own, name it: the reconciliation somebody does by hand every Monday, the file review that takes two hours. If there is not one yet, the honest answer is that the meter should stay at a low ceiling until there is.
Find out who holds the roles
List who currently has Global administrator, Billing administrator, AI administrator and License administrator in your tenant. The first two set how this is billed, and the second two edit the policies, limits and alerts that decide what it is allowed to spend. If that list surprises you, fix the list before you configure anything that depends on it.
Open Cost management and read what is actually there
Go to Copilot then Cost Management in the Microsoft 365 admin center and read the current state: which policies exist, what their limits are, which billing method each uses, and whether a per-user limit is set. That tells you what governs your tenant today. Microsoft's partner announcement publishes the default limit that arrives with a new purchase during the rollout as 4,000 Copilot Credits per user per month, and the same dashboard is where to confirm what your tenant shows once a purchase is made. Treat the dashboard as the source and any article, including this one, as a pointer.
Settle the Azure subscription and the billing method first
Settle this early, because every policy bills against it. Microsoft states you can update the billing method on an existing policy without deleting and recreating it, and a correct choice at the start keeps the first invoice and any Azure Consumption Commitment treatment right from day one. Decide which Azure subscription this bills against, confirm it is linked to the right billing account, and if your institution holds a Microsoft Azure Consumption Commitment, settle here whether this spend should count toward it.
Set the policy limit and the per-user limit yourself
Pick a monthly ceiling you would be comfortable seeing on an invoice, and set the per-user limit even though the interface calls it optional. Microsoft's own guidance is to set it so one person cannot spend the organization's credits, and its policy guidance says to set at least 2,000 credits per user per month, against a default of 4,000. Then set the alert threshold below the ceiling, and name a person who receives the alert, since alert emails continue daily once the threshold is reached. Every one of these settings can be edited later, so start at a ceiling you would defend and adjust once the first month of consumption is visible.
Make the Auto-apply new services call yourself
Leaving it on means services Microsoft has not shipped yet inherit this policy automatically. That is convenient and it is a governance decision. For a regulated institution, ABT's usual recommendation is to turn it off on any policy with a meaningful limit, so a new service or agent is reviewed before it joins the policy, and to record the choice either way.
Name who reads the consumption report every month
Give finance or audit a reader-based role so they can review consumption without the ability to change it, put the review on a monthly cadence, and keep the export. A named owner, a standing review and a saved report are the evidence ABT recommends keeping for AI spend oversight, and they are considerably easier to produce than an administrator pulling a screenshot on request. What any given examination expects is a question for your own compliance function.
A free licensing assessment, sized to the 2027 default
Find out what your tenant is configured to spend, and what the usage-based experiences are worth to your team.
Access Business Technologies is a Tier 1 Microsoft Cloud Solution Provider working with credit unions, banks and mortgage companies. We manage Microsoft 365 tenants and we host Azure environments, so a Copilot estate with a fixed line and a metered line is the kind of thing we untangle regularly.
- A read of your current Cost management configuration, covering the policies that exist, their limits, their billing methods and whether a per-user limit is set, so the default lands on a tenant somebody has already looked at.
- The Azure subscription question answered, naming which subscription the meter would bill against, which billing account it is linked to, and whether it already exists or would be created.
- A role inventory for the four roles that can change what this spends, mapped against who should hold them.
- A usage forecast built from real work, starting from the tasks your team would hand to an agent, so the ceiling you set has a reason behind it.
- A prepaid versus pay-as-you-go comparison at your projected volume, including whether an Azure Consumption Commitment changes the answer, and the monthly review routine that keeps it honest afterwards.
ABT also operates M365 Guardian, its managed security service for credit unions, banks, and mortgage companies.
Where the facts on this page come from
Every date, price, quotation and behaviour described on this page was taken from Microsoft's own pages and re-checked against them on November 8, 2026, when this page was updated for Microsoft's November 3 change to the date.
- Microsoft Partner Center announcements, November 2026, update dated November 3, 2026. The rollout window in Microsoft's FY27 Q3, January to March 2027 (previously communicated as November 2 and then December 1, 2026), the default-on statement, the scope covering new purchases of Microsoft 365 Copilot Business licences in CSP including standalone offers and bundles, the extension of the default to existing Copilot Business licences in the tenant on a new purchase, the three eligible usage-based experiences, the included Azure subscription setup, the default spending limit of 4,000 Copilot Credits per user per month and its 100-user example, the revised timelines applying across all markets, and the revised sandbox timing. Read the Microsoft announcement.
- Microsoft Learn, Usage-based billing for Microsoft 365 Copilot Business in Partner Center. Pre-release documentation, subject to change before general availability: the purchase events that enable usage-based billing, the rule that a default spending policy is created only if one does not already exist, and the scope covering Copilot Business offers and bundles in the commercial segment. Read the Partner Center documentation.
- Microsoft Learn, Usage-Based Billing and Cost Management for Copilot Credits. The services managed by usage-based billing in the Microsoft 365 admin center, the Auto-apply new services default, and the reader-based roles for reviewing consumption. Read the Microsoft overview.
- Microsoft Learn, Set up usage-based billing for Copilot Credits. The role requirements, the daily alert emails, the editable billing method on an existing policy, the Azure subscription settings and the automatic subscription creation. Read the Microsoft setup guide.
- Microsoft Learn, Managing AI experiences enabled by usage-based billing. The default spending policy scope, the monthly and per-user limits and the 2,000-credit guidance, the loss of access at the limit and the reset on the first of the month, the multi-policy resolution order, and group-move behaviour. Read the Microsoft management guide.
- Microsoft Learn, Monitor Copilot Credit spending. The dashboard refresh intervals and the running-task grace. Read the Microsoft monitoring guide.
- Microsoft Learn, Usage-based billing guidance for CSPs, partner-managed customers, and MACC. The CSP and partner-managed setup steps and the Azure Consumption Commitment treatment. Read the Microsoft CSP guidance.
- Microsoft Learn, Understanding the user subscription license and usage-based billing. The requirement that usage-based experiences consume Copilot Credits and need a user subscription licence. Read the Microsoft licensing explainer.
- Microsoft Copilot Credits Guide, November 2026. The $0.01 per Copilot Credit pay-as-you-go price, tenant-level credit pooling, the four Copilot Cowork cost buckets, the Pre-Purchase Plan discount tiers and annual expiry, the Microsoft Azure Consumption Commitment treatment, and the description of GitHub Copilot Harness. Read the Microsoft Copilot Credits Guide.
- Microsoft Learn, Copilot Cowork. Background on what Cowork does and how it is administered. Read the Copilot Cowork documentation.
Microsoft changes product guidance, and states that its published pricing is subject to change. If you are planning around this date, confirm the current wording and figures against the Microsoft sources above before relying on any statement, including the ones on this page.
Related reading
Copilot Credits and Usage-Based Billing: Cost Governance for Financial Institutions
The budgets, hard caps and access controls that make metered AI spend governable. Written before this change, and the reason it matters more now.
Microsoft 365 Copilot Business Pricing for Community Banks, Credit Unions, and Mortgage Lenders
What the per-seat line costs and what it includes, which is the other half of the bill this page describes.
I Gave Copilot ONE Prompt. It Did 6 Hours of Work.
Copilot Cowork running multi-step work end to end. Useful for judging what your own usage forecast should look like.
Three neighbouring decisions: the Copilot free 30-day trial, Microsoft 365 Copilot without a base subscription, and a free Microsoft 365 licensing assessment.
Why a ceiling matters once agents are doing the work
Agents that run on their own are exactly what the meter pays for, and exactly why a limit somebody chose beats a limit nobody looked at. About a minute on how that goes wrong.
Worth separating clearly: a spending policy decides who can use the metered services and caps what they cost. What an agent is permitted to reach, which data it can act on and what it is allowed to do are governed by identity, permissions and data access controls, which are a different set of decisions from the ones on this page.
Custom agents doing more than anyone scoped them to do. A spending policy bounds the cost of that. Bounding the access behind it is separate work.
Copilot Business usage-based billing, answered from Microsoft's documentation
Microsoft's November 3, 2026 update states that usage-based billing is enabled by default for new Microsoft 365 Copilot Business subscriptions purchased through Cloud Solution Provider during Microsoft's FY27 Q3, January to March 2027, instead of December 1, 2026 as previously announced, with pay-as-you-go as the default billing configuration. Microsoft first communicated November 2, 2026, then December 1. Microsoft says the purpose is to help customers access eligible usage-based experiences, including Copilot Cowork, Work IQ APIs, and GitHub Copilot Harness, with less billing setup. Microsoft also states that new Copilot Business purchases include the Azure subscription setup needed for usage-based billing.
It can. Microsoft states the default applies to new purchases of Microsoft 365 Copilot Business licences in CSP, including standalone offers and bundles, and its November 3 update adds that new purchases enable usage-based billing by default for existing Microsoft 365 Copilot Business licences in the tenant. A tenant that already holds Copilot Business licences and buys more during the rollout should expect the default to reach the licences it already has. Microsoft's Partner Center documentation, which describes the feature ahead of release, adds that a default spending policy is created only if one does not already exist. Because the usage-based billing controls apply at tenant level, the practical step is the same either way: read what is configured in Cost management in the Microsoft 365 admin center before the next purchase.
Yes, under Microsoft's November 3, 2026 update. Microsoft states that the updated sandbox and usage-based billing general availability timelines apply across all markets, including Australia, Belgium, Brazil, France, Germany, India, Italy, Korea, the Netherlands, Poland, and Spain, where these capabilities were previously not expected to be available at first.
Microsoft's November partner update states that the default spending limit is 4,000 Copilot Credits per user per month, and that administrators can adjust it. Microsoft's example is a customer with 100 Microsoft 365 Copilot Business users, who could consume up to 400,000 Copilot Credits per month under the default limit, with charges based on actual usage. At the published price of $0.01 per Copilot Credit, that example works out to $4,000 a month at the default per-user limit, which is arithmetic on Microsoft's two figures and a planning figure: the bill follows actual consumption and the limits administrators set. The limit that applies to your own tenant is visible in the Cost management dashboard in the Microsoft 365 admin center.
Microsoft publishes the pay-as-you-go price as $0.01 per Copilot Credit, which means a dollar of metered spend is 100 credits. Credits are pooled at the tenant level, and the number consumed by a given response or action depends on the complexity of the task. Prepaid credits through the Copilot Credit Pre-Purchase Plan carry tiered discounts running from 5 percent at 300,000 credits to 20 percent at 300,000,000 credits, and Microsoft states that unused prepaid credits expire at the end of the annual term. Microsoft notes that its published pricing is in United States dollars and subject to change.
Through spending policies, in the Microsoft 365 admin center under Copilot then Cost Management. A policy carries a monthly spending limit, and Microsoft offers a choice between not limiting monthly spending and limiting it. A per-user limit is also available, and although the interface marks it optional, Microsoft advises setting it to prevent runaway spending of Copilot Credits by one individual user, and its policy guidance says to set at least 2,000 credits per user per month. Policies also carry alert thresholds that email named administrators or stakeholders when usage reaches a set credit amount or percentage, and Microsoft states the alert emails continue daily until the monthly usage period resets or the policy is adjusted.
Microsoft states that when users hit the limit they lose access to agents and services for the rest of the month, until credits reset on the first of the month. Blocked users can submit a credit request for access or a higher limit, which administrators review in the Cost management dashboard. Microsoft also states that a task already running when a per-user limit is exceeded can complete without interruption, and that the excess usage is not billed, at Microsoft's sole discretion. That last clause makes the grace a courtesy, so build the budget without it.
Yes, unless you turn that off. Microsoft states that the Auto-apply new services setting is enabled by default for spending policies, so newly supported Microsoft Copilot services and agents are added to the policy automatically as they become available. Microsoft advises reviewing existing spending policies to determine whether automatic coverage is appropriate, and turning the setting off for any policy where future services and agents should be reviewed first. For a regulated institution, ABT usually recommends turning it off on any policy with a meaningful limit and documenting the decision either way.
Yes. Microsoft states that you can update the billing method for an existing spending policy by opening the policy and updating its billing method, and that doing so does not require deleting and recreating the policy. Existing settings such as scoped users and groups, spending limits, alerts and enabled services are retained. Microsoft also states that a Global administrator or Billing administrator is required to override or set the billing method, so plan for one of those roles to make the change. The choice still deserves care for an institution holding a Microsoft Azure Consumption Commitment, because Microsoft states that eligible Copilot usage applies against a commitment only when the selected subscription links to the billing account that includes it.
Microsoft splits this across two tiers. Global administrator and Billing administrator roles can add, select and change billing methods, and set billing methods in policies. AI administrator and License administrator roles can edit spending policies and manage limits and alerts, and Microsoft states they cannot create spending policies. Microsoft's pages differ on whether AI and License administrators can also change billing methods, so confirm the exact permission in your tenant. Microsoft also supports reader-based roles, including AI Reader and Global Reader, that can review consumption dashboards and reports with no ability to change policies, limits, alerts or billing methods, which is how finance, audit and compliance can monitor AI spend directly. Microsoft recommends using the roles with the fewest permissions and limiting Global administrator to emergency scenarios.
Microsoft first announced Partner Center sandbox environments for November 2, 2026, and moved that date in its November 3 update. Microsoft states it will announce a revised date through Partner Center with readiness guidance, and that sandbox testing is available for at least 30 days before general availability. A partner preparing customers can use that window to rehearse the Azure subscription linkage and the spending policy setup before the default reaches a live tenant.
Set the ceiling yourself
before the default does.
Tell us roughly how many people you have and what you would want an agent to take off their hands. Our engineers will read what your tenant is configured to spend today, name the Azure subscription the meter would bill against, and build a usage forecast from real tasks.

