Microsoft now lets you cap Copilot Studio, Cowork, Copilot Managed Runtime and Dynamics 365 agent spending from one screen in the Microsoft 365 admin center. The cap is a hard stop: a user or agent that hits it loses access until the first of the next month. That makes the budget numbers you type in a service-level decision as much as a finance one. Set them per department, route the charges to the right Azure subscription, and do it before usage-based billing becomes the default on more of your Copilot licenses.
Agent 365 Cost Management is the Copilot > Cost Management node of the admin center. In it you write spending policies (rules that say which users, groups, agents or environments may consume Copilot Credits, how many per month, and which bill they land on). At Ignite on November 17, Microsoft's Dynamics 365 announcement described it as "the place to see and control usage-based AI like Cowork, Copilot Studio, Copilot Managed Runtime, and Dynamics 365 agents," with spending policies, limits, alerts and built-in departmental chargeback.
What Microsoft Shipped at Ignite and What Is Still Coming
The controls are in preview today, and the forecasting and cross-vendor pieces arrive over the next six weeks. The Ignite 2026 Book of News lists the services in scope as Copilot Cowork, Copilot Code, GitHub Copilot CLI, Copilot Studio, Copilot Managed Runtime, Autopilot and the Work IQ APIs, and labels the spending policies, limits, alerts and Fabric-based chargeback reporting "In preview."
The timeline, per the same document:
| Capability | Status as of November 17, 2026 |
|---|---|
| Spending policies, limits, alerts, chargeback | Preview |
| Spend forecasting, plain-language questions, optimization recommendations | Frontier program, "this month" |
| Value insights across Microsoft and non-Microsoft agents | December |
| Delegation to business leaders | December |
There is a licensing catch on the analytics side. The Book of News says the new Agent 365 Business Analytics insights for Microsoft services need at least one Microsoft 365 Copilot license in the tenant, while insights for non-Microsoft services need an Agent 365 license. If your plan was to use this as the single pane for Claude, Gemini and OpenAI spend as well, price the Agent 365 seat into that plan.
Microsoft's pitch leans on a cost-overrun statistic. Its Ignite live news page cites a McKinsey study for the claim that AI spending "can nearly quadruple" as organizations go enterprise-wide, "with 93% reporting they've exceeded their AI budgets." Treat that as the vendor's framing for a product it is selling. The useful part for you is the mechanics.
How a Spending Policy Actually Behaves
A spending policy is a limit, and Microsoft's documentation is blunt about what happens at the limit. Per the Microsoft Learn page on managing spending policies (updated November 11), when users hit it "they lose access to agents and services for the rest of the month until credits reset on the first of the month." Users can request more credits, but they do not spill over to another policy.
The details that will catch an admin out:
- There is a floor. The same page requires a per-user budget of at least 2,000 credits per month. You cannot set a per-user allowance of 200 credits to keep a pilot group on a short leash.
- Overlapping policies do not add up. If a user sits in two policies covering the same service, the one with the highest per-user limit wins outright, then the largest overall limit, then the newest. Settings from the losing policy are ignored.
- Moving groups does not reset the meter. Consumption follows the person. A user who burns 500 credits under one policy and moves departments mid-month carries those 500 credits into the new policy's limit.
- New services join automatically. "Auto-apply new services" is on by default, so the next Copilot agent Microsoft adds to usage-based billing starts drawing on your existing policy. The usage-based billing overview, updated on Ignite day, already lists 17 services, including Teams Phone Agent, Clipchamp video creation and Windows 365 for Agents.
- Alerts repeat. The setup guide says alert emails start at your threshold and continue daily until the monthly period resets or you change the policy.
Roles matter too. The setup guide gives policy creation and billing-method choices to Global and Billing administrators. AI administrators and License administrators can edit limits, alerts and billing methods but cannot create a policy. AI Reader and Global Reader get read-only dashboards, which is the role to hand your FinOps analyst.
Why Copilot Studio Is the Part to Plan Carefully
Copilot Studio moves into this console only if you opt in, and opting in for "All environments" switches off your Power Platform controls in one step. Microsoft's guide to managing Copilot Studio costs in the Microsoft 365 admin center explains the mechanism: you create a resource-based policy (scoped to an agent or an environment instead of a person), and for whatever it covers, "Copilot Credit management moves to the Microsoft 365 admin center, replacing their Power Platform admin center capacity allocations and linked billing plans."
The precedence rules decide who pays:
- Microsoft 365 admin center beats Power Platform admin center for any environment or agent a policy covers.
- Resource-based beats identity-based. Microsoft's example: an HR agent with its own policy is billed to that policy regardless of who runs it. If the agent hits its limit, usage does not fall back to the user's policy.
- Per-agent limits exist. Microsoft's sample is a 10,000-credit policy with a 1,000-credit cap per agent.
Two gaps to know before you migrate. Resource-based policies do not cover AI Builder features or the credits they consume, and Microsoft tells you not to move agents, workflows or environments that use AI Builder prompts. A new policy can also take up to 12 minutes to apply after you link an environment. Microsoft's own advice is to start with specific environments, and you should take it.
This matters more after you read what a Copilot Studio conversation can cost. We worked through the meter in Your Copilot Studio Chat Could Cost $7.84 on a Reasoning Model: the capacity pack is still 25,000 credits for $200 a month, and an agent on a reasoning model can eat through a department's allocation fast. A per-agent cap is the control that stops one runaway agent from locking a whole department out of Cowork for three weeks.
How Chargeback Lands on the Azure Bill
Departmental chargeback works by pointing each policy at a different Azure subscription and resource group, so the cost shows up where your cloud FinOps team already looks. An October 30 post on Microsoft's AI FinOps blog explains the setup: when you set a policy's billing method you choose the subscription and resource group that receive the charges, and you can then filter Azure cost analysis by the Copilot Studio meter category, which reflects all Copilot Credits usage. Built-in chargeback works for policies billed through pay-as-you-go and pre-purchase plans.
Billing draws from prepaid money first. The setup guide gives the order as prepaid capacity packs, then the Copilot Credit Pre-Purchase Plan (P3), then pay-as-you-go. Credits you already allocated to environments in the Power Platform admin center reduce what the Microsoft 365 side can see as available, which is one more reason to migrate environments deliberately.
If you already tag cloud AI spend by team, as in Best FinOps Tools for AI Spend, map each spending policy to the same cost center that owns the matching Azure subscription. Otherwise the Copilot line arrives as one lump and finance asks IT to split it by hand.
The Graph API Is Beta and Reports Credits, Not Dollars
Automate policy creation only if you can live with a beta API that has known gaps. Microsoft's Message Center notice MC1521616 put the Copilot cost management APIs on the Graph beta endpoint from mid-October 2026 as a public preview, with no general availability date, and says "detailed consumption reporting is not included in this release." The Microsoft Learn overview adds that the API reports usage in credits and does not include pricing, invoices or currency costs.
Independent testing found rougher edges. Vasil Michev's first look at the API on October 27 reported that policies created through the API "can fail to properly display in the UI," that the API cannot configure billing methods, that a policy's audience cannot be changed after creation, and that per-user balances need one request per user. For now, create policies in the console and use the API to read balances into your reporting.
What the Usage-Based Billing Default Means for Your Renewal
The deadline that should drive this work is the shift to usage-based billing by default, and its date has already moved twice. Topedia reported in September that new Microsoft 365 Copilot Business purchases through CSP partners would come with usage-based billing preconfigured, and an October 3 update to that post moved the date from November 2 to December 1, 2026.
Since then, the timing has slipped again, according to secondary sources. WindowsForum reports that a November 3 update moved the start to Microsoft's FY27 Q3 (January to March 2027), that a new purchase also turns usage billing on for existing Copilot Business licenses in the same tenant, and that the default limit is 4,000 Copilot Credits per user per month. O365HQ cites Microsoft's partner FAQ, updated November 6, for the same 4,000-credit cap, describes it as about $40 per user, and says the default can be switched off by setting the spending limit to zero. That FAQ sits behind Microsoft's partner login, and we could not open it, so treat the date and the cap as unconfirmed until your partner shows you the text.
Do the arithmetic either way. A 4,000-credit default across 1,000 users is a ceiling of 4 million credits a month, or 160 capacity packs at list price. Most users will not get near it. The default policy still sets your maximum exposure, and the AI bundle price increases already in your Microsoft renewal make it harder to absorb a surprise.
The steel-man for leaving the defaults alone is real. Hard caps cut people off mid-task, and a team that loses Cowork on the 20th will call IT. Microsoft gives you two answers to that: user-level threshold notifications that warn people before they hit the cap, and a credit-request flow that admins can route to a budget owner. Use both, and set limits from measured usage.
What to Do Before Usage Billing Becomes the Default
This Week:
- Open Copilot > Cost Management and export the Consumption tab by policy, user and service. Find your top 20 consumers and which services they use.
- Assign AI Reader to your FinOps lead and License administrator only to the people who will edit limits. Keep policy creation with Billing administrators.
- Turn off "Auto-apply new services" on the default policy until someone has reviewed the 17 services already eligible.
This Month:
- Create one identity-based policy per department, each billed to that department's Azure subscription and resource group, with a per-user limit set from last month's real consumption plus headroom above the 2,000-credit floor.
- Pick one Power Platform environment with no AI Builder prompts and move it to a resource-based policy with a per-agent cap. Watch it for a full billing cycle before you touch "All environments."
- Set policy alerts at 50% and 80%, user notifications at 75%, and route credit requests to the department's budget owner.
Before Your Copilot Renewal:
- Ask your CSP or EA account team in writing for the usage-based billing start date for your tenant, the default per-user limit, and whether adding a license switches existing ones over.
- Price a Copilot Credit Pre-Purchase Plan against your forecast once the Frontier forecasting view is in your tenant.
- If you need cross-vendor spend views in December, get the Agent 365 license cost in the same quote.
The Bottom Line
Microsoft has rebuilt the cloud budget playbook for Copilot: a meter, a policy, a subscription to bill, and a hard stop. The parallel is Azure itself a decade ago, when companies that skipped subscription design and tagging spent years untangling one shared bill. The controls here are good enough to use today, with two caveats. Copilot Studio migration replaces Power Platform capacity allocations for every environment a policy covers (removing the environment hands control back), and the API is still beta. Any department without its own policy runs on the tenant default.
Write the department budgets into the console this month, before the usage-billing default reaches your tenant.
Continue Reading
- Your Copilot Studio Chat Could Cost $7.84 on a Reasoning Model
- Microsoft's New Copilot Bills Autopilot Outside the $30 Seat
- Best FinOps Tools for AI Spend: No Dashboard Fixes an Untagged Key
- AI Bundles Push Microsoft, Google and Salesforce to Raise Prices
- Your Unlicensed Copilot Chat Users May Hit Limits Admins Can't See
- Set Privacy Rules Before Enabling Claude Enterprise Smart Reports
- Copilot Studio Agents Keep Shared Memory, No User Opt-Out
