To set up pay-as-you-go billing for Copilot agents safely, create an Azure subscription, add a monthly Azure budget with alerts, then create a billing plan in the Power Platform admin center and link your environment to it. Set a monthly limit per agent, and only then give staff the builder role.
The order is the point. Pay-as-you-go has no ceiling of its own: usage is billed to your Azure subscription at the end of each month, with no up-front commitment. A budget does not stop spending either. So you need two layers, an Azure budget that warns you and an agent limit that stops the agent, both in place before the first employee clicks "create agent".
What you are switching on, in plain terms
Copilot Studio measures an agent's work in Copilot Credits. Azure's published retail price for the Copilot Studio pay-as-you-go meter is $0.01 per Copilot Credit, and the bill arrives at the end of the month for what was used. The alternative is a prepaid pack of 25,000 credits at $200 a month, which works out at $0.008 a credit but only helps if you use most of the pack: Microsoft's licensing guide says packs are billed annually and unused credits do not roll over to the next month. Pay-as-you-go suits a firm that does not yet know its volume, which is most small firms starting out.
What costs how many credits is set by Microsoft's billing rates page, last updated on 3 November 2026: a classic (scripted) answer is 1 credit, a generative answer 2, an agent action 5, and tenant graph grounding 10. Staff using an agent while signed in with a Microsoft 365 Copilot licence are not charged for that employee-facing use, within fair-use limits. Anyone without that licence, and every public-facing chat, consumes credits.
The tutorial on whether Copilot agents cost money covers the meter itself. Read that first if credits are new to you; the steps below assume you already want agents and need them fenced in before anyone builds one.
The Complete Excel Course with AI Integration
From formulas and pivot tables to Power Query, DAX, VBA and AI with Copilot, ChatGPT and Claude — hands-on from the first lesson.
By Sagnik Bhattacharya and Virginia Thorn, Primetime Emmy Award winner
Buy nowStep 1: get an Azure subscription you control
Pay-as-you-go needs an active Azure subscription in your tenant. If you do not have one, Microsoft's setup page says to follow your usual process or create one through its Azure account page, and you need permission to create resources and register resource providers on it. The page says most owners and contributors of a subscription have that. Microsoft's Copilot Studio pricing page adds that a free Azure account includes a $200 credit for building agents or other Azure services, which is useful for a trial but not a reason to skip the budget.
Two choices here matter for a small firm:
- Use a dedicated subscription, or at least a dedicated resource group, for Copilot. When you create a billing plan, Microsoft creates a hidden Power Platform account resource in the resource group you choose, and all Copilot charges land there. A separate resource group means a budget scoped to it measures Copilot and nothing else.
- Decide who owns the subscription. It should be an owner, not the person who will build agents. The builder should not be able to raise their own budget.
A new subscription may take up to 48 hours before Cost Management features are usable, according to Microsoft's budget page. Create the subscription a couple of days before you plan to roll out, not on the morning.
Step 2: create the Azure budget before anything is billed
In the Azure portal, open the subscription (or the resource group you will use), choose Budgets in the menu and select Add. Microsoft's budget tutorial describes the form: check the scope, name the budget, pick a reset period of monthly, set an expiry date, and enter the amount.
Alerts are the part owners skip. A budget needs at least one threshold and one email address, and allows up to five of each. Each threshold can be on actual cost or forecast cost. Forecast alerts warn you that you are heading over the budget, while actual alerts say you are already there.
A filled-in alert set for a small firm
Illustration: an electrical contractor with a monthly Copilot budget of $150.
| Alert | Type | Threshold | Sent to |
|---|---|---|---|
| Early heads-up | Forecast | 100% of budget ($150) | Owner and office manager |
| Half spent | Actual | 50% ($75) | Owner |
| Nearly there | Actual | 80% ($120) | Owner and office manager |
| Over budget | Actual | 100% ($150) | Owner, office manager and IT provider |
| Wake-up call | Actual | 120% ($180) | Everyone above |
That uses all five thresholds. Add Microsoft's note to your own runbook: cost and usage data typically arrives 8 to 24 hours late, budgets are evaluated every 24 hours, and notification emails usually go out within an hour of the evaluation. So an alert can trail the real spend by a day or two. That lag is why the 50 per cent alert exists, and why the agent limit in step 4 matters more than the budget.
Also add azure-noreply@microsoft.com to the approved senders, because Microsoft says the alert emails otherwise may land in junk. If you want a text or app notification, a budget can call an action group, which works for subscription and resource-group scopes.
Step 3: create the billing plan and link one environment
Now connect Copilot Studio to that subscription. In the Power Platform admin center:
- Choose Licensing in the navigation pane, then Pay-as-you-go plans, which opens the Billing plans page.
- Select New billing plan and choose Azure subscription.
- Name the plan, for example "Copilot agents - office".
- Pick the Azure subscription and a resource group. If the subscription has no resource group, create one in the Azure portal first.
- Under Power Platform products, choose the product the meters apply to, then Next.
- Choose a region, select the one environment you want to link, and Save.
Who can do this? Microsoft's page lists environment admins, Power Platform admins, global admins and Dynamics 365 admins. Environment admins are limited to billing policies and environments of their own. Pay-as-you-go works for production and sandbox environments.
Link one environment only, to begin with. An environment can sit in only one billing plan at a time, and linking only the environment where agents are meant to live keeps experiments elsewhere from billing you. You can unlink later; usage already incurred is still billed, but further usage is not.
Where the charges appear
The hidden resource is the thing to find. In the Azure portal, open the resource group, select View hidden types above the resource list, and look for the Power Platform account resource named after your billing plan. You can tag it, which helps if you later split costs between departments. Billing plans can also be created per team, which is how larger firms bill sub-teams separately.
A separate plan for staff using Copilot Chat agents
Microsoft also describes a different route for people without a paid Copilot licence who want to use agents in Microsoft 365 Copilot Chat. In the same menu you choose Microsoft 365 Copilot Chat instead of Azure subscription, add a name, subscription and resource group, and save. Microsoft then creates an environment called Microsoft 365 Copilot Chat that you cannot delete, though you can unlink it. Treat that as a separate decision with its own budget line: it covers staff use, not the agents you build for customers.
Step 4: set a monthly limit on each agent
This is the layer that stops spending. Microsoft's capacity page says admins can set monthly consumption limits for each agent, whether the environment uses prepaid capacity or pay-as-you-go. In the admin center go to Licensing, then Copilot Studio under Products, and on the Summary tab select Manage Agents. There you can search agents, see month-to-date billed credits and each agent's status (within limit, nearing limit or over limit), turn an agent off, and set a limit.
Two guardrails exist: notifications to admins as an agent nears its limit, and a hard stop that turns the agent off once it hits the limit. Microsoft warns that limits are not applied instantly, so an agent may keep answering for a while after it hits one. Leave margin: if the budget is $150, an agent limit equal to $120 of credits (12,000 credits at $0.01) leaves room.
One more catch from Microsoft's pages: an agent's limit does not stop the agent flows it calls, because flows are billed and checked separately. If an agent triggers automations, watch the agent flow actions line as well.
Main worked example: a customer FAQ agent for an accountancy practice
Illustration: a six-person accountancy practice wants a website agent that answers questions about opening hours, document lists and fees, using classic answers for its fixed replies and generative answers for the rest.
- Average conversation: four classic answers (4 credits) and two generative answers (4 credits), so 8 credits, which is $0.08.
- Expected traffic: 40 conversations a day over 30 days, which is 1,200 conversations.
- Credits: 1,200 × 8 = 9,600, which is $96 a month.
- Budget: $150 a month, giving about 56 per cent headroom for a busy deadline month.
- Agent limit: 12,000 credits, which is $120.
Microsoft's own customer-support example uses the same shape: four classic and two generative answers per run, at 900 customers a day for 7,200 credits a day. The point of copying the pattern is that you can scale it down to your traffic and check the answer. If traffic doubles in tax season, 19,200 credits would be $192 and the agent limit would switch it off partway through the month, which is the behaviour you want while you decide whether to raise it.
A fuller walkthrough of that cost, with cheaper alternatives, is in what a customer FAQ agent costs.
Step 5: decide who can build, then tell them the rules
Only now should staff touch the tool. Microsoft's capacity page says that in the Power Platform admin center you go to Settings and update the Copilot Author setting, then assign a security group, and only members of that group get access to Copilot Studio. Create a group with two or three named people, for instance the owner and the person who keeps the website. Everyone else can still use the finished agents.
Write a half-page builder rule and send it with the invitation. A usable template:
Copilot agent builder rules (draft for [business name])
1. Build only in the "Office agents" environment. Never in the default one.
2. Every new agent gets a monthly credit limit before it is published.
3. Use classic answers for fixed facts (hours, fees, forms). Use generative answers
only where the wording must change.
4. Do not turn on tenant graph grounding (10 credits a message) without asking [owner].
5. Do not choose a reasoning model without asking [owner].
6. Check the agent's Monitor page on Friday, and tell [owner] if credits for the week
exceed [number].Rules 4 and 5 come from the rate table. Tenant graph grounding costs 10 credits a message, five times a generative answer. Reasoning models are metered by the token as well: Microsoft's own example of one customer follow-up with a reasoning model comes to 141 credits for the model charge, plus the normal rates, on top. At $0.01 that single message is over $1.40, against about eight cents for the FAQ conversation above. That is the kind of surprise a builder rule prevents.
A trial that cannot overspend, and when to use it
If you only want to look first, Microsoft's licensing page says a Copilot Studio trial lets you create agents and test them in the test chat, but not publish them. A trial agent keeps working for up to 90 days after the trial ends, per the same page. Use this before step 3 while staff experiment, since nothing is published and no customer traffic is billed.
When the 50 per cent alert lands mid-month
A realistic week. On a Monday the owner gets the 50 per cent alert on the 14th of the month, which is a day or two late because of data lag. Spend is $75 in 14 days, so the forecast says $160. The owner opens the Power Platform admin center, goes to Summary and downloads the environment report, then the agent report. The report shows one agent consumed most credits, with the Product or AI feature column naming tenant graph grounding. A builder had switched it on during testing. The owner turns it off, lowers the agent's limit, and mentions the rule in the next staff meeting. Microsoft's capacity page notes that these reports show consumption by environment, agent and user, but not by single conversation or token counts, so the fix is by agent and feature, not by message.
Reading the first month's report
The first report is where the abstract rates turn into your own numbers. Microsoft's capacity page says the detailed environment report has columns for agent name, Product or AI feature, channel, LLM model, knowledge source or tool used, and billed against non-billed credits. Here is an illustrative extract for the accountancy practice's first month, after a test week.
| Agent | Feature | Channel | Billed credits | Cost at $0.01 |
|---|---|---|---|---|
| Website FAQ | Classic answer | Website | 4,800 | $48 |
| Website FAQ | Generative answer | Website | 4,800 | $48 |
| Staff handbook helper | Generative answer | Teams | 0 (licensed users) | $0 |
| Test agent | Tenant graph grounding | Test chat | 2,000 | $20 |
Three things to read from it. First, the FAQ agent landed on $96, exactly where the sum predicted, which means the sum is a usable forecast. Second, the handbook helper cost nothing because every user was signed in with a Copilot licence, which matches Microsoft's rate table, though the footnote says that use is subject to fair-use limits. Third, the test agent consumed $20 of grounding in a week while nobody was watching. Nothing was wrong, but without a limit that agent could have run on for the month. Check the Azure bill the same week, because Microsoft says Azure Cost Management is where you see the amounts billed to the subscription.
Three situations and what to do
An agent starts answering far more than expected
Say the website agent is linked from a newsletter on the first of the month and conversations jump from 40 to 400 a day. At 8 credits a conversation that is 3,200 credits, or $32, a day. Spend passes the $75 half-way mark during day three and the agent's 12,000-credit ($120) limit during day four. The budget email may arrive a day after the line is crossed, because of the data lag, and the agent may keep answering for a few hours past its limit, so the forecast alert is the one that gives you warning. Decide then: raise the limit knowingly, or leave it off until the campaign ends. The point is that a person made the call.
A builder leaves the firm
Remove them from the Copilot Author security group the same day. Check Manage Agents for anything they owned that is still consuming credits, and reassign or switch it off. Agents you do not recognise are the first thing to question in a monthly check.
You want to stop completely
Microsoft's setup page says you can turn pay-as-you-go off at any time by removing the environment from the billing policy or deleting the policy. Usage already incurred is still billed, and deleting the policy does not delete the hidden Azure resource, so remove that in the Azure portal if you want it gone.
A message to staff, ready to adapt
People follow a rule better when they know the reason. This note works for a small firm and can be pasted into an email.
Subject: Copilot agents: who can build them, and why
Hi all,
We are starting to use Copilot agents for [customer questions / internal requests].
Agents cost us a few cents each time they answer, billed to a monthly budget of
$[amount], so we are keeping building to [two names] for now.
If you have an idea, send it to [name] with: who it helps, what questions it would
answer, and roughly how many times a week. We will test it in the office
environment first and set a monthly limit before it goes live.
Using an agent that has already been published is free of charge to you. Thanks,
[your name]The message does not promise that the agent is free to the firm, which it is not, and it asks for the one number, weekly volume, that makes the forecast possible.
A short checklist to run once a month
- Open the Azure budget and check actual against forecast.
- Open Manage Agents: any agent nearing or over its limit?
- Download the agent report and sort by billed credits.
- Check the Copilot Author security group for leavers and new joiners.
- Read the billing rates page once a quarter in case the rates changed.
If you want a second pair of eyes on the numbers, that is the sort of thing my AI implementation consultation covers. For the next decision, whether Copilot Studio is the right tool at all, see what Copilot Studio is and whether a small business needs it and Power Automate versus Copilot Studio for approvals.
Pay-as-you-go setup questions owners ask
Does an Azure budget stop Copilot spending at the limit?
No. Microsoft's budget documentation says notifications are triggered when thresholds are exceeded, but resources are not affected and consumption is not stopped. To actually stop an agent, use the monthly agent limit with the hard-stop option in the Power Platform admin center, and keep the Azure budget as the early-warning layer.
Who can create a billing plan?
Environment admins, Power Platform admins, global admins and Dynamics 365 admins can create a billing policy, with environment admins limited to their own environments. You also need permission on the Azure subscription, usually as owner or contributor, to create resources and register providers there.
How much does a Copilot Credit cost on pay-as-you-go?
Azure's published retail price for the Copilot Studio pay-as-you-go Copilot Credit meter is $0.01 a credit, billed through your Azure subscription. A classic answer uses 1 credit and a generative answer 2, so a generative answer costs about two cents. Check Microsoft's current rate table before you forecast.
Can staff build agents before I have set a limit?
They can if you have not restricted the Copilot Author setting, which is why this order matters. Create the budget and limits first, then assign a security group to Copilot Author so only named people can build. Environments that are not linked to a billing plan are not billed to your Azure subscription.
Further reads
- Microsoft 365 Copilot Readiness Checklist for Small Businesses — Wider readiness steps before any Copilot rollout.
- Is Microsoft 365 Copilot Worth It for a Small Business? — Decide whether the paid licence is worth it first.
- Microsoft AI Chatbot for Business: Copilot Chat vs Microsoft 365 Copilot — Copilot Chat against Microsoft 365 Copilot in plain terms.
- AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.
Sources: Microsoft Learn pages on pay-as-you-go setup and overview, Copilot Studio billing rates, Copilot Studio licensing and trial, Copilot Credit capacity management and Azure Cost Management budgets; Microsoft Copilot Studio pricing page; Azure retail prices list for the Copilot Studio pay-as-you-go meter.