Copilot Studio Pricing in 2026: Costs, Copilot Credits and How to Budget for AI Agents

Copilot Studio has no simple sticker price. If you're asking how much Copilot Studio costs, the real answer is that you pay for what your agents consume, so two teams running the same agent can get very different bills. Copilot Studio pricing starts with one unit, the Copilot Credit, and everything else follows from it.

The short answer: Copilot Studio is billed in Copilot Credits. Pay-as-you-go costs $0.01 per credit, billed monthly through an Azure subscription. A prepaid pack costs $200 a month for 25,000 credits (about $0.008 each). Building agents is free with the maker license. You pay when agents run.

This guide shows what Microsoft Copilot Studio pricing looks like in 2026. It covers what a credit is and what spends it, the ways to pay, which Copilot you actually need, a worked monthly bill with break-even, costs beyond the meter, the mistakes that cause bill shock, and a worksheet you can copy.

That number only makes sense once you know what a credit buys, so start there.

What Copilot Studio Is, and Whether It's Free?

What is Copilot Studio? It is Microsoft's low-code tool for building AI agents that answer questions, take actions and run workflows, grounded in your own data and connected to your systems. If you want the full picture of how Copilot Studio agents are built, the short version is this: you build an agent from topics, knowledge sources and actions, publish it to a channel such as Teams, Microsoft 365 Copilot or a website, and each interaction consumes credits.

So is Copilot Studio free? Building is: as the short answer above notes, the Copilot Studio user license lets staff create and manage agents at no charge. Running agents is not free once they serve users, because that usage is billed in credits. The free trial is covered further down.

Three typical Copilot Studio use cases set up the cost example later in this guide:

• An HR policy agent that answers staff questions about leave and benefits.
• An IT help desk agent that resets passwords or logs tickets.
• A customer FAQ agent on your website.

The customer-facing agent is the one that most often drives volume, and so the bill.

How Copilot Credits Work (and What Spends Them)

A Copilot Credit is the single unit Microsoft uses to meter everything an agent does. How many credits a conversation uses depends on what the agent does in it, not on how long the chat runs.

What a Copilot Credit is?

A Copilot Credit is the common currency for Copilot Studio usage. Each agent event, such as a generative answer, an action or a grounded lookup, consumes a set number of credits. Your organization pays for those credits through pay-as-you-go, prepaid packs, or usage included with Microsoft 365 Copilot licenses.

Microsoft's billing documentation notes that on September 1, 2025, the billing unit changed from "messages" to credits, with no change to the pack quantity or the pay-as-you-go rate. That still surprised people. The price per unit stayed the same, but what the unit counted became more granular, so agents using generative or reasoning features now consume more units per reply than many budgets assumed.

What spends credits, and why the cost per reply varies?

Two terms first. Your tenant is your organization's Microsoft 365 environment. Grounding is the agent looking up your organization's data before it answers.

Rates from Microsoft's Copilot Studio billing rates documentation, checked November 5, 2026.

A scripted answer costs 1 credit. A single reply that grounds on tenant data and calls one action stacks three charges: a generative answer (2) + tenant graph grounding (10) + one action (5) = 17 credits for one reply. That's the same question, answered with 17 times the credits, purely because of how the agent was designed.

One practitioner point that catches teams out: autonomous agents, the ones triggered by events with no human in the chat, consume Copilot Studio credits every time they fire, even when nobody is watching.

Now that you know what spends credits, here's how you can pay for them.

Copilot Studio Pricing Options Compared: Pay-as-You-Go, Prepaid Packs and Included Usage

There are three ways to pay for the same credit. The right one depends on volume and predictability, not on the agent itself.

Prices and terms per Microsoft's Copilot Studio billing documentation and November 2025 Licensing Guide, checked November 5, 2026.

Which license do I need? Makers need the free user license, and usage is covered by one of the routes above. There is no per-user Copilot Studio price for end users; the Copilot Studio licensing cost sits in credits, not seats.

Do I need a Copilot Studio license if I have Microsoft 365 Copilot? For internal agents used by licensed staff inside Microsoft 365 Copilot, Teams or SharePoint, often not, because Microsoft zero-rates core events such as generative answers and tenant graph grounding for those users. For anything external, for unlicensed users, or for autonomous agents, you need credits.

