aiTudu Book a call

Where you can cap Copilot Studio spend on pay-as-you-go

The first question about Power Platform pay-as-you-go is nearly always "can we set a maximum?" For Copilot Studio the answer is yes, but not where most people look.

Short answer. An Azure budget only sends alerts; billing carries on after you reach it. The hard stops for Copilot Studio are in the Power Platform admin center: the per-environment overage setting, and per-agent monthly limits with Hard stop switched on.

Why Azure can't save you

You can build an emergency brake: a budget alert triggers an action group, which runs a Logic App or runbook that unlinks the environment from its billing plan through the Power Platform API. It works, but it also cuts access for everything relying on pay-as-you-go in that environment, and you should still expect a day of overshoot. Treat it as a last resort, not the plan.

The four places you can set limits

1. Azure, where the money is billed

Each billing plan creates a Power Platform account resource in a subscription. Use one billing plan per cost centre, each in its own tagged resource group, and put a budget on each one, alerting at 50%, 80% and 100% of actual spend plus forecast. Give finance Cost Management Reader, and restrict who can create billing plans.

2. The billing plan, which decides what can be billed

Only the products ticked on a billing plan are billed through pay-as-you-go in its environments. Enable just the meters each environment needs, such as Copilot Studio alone, and link only the environments that need it. Developer and sandbox environments usually shouldn't be linked.

3. The environment's overage setting

In PPAC, Licensing, Copilot Studio, each environment has a capacity overage choice: draw from the tenant's spare capacity (the default), bill to the pay-as-you-go plan, or neither. With neither, the environment uses its allocated Copilot Credits and then stops. Set this on purpose; don't leave the default.

4. Per-agent monthly limits

Under Summary, Manage Agents you can give each agent a monthly credit limit, notify environment and tenant admins, and switch on Hard stop to turn the agent off at the limit. It works for prepaid and pay-as-you-go environments alike. Two caveats:

Everything else on pay-as-you-go has no hard cap

MeterPrice (Oct 2026)Hard cap?How to limit it
Copilot Studio$0.01 per creditYesAllocation, overage setting, per-agent limits, Copilot Author group
Power Apps per app$10 per active user per app per monthNoManaged Environment sharing limits; per-user licences for heavy users
Power Automate (preview)$0.60 per cloud or attended run; $3 per unattended runNoPer-flow licence for high-volume flows; DLP
Dataverse$48/GB database, $2.40/GB file, $12/GB logNoCapacity allocation, audit retention, clean-up jobs
Power Pages (preview)$4 per authenticated user, $0.30 per anonymous userNoPrivate or trial mode for dev and test sites

Reasoning models cost more credits per call and are the usual cause of a sudden Copilot Studio spike. The detailed usage report in the admin center breaks spend down by agent, channel and model, so check it before blaming users.

The setup I recommend

  1. A dedicated, tagged resource group and a budget with alerts for each billing plan.
  2. Only the Copilot Studio meter enabled on those billing plans.
  3. The overage option chosen deliberately in every pay-as-you-go environment.
  4. Monthly limits with Hard stop on every production agent, with a margin.
  5. Agent building restricted to a security group.
  6. A monthly look at the detailed usage report.

Sources

Prices and portal paths change. Check the linked pages before you rely on a number here.

Need this set up?

I'll set your limits and show you who is spending what.