Power Automate Pricing Explained: What It Really Costs [2026]

Power Automate advertises a clean number: $15 per user per month. For a tool that does desktop RPA, cloud workflows, and AI, that looks almost too cheap next to Zapier or Workato. It usually is. The $15 sticker is the smallest number most organizations end up dealing with, because what you actually pay is decided by four things the pricing page does not put up front: which connectors your flows touch, whether automations run with a human watching, how many API requests they fire per day, and how the per-user and per-flow plans cross over as you scale.

This is a decode of the licensing bill — the part that surprises people after the pilot works and procurement asks "so what does rolling this out actually cost?" If you are weighing it against other platforms, our Zapier vs Power Automate and Make vs Power Automate breakdowns run the head-to-head; this post is about the Microsoft maze itself.

The 2026 plan lineup

Microsoft consolidated Power Automate's plans in 2023 (the old "Per User with Attended RPA" plan at $40 became "Premium" at $15, and "Per flow" became "Process"). Here is the current list pricing, billed annually:

Read that table and the cheap-looking plan is the seeded one bundled with Microsoft 365. That is exactly where the first hidden cost lives.

Layer 1: The seeded-license trap (standard vs premium connectors)

Every Microsoft 365 and Office 365 license includes Power Automate use rights. People see that and assume automation is "free, we already pay for Microsoft." It is free — for a specific, narrow definition of automation. Seeded rights cover standard connectors only: Outlook, SharePoint, Teams, OneDrive, Excel, Forms, Planner. Move data between Microsoft apps and you never pay a cent.

The trap is that the useful flows almost always reach outside that fence. A flow that reads a SQL Server table, calls an HTTP endpoint, hits a custom connector, writes to Dataverse, or syncs Salesforce uses a premium connector — and premium connectors are not in the seeded grant. The flow will build fine in the maker portal and then fail or demand a license the day it runs in production. To run it, the invoking user needs Premium ($15/user/mo), or the flow itself needs a Process license assigned.

Layer 2: Attended vs unattended RPA

Power Automate's desktop RPA is a real reason teams pick it over cloud-only tools. But RPA splits into two licensing worlds, and the gap between them is the steepest price jump in the catalog.

• Attended RPA — a bot that runs while a human is signed in and watching. This is included in Premium at $15/user/mo. Good for "click this for me" desktop tasks.
• Unattended RPA — a bot that runs on its own, on a schedule, with nobody logged in. This is the automation that actually replaces manual back-office work, and it requires a Process license at $150/bot/mo (or Hosted Process at $215/bot/mo if you also want Microsoft to host the VM it runs on).

So the headline RPA story ("$15 and you get robotic process automation") is true only for the supervised version. The version most ROI cases are built on is 10× the price per bot. If unattended RPA at scale is your goal, Power Automate's true entry point is $150–$215 per concurrent bot, not $15.

Layer 3: The request caps nobody mentions

Each license tier carries a daily ceiling on Power Platform requests — connector calls, action executions, and trigger checks. Hit the ceiling and your flows throttle until the 24-hour window resets. This is the Power Automate equivalent of the "what counts as a task" question that trips people up on usage-based tools (we cover that pattern in what counts as a task).

The number that catches teams is the seeded 6,000/day. A single moderately busy flow — one that loops over rows, calls a connector per row, and runs a few times an hour — can burn through 6,000 actions before lunch. The "free with Microsoft 365" automation quietly throttles, and the fix is, again, a paid license with a higher ceiling.

Layer 4: The per-user vs per-flow crossover

Once you accept you are paying, the real optimization is choosing between licensing people (Premium) and licensing flows (Process). The arithmetic is simple. Premium is $15 × number of users. One Process license is a flat $150 and can be shared by everyone who uses that flow.

There is a multiplier most cost models miss: Process licenses are scoped per environment. Run the same unattended bot in Dev, Test, and Prod and that is three Process licenses, not one — $450/mo for a single automation across a normal application-lifecycle setup. Enterprises evaluating Power Automate against Workato or Boomi should model environments into the comparison; our enterprise iPaaS quote decode walks through how those vendors hide their own multipliers.

What this bill still doesn't count

Everything above is the licensing cost. Honest TCO for an enterprise rollout adds line items that never appear on the pricing page:

• Dataverse capacity. Premium and Process include a small Dataverse allotment (250 MB / 50 MB database). Real deployments exceed it, and overage is a separate paid capacity add-on.
• On-premises data gateway. Connecting to on-prem SQL or file shares means standing up and maintaining gateway servers — infrastructure and admin time, not a SKU.
• Governance and CoE. At scale you need a Center of Excellence, environment strategy, and DLP policies. That is headcount, and for most organizations it dwarfs the license spend.

None of these are reasons to avoid Power Automate. They are reasons to stop quoting "$15/user" as the answer to "what does it cost," and a fair comparison to alternatives has to put them on both sides of the ledger.

The 2026 catch: AI Builder credits are going away

If part of your business case is the AI inside Power Automate — document processing, prediction, text recognition — note a packaging change. Premium and Process plans have included roughly 5,000 AI Builder credits per user/month, and standalone AI Builder capacity packs sell at $500 per 1 million credits. Microsoft has announced that the seeded AI Builder credits bundled with these licenses will be removed on November 1, 2026; after that, AI Builder features draw on Copilot Credits or active paid add-ons. Capacity add-ons already stopped being sold to new customers as of November 1, 2025.

Practically: if AI is core to your flows, do not assume the bundled credits will still be there in 2027. Budget for Copilot Credits or an add-on as a separate, ongoing line.

So who is each plan actually for?

• Stay on seeded M365 rights if your flows only move data between Microsoft apps and stay under ~6,000 actions/day. This really is free.
• Buy Premium when individuals need premium connectors or attended desktop automation, and you have fewer than ~10 people sharing any given process.
• Buy Process when an unattended bot runs a shared business process, or when 11+ users hit the same premium flow — and remember to count environments.
• Use pay-as-you-go for spiky, low-frequency flows where a $0.60/run meter beats a standing monthly license.

If the licensing maze pushes you to look elsewhere, the Power Automate alternatives roundup compares simpler per-task and per-operation models — and the Zapier pricing decode and cost of leaving Zapier are useful if you are moving in the other direction.

FAQ

Is Power Automate really free with Microsoft 365?

Partly. M365 includes Power Automate with standard connectors and a daily request cap (~6,000/day). It is genuinely free for Microsoft-app-to-Microsoft-app automation. Any flow using a premium connector (SQL, HTTP, custom, Dataverse, Salesforce) needs a paid Premium or Process license.

What's the difference between Premium and Process?

Premium ($15/user/mo) licenses a person and includes attended RPA. Process ($150/bot/mo) licenses a single flow that unlimited users can share and is what unattended (lights-out) RPA requires. Past ~11 shared users, Process is cheaper per process.

Why did my flow stop running mid-month?

Most often a daily Power Platform request limit. Seeded M365 licenses cap around 6,000 requests/day; a busy loop-heavy flow can exhaust that and throttle until the window resets. A higher tier raises the ceiling.

Do I need a separate Process license for each environment?

Yes. Process licenses are scoped per environment, so the same unattended bot running in Dev, Test, and Prod consumes three licenses. Factor that into any cost model.