Pooling matters. Capacity is bought at tenant level and allocated to environments in the Power Platform admin center, so one pack can serve several agents. Buy for total tenant usage, not per agent. Microsoft applies the same per-user versus capacity logic across its stack, as our Power BI licensing breakdown shows, so the habit carries over.

Your bill also depends on which Copilot you actually need.

Explore Our Conversational AI Services

Copilot Studio vs Microsoft 365 Copilot vs Built-In Agents: Which Cost Model Applies

Microsoft 365 Copilot is a per-user assistant inside Word, Outlook, Teams and other apps, priced per seat; see what Microsoft 365 Copilot includes for the detail. Copilot Studio builds custom agents priced by consumption. The Copilot Studio vs Copilot 365 choice is rarely either-or: many organizations need both, and the two cost models stack rather than replace each other.

The difference between Copilot and Copilot Studio comes down to these decision criteria:

• Expected monthly volume.
• How predictable usage is.
• Internal versus external audience.
• How many staff already hold Microsoft 365 Copilot licenses.
• Governance needs, including who can publish agents.
• How much budget certainty finance requires.

One edge case worth naming: buying seats only to cover an agent a few people use rarely usually costs more. At Microsoft's listed enterprise price of $30 per user per month, 15 seats cost $450 a month, while those 15 people asking 20 three-reply questions a month at 2 credits each would use 1,800 credits, or $18 on pay-as-you-go (illustrative).

If your agents sit across both models, a short scoping conversation with a team that builds Copilot agents can settle the plan before you commit. 

A Worked Monthly Cost Example, With Break-Even

Here is one agent, priced three ways, using the rates from the table above. The numbers are illustrative, not client data: swap in your own volumes and Microsoft's current rates.

The assumptions

• Agent: a customer FAQ agent on your website, so external use applies and credits are always charged.
• 5,000 conversations a month.
• 3 agent responses per conversation, giving 15,000 responses.
• Each response: one generative answer (2 credits) plus two agent actions, one to look up the customer's record and one to log the interaction (2 × 5 = 10 credits). That's 12 credits per response.

The formula: conversations × responses per conversation × credits per response = monthly credits.

Pay-as-you-go vs prepaid packs for the same month

5,000 × 3 × 12 = 180,000 credits a month.

Decide pack by pack. Each extra pack only pays off if it replaces more than 20,000 credits of pay-as-you-go, which is why topping up the last 5,000 credits on pay-as-you-go (50)beatsaneighthpack(200). Weigh the final figure against the return side of an AI agent, such as the tickets or staff hours it replaces, before deciding the price is high or low.

The break-even point

One $200 pack holds 25,000 credits. The same 200buys20,000creditsonpay-as-you-go(200 ÷ $0.01). So a pack beats pay-as-you-go only when you would use more than 20,000 credits that month.

Below that, you pay for capacity you don't use. At 9,000 credits used, the pack still costs $200, an effective rate of about $0.022 per credit, more than double pay-as-you-go. That's our own arithmetic from Microsoft's prices.

Rule of thumb: run on pay-as-you-go for 2-3 months, measure real consumption, then buy packs for the steady baseline only.

When the same agent costs over ten times more

This is the answer to "why did my bill jump?" Take the same 15,000 responses and change only the design:

• Lean design: generative answers only, 2 credits per response = 30,000 credits = $300 on pay-as-you-go.
• Our example: 12 credits per response = 180,000 credits = $1,800.
• Heavy design: add a premium-model prompt tool to every reply (100 credits per 10 responses, so 10 per response), giving 22 credits per response = 330,000 credits = $3,300.

The heavy version costs 11 times the lean one for the same traffic. Design choices (reasoning models, grounding, actions per turn) move the bill more than conversation volume does.

The credit meter isn't the whole bill.

Costs Beyond the Credit Meter, and How to Test Before You Pay?

Budget for these alongside credits:

• Azure subscription. Pay-as-you-go needs one, linked through a billing policy, and someone must own it.
• Power Platform environment and Dataverse storage. Agents live in environments, and storage beyond your entitlement is billed separately; it helps to understand how Power Platform environments work before you split dev, test and production.
• Microsoft 365 Copilot seats. A separate per-user cost if you choose the included-usage route, at Microsoft's listed $30 per user per month for enterprise plans.
• People. Design, testing, governance and ongoing tuning are usually the largest cost that isn't a license.

