Copilot Studio Pricing and Copilot Studio Licensing With Copilot Credits per Agent Action

Short answer: Copilot Studio is billed in Copilot Credits, not seats. A prepaid pack costs 200 US dollars a month for 25,000 credits, about 0.8 cents a credit, and pay-as-you-go is billed monthly through Azure. A generative answer costs 2 credits and an agent action 5. Employees licensed for Microsoft 365 Copilot at 30 dollars a month use internal agents at no extra credit charge.

If you are building the Copilot Studio business case this quarter, Microsoft publishes more of the math than most agent vendors. It is split across a pricing page, a Learn article on billing rates and a licensing guide. We checked all three on 8 October 2026 and put the numbers in one place, then added the agent cost that none of them covers.

Copilot Studio pricing at a glance

How much does Copilot Studio cost per month?

As little as nothing and as much as your traffic demands. There is no fee to build an agent. What you pay depends on how many credits your agents burn: one pack of 25,000 credits is 200 dollars, and packs stack and pool across every agent in the tenant. A small internal agent used only by Microsoft 365 Copilot licensed staff may need no pack at all. A public website agent answering a few thousand customers a day will need several.

Microsoft's licensing guide lists the pay-as-you-go meter at 0.01 dollars a credit, which makes the pack about 20 percent cheaper per credit when you use all of it. Pay-as-you-go needs no commitment, is billed in arrears at the end of the month, and is the setting that keeps an agent online when a pack runs out.

Copilot Studio licensing for Microsoft 365 Copilot users

Copilot Studio licensing has one rule that changes the whole budget. When a user licensed for Microsoft 365 Copilot talks to an employee-facing agent, and the agent acts under that user's identity, the classic answers, generative answers, agent actions, tenant graph grounding and AI tools it uses are no charge, within fair-use limits. You pay credits for everyone else: unlicensed employees, customers, partners, and autonomous agents that run on a trigger with no user at all.

Three exceptions catch teams out. Computer-using agents are not included in the Microsoft 365 Copilot use rights. Agent flows are only free when triggered by "When an agent calls the flow"; any other trigger bills at the standard rate. And publishing an agent to an external channel, such as your public website, needs standalone Copilot Studio capacity. If your Copilot Studio agents will also be governed under Agent 365, our Microsoft 365 E7 and Agent 365 licensing breakdown covers the seat side.

Copilot Credits billing rates per feature

Each interaction can use several features at once, and each has its own rate. From Microsoft's billing rates article, updated 1 October 2026:

Reasoning models stack: you pay the feature rate plus the premium tool rate on the tokens the model uses, so a deep-reasoning answer can cost several times a plain generative one. Microsoft's own example is a grounded answer at 12 credits, 10 for grounding and 2 for the answer.

What happens when you run out of Copilot Credits?

Microsoft allows a grace band, then switches agents off. When a tenant on prepaid capacity reaches 125 percent of its credits, custom agents are disabled after the current conversation ends, and users see a message such as "This agent is currently unavailable. It has reached its usage limit." The admin gets an email. Agent flows are stricter: new flow runs are blocked as soon as prepaid capacity is fully used. An environment linked to a pay-as-you-go billing plan is not disabled, because overage simply bills to Azure.

You can also set a monthly consumption limit for each agent in the Power Platform admin center, under Licensing, Copilot Studio, Manage agents. Use it. It is the only native ceiling on what an agent costs you in credits.

A worked Copilot Studio budget for a US support agent

Take Microsoft's own customer support example: a website agent that gives four classic answers and two generative answers per conversation to 900 customers a day. That is 8 credits a conversation and 7,200 credits a day.

The Copilot Studio line is under 2,000 dollars. The refund line, which never appears on a Microsoft invoice, is thirty times larger. If the only job is answering questions from your help content, it is also worth pricing a website AI chatbot trained on your own content against those credits before you commit to packs.

The cost Copilot Credits never meter

An agent action costs 5 credits whether it looks up an order or places a 4,000-dollar purchase order. Credits meter Microsoft's work, not the money your agent moves, and the per-agent consumption limit caps the credit bill, not the payments. Microsoft governs which tools and connectors an agent may call. It does not hold a per-agent dollar budget, a per-purchase ceiling or an approval threshold, which matches what we measured in the Microsoft Agent 365 schema, where 623 agent properties carry no money at all.

That is the gap AgentsPay fills. Your Copilot Studio agent calls AgentsPay through a connector or HTTP action before any payment, and AgentsPay checks the per-agent budget and per-transaction cap, the vendor rules and the approval threshold for that agent. Larger amounts wait for a person in Slack or email, and the agent cannot raise its own limit. The same policy covers agents you run in other platforms, such as IBM watsonx Orchestrate or AWS AgentCore, so finance sees one budget per agent instead of one per vendor.

How to budget Copilot Studio without guessing

1. Split users first. Count Microsoft 365 Copilot licensed employees separately; their internal use is mostly free.
2. Price one conversation. Add the credits per feature for a typical run, using Microsoft's usage estimator, and include reasoning tokens if the agent uses a reasoning model.
3. Buy packs for the baseline and turn on pay-as-you-go for peaks, so agents do not switch off at 125 percent.
4. Set a monthly consumption limit per agent in the admin center.
5. Budget the money the agent moves as its own line, with a hard limit outside the agent.

Is Copilot Studio worth it at these prices?

For a Microsoft 365 shop, usually yes. Internal agents for licensed staff cost almost nothing beyond the seat, and a customer-facing agent at a few cents per conversation is cheaper than a human touch on routine questions. The risk is not the credit bill, which has a ceiling. It is what an agent with a purchasing or refund tool can do inside that bill. Put the dollar limit where the agent cannot reach it, and the rest of the business case is arithmetic.

Frequently asked questions

Is Copilot Studio included in Microsoft 365 Copilot?

Partly. A Microsoft 365 Copilot license at 30 dollars a user a month includes Copilot Studio for building and using employee-facing agents inside Microsoft 365, and those users' interactions consume no credits within fair use. Agents for customers, unlicensed staff or external channels need Copilot Credits.

Do Copilot Credits roll over?

No. A Copilot Credit pack is monthly capacity pooled across the tenant, and Microsoft's enforcement resets when prepaid credits renew each month, so unused credits do not carry into the next month. Size packs to your normal month and let pay-as-you-go absorb peaks.

Can I set a spending limit in Copilot Studio?

For credits, yes. Admins can set a monthly consumption limit per agent in the Power Platform admin center. That caps what the agent costs in Copilot Credits. It does not cap the purchases, refunds or payments the agent triggers through its tools, which need a separate spend control.

Is Copilot Studio pay as you go available?

Yes. You link an Azure subscription billing plan to a Power Platform environment and pay for credits used, billed at the end of each month with no commitment. Environments on pay-as-you-go are not disabled by overage enforcement, because extra usage bills to Azure.