Copilot Agent Billing: Budgets, Caps and Alerts

Per-user licences still cover everyday Copilot chat; agentic work now draws Copilot Credits, so budget it like any other metered cloud service.

What is changing

Microsoft's post on the evolution of the Copilot pricing model splits Copilot into two cost lines. The Copilot user subscription licence, priced per user per month, stays in place for everyday AI work. Advanced workloads move to usage-based billing measured in Copilot Credits. The post names Cowork, Code, Autopilot, new advanced experiences in apps such as SharePoint, and frontier models, and says Copilot Studio agents are coming in October.

Two details make this manageable for a small business:

• Microsoft states that usage-based services stay off until an admin creates a spending policy in the Microsoft 365 admin center, and nothing is billed before that.
• Microsoft Learn, updated on 25 September 2026, currently lists Cowork, apps built with Copilot Cowork and the Work IQ API as the services managed in the new Cost management experience. Copilot Chat pay-as-you-go, SharePoint agents and Copilot Studio still have their own billing pages.

So nothing arrives on your bill by accident today, but the list of covered services will grow. Plan for that now.

Get the roles and billing method right

1. Decide who configures billing. Global administrator and Billing administrator can set billing methods and activate the default policy. AI administrator and License administrator can edit policies, limits and alerts, but cannot create policies.
2. Give finance read-only access. Microsoft supports reader roles such as AI Reader and Global Reader for consumption dashboards without configuration rights.
3. Choose an Azure subscription to bill against. The admin center can use an existing subscription or create one. If you buy through a Cloud Solution Provider, follow Microsoft's partner FAQ, as the subscription must be linked to the partner billing account.
4. Decide on prepaid versus pay-as-you-go. Microsoft applies prepaid capacity packs first, then a Copilot Credit Pre-purchase Plan, then pay-as-you-go.

Create the first spending policy

In the Microsoft 365 admin center go to Copilot, then Cost management, and select Get started. Then:

1. Pick the billing method.
2. Choose Limit monthly spending for the default policy rather than leaving it unlimited.
3. Set a monthly per-user limit. Microsoft describes this as optional, but recommends it to stop one person consuming all available credits.
4. Add alert recipients and a threshold, as a credit amount or a percentage. Alert emails start at the threshold and repeat weekly until the period resets or you change the policy.
5. Turn on user-level notifications so people see they are approaching their cap.
6. Review Auto-apply new services. It is on by default, meaning future supported services and agents join the policy automatically. For an SME, turning it off is the safer choice so each new service is reviewed first.
7. Select Customize setup configuration to scope the default policy to a pilot security group, then Activate.

Note that the default policy sets the tenant limit for all users, and each additional policy has its own independent limit.

Understand what the caps actually do

• When a limited policy runs out, users lose access to covered agents and services until credits reset on the first of the month.
• If a user sits in several policies for the same service, Microsoft picks the one with the highest per-user limit, then the largest overall limit, then the newest. Settings are not combined.
• Moving someone between groups does not reset their consumption for the month.
• Deleting a policy does not reset or reallocate credits; it only removes the limits.

The practical rule: keep policies few and group-based. Two or three is plenty for most SMEs.

Monitor spend weekly

1. Open the Overview tab, which Microsoft says refreshes every four hours, and check total credits, pay-as-you-go spend and anyone near a limit.
2. Use the Consumption tab, which refreshes every two hours, to break usage down by policy, user, group, agent and service.
3. Handle Credit requests promptly. You can route them to your own helpdesk or approval flow with a custom request policy.
4. Ask users to check their own task cost in Cowork with the /cost command before long jobs.
5. Reconcile monthly against the Azure invoice and record any policy changes.

The same discipline applies to other metered AI tools; our note on Claude Code usage credits and budgets uses a similar approach.

A sensible SME starting point

• One pilot policy, one security group, a modest monthly limit and a per-user cap.
• Auto-apply new services turned off.
• Alerts at a threshold that gives you time to act before the cap bites.
• A named person who reviews consumption every week for the first two months.
• A written note of why the pilot exists and what result would justify widening it.

For the governance of apps built with these features, see our note on Copilot Managed Runtime governance.

Source basis

• Microsoft Tech Community: Evolution of the Copilot pricing model
• Microsoft Learn: Usage-based billing and cost management for Copilot Credits
• Microsoft Learn: Managing AI experiences enabled by usage-based billing
• Official Microsoft Blog: Introducing the new Copilot with Home, Code and Autopilot