On the Copilot Studio free trial: Microsoft offers a free trial that lets makers build and test agents. It's meant for evaluation, not for serving real users at scale.

The cheapest reliable test is a small pay-as-you-go sandbox. Build in a dev environment, set an Azure budget alert at a low threshold such as $50, run 50-100 scripted test conversations, and read the actual credits used per response. That figure replaces the assumption in the worked example.

Cost Controls and the Mistakes That Cause Bill Shock

Most surprise bills come from configuration, not volume. Each mistake below has a one-line fix.

1. A premium or reasoning model switched on for every topic. Fix: enable it only on topics that need multi-step reasoning, and test the credit difference first.
2. Grounding on tenant data for every reply, including simple FAQs. Fix: route high-volume, low-complexity questions to scripted or knowledge-only answers; designing an agent's conversation paths so the cheap path handles routine questions is one of the most effective savings available.
3. Nobody owns the Azure meter. Fix: name one billing owner per billing policy and review usage monthly.
4. Treating Azure budgets as a hard cap. Azure budgets warn you; they don't stop spending. Fix: set alerts at several thresholds (well before, close to and at the budget), and pair them with capacity allocation per environment.
5. Buying packs for peak instead of baseline. Fix: buy packs for your lowest steady month and cover peaks on pay-as-you-go.
6. Autonomous agents firing on every event. Fix: add trigger conditions and filters, and review run counts weekly in the first month.
7. Not monitoring per-agent consumption. Fix: check usage by environment and agent in the Power Platform admin center every month.
8. Not re-checking prices after Microsoft changes billing. Fix: put a quarterly price check in the calendar. The September 2025 switch is the reminder.

Know the costs, control them, then write them down.

A Copilot Studio Budget Worksheet You Can Copy

Fill in one row per agent, total the credits, then apply the break-even rule to choose the plan. The table works as a manual credits calculator; add a row for each new agent as you scale.

In this illustrative row, the expected month costs $1,450, and the buffer caps the budget line at $1,900 (45,000 extra credits at $0.01). The buffer is a planning ceiling, not a reason to buy more packs.

The buffer column is our planning advice, not a Microsoft figure: early agents often run above forecast while topics and prompts are tuned, and a modest buffer covers that without over-buying packs. If you'd rather have this built from your own volumes, that's the core of our Copilot Studio scoping and deployment work. 

Talk to Our Experts Now!

Copilot Studio Pricing FAQs

How much does Copilot Studio cost?

$0.01 per credit on pay-as-you-go, or $200 a month for a 25,000-credit prepaid pack. The monthly bill depends on volume and agent design; the worked example above runs from $300 to $3,300 for the same 15,000 responses.

Is Copilot Studio free?

Building agents is free with the maker license. Running them for users consumes credits, unless the usage is qualifying internal use by Microsoft 365 Copilot-licensed staff.

What is the difference between Copilot and Copilot Studio?

Microsoft 365 Copilot is a per-user assistant inside Microsoft apps, priced per seat. Copilot Studio builds custom agents billed by consumption.

Do I need a Copilot Studio license if I have Microsoft 365 Copilot?

Not for core internal use by licensed staff inside Microsoft 365 Copilot, Teams or SharePoint. External agents, unlicensed users and autonomous agents need credits.

Is pay-as-you-go or a prepaid pack cheaper?

Pay-as-you-go is cheaper below about 20,000 credits a month. Packs are cheaper above that, as long as you actually use the credits.

Is there a free trial?

Yes, Microsoft offers a free trial for building and testing agents. For realistic cost testing, pair it with a small pay-as-you-go sandbox and a low Azure budget alert.

Conclusion

The credit is the unit, and agent design decides how many credits each reply spends. Pay-as-you-go suits pilots and variable volume, while packs pay off only above about 20,000 credits a month, bought pack by pack for your baseline. Copilot Studio pricing stays predictable when every budget has a buffer and a named owner.

Measure real consumption before you commit, and recheck Microsoft's rates every quarter. When you're ready to scope agents and costs together, Centric can help, and our step-by-step Copilot implementation guide covers the rollout itself.