Copilot Studio vs Power Automate Pricing: Which License to Buy for Which Work

The short answer: Power Automate is licensed, Copilot Studio is metered. Power Automate Premium is $15 per user per month paid yearly, Power Automate Process is $150 per bot per month, and Hosted Process is $215 per bot per month. Copilot Studio is $200 per month for 25,000 Copilot Credits pooled across the whole tenant, which works out to $0.008 per credit. Buy Power Automate when the steps are known in advance and you want them run the same way every time. Buy Copilot Studio when something has to decide what to do. On agent flow actions the two cross over at roughly 144,000 actions a month, which is far higher than most teams expect.

The two price lists, side by side

Both products sit on the Power Platform price page, so buyers compare them directly. Here is what Microsoft currently lists in the US.

Notice that only one row on that table is a consumption line. Everything above it is a license that runs whatever you point it at. That single structural difference drives every decision below.

Why the two prices are not comparable as printed

A Power Automate Premium seat is attached to a person. That person can build and run cloud flows and attended desktop automation, and the price does not move with how much they run. A Process license is attached to a bot rather than a person, which is what makes unattended automation possible: nobody has to be signed in for the work to happen. Hosted Process is the same thing with Microsoft supplying the virtual machine so you do not have to.

Copilot Studio does not work like either. The maker license itself costs nothing. What you buy is a pool of Copilot Credits that the whole tenant draws from, and every action has a published price in credits. At $200 for 25,000 credits, each credit costs $0.008, and the rate card converts straight into dollars.

The spread across that table is the important part. The same $200 buys 333 minutes of premium voice or 192,000 flow actions. Anyone budgeting from an average credit price will be wrong by two orders of magnitude depending on which actions their agents actually take.

Where the two actually cross over

The honest break-even is on agent flow actions, because that is the one place the two products do genuinely overlap: a deterministic sequence of steps that could be run either by a Power Automate bot or by a flow invoked from a Copilot Studio agent.

One Process bot costs $150 a month and runs unattended flows without per-action metering. That same $150 buys 18,750 Copilot Credits, and at 13 credits per 100 agent flow actions, that is about 144,000 flow actions a month. A Hosted Process bot at $215 works out to roughly 207,000.

Most teams are nowhere near those numbers. If you are running a few thousand steps a month, invoking flows from a Copilot Studio agent is cheaper than dedicating a bot license to them. If you are running genuine high-volume back-office automation, the flat bot license wins and keeps winning, because it does not scale with volume at all.

The comparison breaks down completely for attended desktop RPA. Copilot Studio credits do not buy it at any price. If a robot has to drive a Windows application on someone's desktop, that is a Power Automate Premium seat or a Process bot, and no amount of credit budget substitutes. The main non-Microsoft option for that work is UiPath, which publishes a single $25 a month entry tier and quotes everything above it, so the comparison there starts from the numbers UiPath does publish rather than a price list.

The zero-rating rule that changes the answer

This is the single largest cost lever in Copilot Studio and it is easy to miss. Employee-facing agent use by a user who already holds a Microsoft 365 Copilot license is zero-rated. No credits are consumed.

If your organization already pays $30 per user per month for Microsoft 365 Copilot, internal agents built in Copilot Studio and used by those licensed employees do not draw on the credit pool at all. In that situation the comparison stops being $200 against $150 and becomes nothing against $150, and Copilot Studio wins any internal automation argument outright.

The rule does not extend to customer-facing agents. An agent that talks to people outside your tenant meters normally, and that is where credit budgets actually get consumed. Split your agent inventory into internal and external before you size anything, because the two halves have completely different economics.

The failure modes are different, and one is worse

A Power Automate bot license has no cliff. You pay $150, the bot runs, and if the volume doubles you pay the same $150.

Copilot Studio has two hard stops. Agent flows are cut off at 100% of prepaid capacity, and at 125% of prepaid capacity Microsoft disables custom agents entirely. Credits also expire monthly, so unused capacity is gone at the end of the billing period rather than banked against a busy quarter. That monthly clock is actually more forgiving than the annual one Salesforce runs on Agentforce Flex Credits, but it still means you are sizing a pool every month rather than once.

The practical consequence is that consumption pricing needs monitoring and license pricing does not. If you go the Copilot Studio route, watch burn rate against the pool from the first week, because the failure mode is an agent that quietly stops working rather than an invoice that quietly grows. Pay-as-you-go is available at roughly $0.01 per credit, which is 25% more than the prepaid rate but removes the cliff, and for a first deployment that premium is usually worth paying while you learn what your real volume is.

So which one should you buy?

In practice most organizations end up owning both, and that is the correct answer more often than not. Power Automate carries the deterministic back office and Copilot Studio handles the requests nobody could write a flowchart for. The mistake is buying one to do the other job, which is where the money goes.

The other mistake is buying either before you know which processes are worth automating. Licensing arguments are much easier to settle once you have ranked the work, and a short exercise to prioritize the automation backlog by value and effort will save more than any pricing trick on this page. Teams that skip that step tend to over-license, because nobody wants to be the person who blocked a project for want of a $15 seat.

Frequently asked questions

Is Copilot Studio included in Power Automate?

No. They are separate products with separate meters, sold on the same price page. A Power Automate Premium or Process license grants no Copilot Credits, and a Copilot Studio credit pack grants no Power Automate licenses. The maker license for Copilot Studio is free, but running anything consumes credits unless the zero-rating rule applies.

How much does Copilot Studio cost per month?

$200 per month for 25,000 Copilot Credits, paid yearly, which is $0.008 per credit. Pay-as-you-go runs about $0.01 per credit with no prepaid commitment. What that translates to in practice depends entirely on the actions your agents take: the same pack covers 5,000 agent actions, 12,500 generative answers or 333 minutes of premium voice.

Do Copilot Credits roll over?

No. Copilot Credits expire monthly, so unused capacity does not carry into the next billing period. Agent flows stop at 100% of prepaid capacity and custom agents are disabled at 125%, so both under-buying and over-buying have a cost.

Which is cheaper for unattended automation?

A Power Automate Process license at $150 per bot per month, once you are past roughly 144,000 agent flow actions a month. Below that, invoking flows from a Copilot Studio agent is cheaper, because $150 of credits buys about 144,000 flow actions at 13 credits per 100. Hosted Process at $215 shifts the break-even to around 207,000.

Do I need Power Automate if I have Copilot Studio?

You do if any of your automation is attended desktop RPA, because credits do not buy it. You also probably want it for high-volume deterministic work, where a flat bot license beats metering and removes the capacity cliff. For everything else, agent flows called from Copilot Studio cover the ground without a second license.

The option that avoids the licensing question

Both products ask you to buy the means of production and then find the value. That is reasonable when you have a long automation backlog and people to work it. It is expensive when what you needed was two or three specific jobs done.

If that is closer to your situation, look at deploying a ready-made agent against the systems you already run instead. There is no pool to size, no capacity cliff to monitor and no per-bot license to justify. Our Copilot Studio pricing breakdown goes deeper on the credit rate card, the Copilot Credits to dollars conversion covers what each action really costs, and if you are still choosing a platform at all, the Gemini Enterprise alternatives comparison puts Microsoft next to Google, AWS, Salesforce and Glean on price. For governing agents once they are running, Microsoft Agent 365 is the layer Microsoft sells for that, and the AI agent marketplace roundup covers where ready-made agents come from.