Picture the January close. The Azure invoice carries a Copilot Credits line, billed pay-as-you-go. The controller asks who approved it. The IT admin says Microsoft turned it on when the reseller added the Copilot Business seats on December 2. The reseller says 4,000 credits per user is Microsoft's default. Nobody chose that number, and nobody in finance has opened the Cost Management page. The Payables Agent's own consumption sits in a different console that nobody has opened either.
The date comes from Microsoft's October 2026 announcement: starting December 1, 2026, usage-based billing is on by default for new Microsoft 365 Copilot Business licenses purchased through a Cloud Solution Provider (CSP), with pay-as-you-go as the default billing configuration (Microsoft Partner Center, October 2026). Business Central agents are not in that announcement. They bill Copilot Credits too, through other consoles, so a Business Central shop that buys Copilot Business seats now runs two meters on one tenant.
Business Central Copilot Credits billing is the metered charge for AI work on a Business Central tenant, counted in Copilot Credits at $0.01 each on pay-as-you-go. Microsoft bills the Payables Agent, Sales Order Agent and Expense Agent (preview) per task, from a prepaid pack or an Azure subscription. Microsoft 365 Copilot Business adds a second meter on December 1: per-user spending policies for features such as Copilot Cowork.
Written from 5+ manufacturing and distribution engagements, 2022-2026, on Business Central. Every setting below was read on Microsoft Learn on October 28, 2026. None was tested in a live tenant for this article, and Microsoft states that its spending-policy requirements may change.
What changes on December 1 in Copilot Credits billing, and what does not
Microsoft's announcement bounds the change four ways. It covers new purchases of Microsoft 365 Copilot Business licenses, standalone offers and bundles included. It turns usage-based billing on for eligible experiences, which Microsoft names as Copilot Cowork, Work IQ APIs and GitHub Copilot Harness. It sets a default spending limit of 4,000 Copilot Credits per user per month, which admins can change. And it reaches supported markets first: the announcement lists Australia, Belgium, Brazil, France, Germany, India, Italy, Korea, the Netherlands, Poland and Spain as not available initially.
Microsoft's own example sizes the exposure. A customer with 100 Copilot Business users "could consume up to 400,000 Copilot Credits per month under the default spending limit." Pay-as-you-go credits list at $0.01 each in the Microsoft Copilot Credits Guide, so that ceiling is $4,000 a month at list, or $40 a seat, and it applies to the eligible services only. Microsoft's admin overview lists the services managed this way today as Cowork, advanced work in SharePoint and OneDrive, the Work IQ API, Copilot Managed Runtime, Teams Phone Agent and Code.
The announcement leaves two questions open. Does adding seats to an existing Copilot Business subscription after December 1 count as a new purchase? Do direct, non-CSP purchases get the same default? The entry is addressed to CSP partners and answers neither. Put both to your reseller in writing, and check Message Center in your own tenant.
A Copilot Credits spending limit is not a budget
A controller reading "default spending limit" will file it as a cap. It limits a seat's usage at a number Microsoft chose.
Microsoft's spending-policy page narrows the claim. Spending policies "are limit-based controls and don't reserve or allocate Copilot Credits to users or groups." The per-user limit has a floor: "Set at least 2,000 credits per user per month," and "your policy must meet the minimum." The same page says its "recommendations and policy requirements may evolve." The lowest ceiling you can put on a seat is 2,000 credits, $20 a month at $0.01, and Microsoft decides where that floor sits.
A budget is an amount a named person approved against a forecast and reviews against actuals. A default limit is a ceiling the vendor picked, with a floor the vendor also picked. Nobody at your company approved either.
One more detail separates the ceiling from the invoice. For users in a group spending policy, "If a running task exceeds the per-user limit, it can complete without interruption." The excess "doesn't count toward the policy limit, isn't billed (at Microsoft's sole discretion), and doesn't appear as consumed credits in the Cost Management dashboards." The dashboard is Microsoft's record of what it counted. The invoice is its record of what it billed. The two can differ, and someone at your company has to be the person who notices.
Four Copilot Credits settings to check before December 1
All four sit in the Microsoft 365 admin center under Copilot > Cost Management > Configuration. Global and Billing administrators set up usage-based billing and the default policy. AI and License administrators can edit policies, limits and alerts, but cannot create policies (Microsoft Learn, setup).
- Spending policy scope and the per-user limit. The default policy covers all users and sets the tenant-level limit. Each additional policy has its own independent limit and inherits nothing from it. The per-user limit is optional, yet Microsoft's setup page says to review and set it "to prevent runaway spending of Copilot Credits by one individual user." Set one limit per seat group and write each number into the budget the controller approved.
- Alert recipients and thresholds. Set the threshold as a credit amount or a percentage. The field pre-populates the email of the admin who is logged in, so add the controller. Alert emails "continue daily until the monthly usage period resets or you adjust the spending policy," which means an ignored alert repeats instead of fading.
- Auto-apply new services. The toggle is on by default. While it is on, newly supported Copilot services and agents join the policy as Microsoft releases them, and Microsoft says it is working to bring more agents and services under this experience. Turn it off on any policy where the controller wants to approve each new spend surface before it draws credits.
- Billing method. Each policy names the Azure subscription that pays, and Global and Billing administrators add, select and change billing methods. Billing runs prepaid Capacity packs first, then a Copilot Credit Pre-purchase plan (P3), then pay-as-you-go. "During initial setup, if the system detects Prepaid Capacity packs, it sets them as the default billing method." If you bought packs for the Payables Agent, read what the default policy points at before December 1.
The fourth check matters because Microsoft says Copilot Credits from prepaid Capacity packs "can be consumed by multiple services managed by both Microsoft 365 admin center and Power Platform admin center." Its Business Central billing page says tenant capacity "is consumed by Business Central environments and other Microsoft services on the tenant." On a tenant that holds packs, a heavy month of invoice processing and a heavy month of Cowork draw on the same balance. On pay-as-you-go, Microsoft describes billing to the Azure subscription you select, so the question becomes which subscription each policy and each Business Central environment points at.
The first three settings govern services Microsoft manages in the Microsoft 365 admin center. Business Central agents are not on that list. Their controls sit elsewhere:
| Control | Microsoft 365 Copilot Business (the December 1 change) | Business Central agents |
|---|---|---|
| Where it is set | Microsoft 365 admin center, Copilot > Cost Management | Power Platform admin center capacity, plus the link between each Business Central environment and a Power Platform environment |
| In the December 1 announcement | Yes: default-on for new CSP licenses | No |
| Cap | Spending policy per user, group or tenant. Default 4,000 credits per user per month. Microsoft's stated floor is 2,000 | Prepaid capacity allocated per environment. On pay-as-you-go, spending limits (budgets) in Cost Management in the Azure portal |
| At the limit | Users "lose access to agents and services for the rest of the month" | When quota is depleted, "the AI capability is unavailable until more capacity is added" |
| Alerts | Email to named recipients at a threshold you set | In-app notifications to users when quota is low or depleted |
| Who sets it up | Global or Billing administrator sets up billing and the default policy. AI and License administrators edit but cannot create policies | Your reseller sets up pay-as-you-go. Your internal admin links the environment |
| Where the usage record sits | Cost Management Overview and Consumption tabs | Power Platform admin center, the Azure portal, and AI consumption trace telemetry in Application Insights |
How to estimate Business Central Copilot Credits spend
Each meter has its own driver. Seats drive one. Invoice and order volume drive the other. Microsoft publishes the rates and worked examples for both, so the estimate takes arithmetic and last month's counts.
| Meter | Formula | Microsoft's example | At $0.01 per credit |
|---|---|---|---|
| Copilot Business, eligible services, default ceiling | Seats x per-user limit | 100 seats x 4,000 = 400,000 credits | $4,000 a month |
| Same seats at Microsoft's floor | Seats x 2,000 | 100 seats x 2,000 = 200,000 credits | $2,000 a month |
| Payables Agent | Invoices x (50 + 5 x lines) | 100 invoices at 3 lines = 6,500 credits | $65 a month |
| Sales Order Agent | Requests x credits per request | 100 requests = 1,650 credits | $16.50 a month |
The seat ceiling moves with headcount. The agent estimate moves with volume. Ten times Microsoft's Payables Agent example, 1,000 invoices a month at three lines each, is 65,000 credits, or $650. Pull last month's invoice and line counts from Business Central and multiply. The Sales Order Agent example assumes half of incoming emails carry a usable attachment, so adjust that input to your own mix.
Capping the two meters carries different risk. A seat that hits its limit loses Cowork until the first of the month. A Business Central environment that depletes its quota loses the agent itself. If the Payables Agent drafts your purchase documents, a cap set too low stops drafting mid-close, and accounts payable feels it before finance does. Set the Business Central cap together with whoever runs AP.
AI Agent Costs: The Real Bill Isn't Tokens, It's Rework argues that rework outruns credits as a cost line. This article prices the credits. Write the AI Pilot Stop Criteria Before the Pilot Starts covers what a stop decision releases once a pilot ends. To net the meter against the saving it buys, run both numbers through the AI ROI calculator.
Who owns the Copilot Credits usage record
Microsoft's setup pages hand the controls to Global, Billing, AI and License administrators. Its Business Central page hands pay-as-you-go setup to your reseller. Finance appears once: reader roles let "finance, operations, licensing, and governance stakeholders" review consumption "with read-only access." That arrangement holds until the person with the settings changes a limit and finance learns of it from the invoice.
The record is also split. A Business Central shop that buys Copilot Business seats reads three consoles to see one month of AI spend: the Microsoft 365 admin center, the Power Platform admin center and the Azure portal. The first two are Microsoft's dashboards. The Cost Management Overview tab refreshes every 4 hours and the Consumption tab every 2 hours, and exports are point-in-time snapshots that can differ from the live dashboard. Business Central also writes an AI consumption trace to the environment's Application Insights resource, which sits in an Azure resource your company configures. It is the one piece of the record you hold.
Four assignments close the gap:
- The controller gets a reader role. AI Reader and Global Reader can view consumption dashboards and reports. Neither can create or change spending policies, limits, alerts, request policies or billing methods. Microsoft recommends roles with the fewest permissions, so skip the Billing administrator seat.
- The IT admin keeps the settings, and the controller signs the changes. A new policy, a raised limit or Auto-apply switched back on is a spending decision. Route it like one.
- Once a month, someone exports the Consumption tab and reconciles it to the Azure invoice. The excess-usage rule above means the dashboard can omit credits the invoice may carry.
- For the first quarter, someone checks weekly. ERP Software Blog, a Dynamics partner commentary site, advised on October 15, 2026: "Make someone responsible for checking it weekly during the first quarter." Put a name on the calendar invite.
The Decision Latency Diagnostic scores the Approve and Audit stages of a decision like this one: who signs a new credit-consuming service on, and where the record of it lives.
Approving spend and keeping its record is a decision with an owner, the ground decision infrastructure covers. OpsGrid, in active beta for Business Central, does not meter or cap Copilot Credits, and none of the four settings above needs it. A reader role, a signed limit change and a named person on a weekly invite do the work. Compare how the five Business Central AI surfaces bill in the Business Central AI agents field guide, and see where Microsoft's own billing terms sit in OpsGrid vs. Dynamics 365 Copilot.
Frequently asked questions
Does the December 1 Copilot Business billing change apply to Business Central agents?
No. Microsoft's October 2026 Partner Center announcement covers new Microsoft 365 Copilot Business licenses purchased through a Cloud Solution Provider, and it names Copilot Cowork, Work IQ APIs and GitHub Copilot Harness as the eligible experiences. Business Central agents such as the Payables Agent bill Copilot Credits under a separate model, set up through the Power Platform admin center and an Azure subscription, and the announcement does not mention them. On a tenant that holds prepaid Capacity packs, Microsoft says services managed in both admin centers can consume the same pack credits, so check which pack or subscription each meter bills.
What is the default Copilot Credits spending limit for Microsoft 365 Copilot Business?
4,000 Copilot Credits per user per month, which admins can change. Microsoft's own example is 100 users consuming up to 400,000 credits a month. At $0.01 per credit on pay-as-you-go, that is $40 per user and $4,000 for 100 users, for eligible usage-based services only. Microsoft's spending-policy page says a per-user limit must be at least 2,000 credits, and that its requirements may evolve.
Who can see Copilot Credits usage without being able to change spending limits?
Microsoft's setup page lists AI Reader, Global Reader and other supported reader-based roles as read-only. They can view consumption dashboards and reports but cannot create or change spending policies, limits, alerts, request policies or billing methods. Microsoft recommends the role with the fewest permissions, so a controller who needs to review spend should get a reader role instead of a Billing administrator seat.
What happens when a Business Central environment runs out of Copilot Credits?
The AI capability stops. Microsoft's Business Central billing page says that when the quota is depleted, the AI capability is unavailable until more capacity is added, and that users receive in-app notifications when the quota is low or depleted. Prepaid capacity is consumed first. On pay-as-you-go, Microsoft points admins to Cost Management in the Azure portal to view detailed usage and adjust spending limits (budgets).