Power Automate can save teams thousands of hours — but its licensing confuses almost everyone, because it mixes two very different things under one name: everyday cloud flows and full robotic process automation (RPA). This guide separates them, lays out 2026 pricing, and shows you how to license automation without overspending or, worse, discovering mid-project that the plan you bought can’t do what you need.

There are three things to understand: the flows already included with Microsoft 365, the per-user Power Automate Premium plan ($40/user/month), and the per-process Power Automate Process plan ($150/bot/month) for unattended automation at scale. Get those three straight and the rest is detail.

It helps to know why this feels harder than it should. Power Automate grew by absorbing two separate worlds — lightweight workflow (the old “Microsoft Flow”) and enterprise RPA (desktop automation) — into one product. The licensing still reflects that history: one meter for people doing everyday and attended work, another for processes running unattended at volume. Once you see the seam, the pricing stops looking arbitrary and starts looking logical.

Two kinds of automation (this is the whole confusion)

• Cloud flows / DPA — API-based automation that connects apps and services (e.g. “when a form is submitted, create a record and send an approval”). This is what most people mean by Power Automate, and it’s the everyday workhorse.
• Robotic Process Automation (RPA) / desktop flows — UI-based automation that drives legacy apps with no API, by mimicking clicks and keystrokes. RPA runs either attended (a person is present) or unattended (fully hands-off, often overnight).

How Power Automate licensing actually works

Behind the plan names, Power Automate licensing answers three questions in order:

1. API or UI? If your automation talks to systems through their APIs (modern apps, connectors), that’s a cloud flow. If it has to operate a screen because there’s no API, that’s RPA/desktop flow.
2. Standard or premium connectors? Cloud flows on standard connectors are usually covered by Microsoft 365. Premium and custom connectors need a paid plan.
3. Attended or unattended? If a person is present, it’s attended (Premium, per user). If it must run with nobody logged in, it’s unattended (Process, per bot).

Walk any automation through those three questions and its licence is determined. We use exactly this sequence to scope every automation request before a line is built.

The Power Automate plans at a glance

Power Automate Premium: $40/user/month

Power Automate Premium is the per-user plan for people who build and run real automation. At $40 per user per month it unlocks all premium and custom connectors, cloud flows, attended desktop flows (RPA), AI Builder capacity, and process mining. If a specific person automates their own work — including driving legacy desktop apps while they’re logged in — Premium is what they need.

Premium is the natural home for “citizen developers” and process owners who build and maintain a portfolio of automations. Because it’s per-user, cost scales cleanly with the number of people building and running attended automation — not with the number of flows they create, which is unlimited. One Premium user can own dozens of cloud flows.

Power Automate Process: $150/bot/month

Power Automate Process (formerly the “unattended” / per-flow plan) is licensed by the process, not the person. At $150 per bot per month, it lets a single automation run unattended — no user logged in, no one watching — which is how you automate high-volume back-office work like overnight data entry, invoice processing, or system-to-system syncs.

Because it’s tied to a process rather than a head, one Process licence can serve an entire department’s automation, and its economics are about throughput, not headcount. The question isn’t “how many people use it?” but “how much work does this bot get through, and what does that work cost us to do manually?” A single $150/month bot that replaces hours of daily manual keying usually pays for itself many times over — which is exactly the calculation to run before buying.

Attended vs unattended RPA: the distinction that decides your plan

Most automation programmes use both: attended bots that help staff during the day, and unattended bots that grind through volume at night. Licensing them correctly means counting users for the attended side and processes for the unattended side — two different meters for two different jobs.

Hosted RPA & machines

Unattended RPA has to run somewhere. Traditionally that meant provisioning your own virtual machines to host the bots. Microsoft also offers hosted RPA — Microsoft-managed machines you rent so you don’t have to build and maintain the infrastructure yourself. It’s an add-on cost, but for many organisations it’s cheaper and far simpler than running a fleet of always-on VMs. When you budget for unattended automation, remember the equation is Process licence + a machine to run it on, whether that machine is yours or hosted.

Free flows included with Microsoft 365

Most Microsoft 365 plans already include Power Automate rights for cloud flows using standard connectors — approvals, notifications, and SharePoint/Teams automation. If your flows only touch Microsoft 365 data and don’t need RPA, you may not need to buy anything at all. The paid plans start mattering the moment you need premium/custom connectors or robotic process automation. As with the rest of the Power Platform, audit what your M365 licences already grant before buying — a surprising amount of everyday automation is already covered.

AI Builder & process mining

Two capabilities bundled into Premium are worth understanding because they change what automation can do:

• AI Builder lets flows read documents, extract fields from invoices, detect objects in images, and make predictions. Premium includes an AI Builder allocation; very high volumes may need an add-on capacity.
• Process mining analyses how your processes actually run (from event logs) so you can find the bottlenecks worth automating. It’s the difference between automating on a hunch and automating where the data says the time is really lost.

Together they turn Power Automate from a workflow tool into a genuine process-improvement platform — but they also mean “automation” can consume AI capacity, so factor that into heavy-use budgets.

Power Automate plan comparison

Which Power Automate plan do you need?

Worked example: automating invoice processing

Request limits, throttling and “capacity” you didn’t know you were using

One under-discussed part of Power Automate licensing is the daily API request limit. Every action a flow performs — reading a row, sending an email, calling a connector — counts as a request, and each licence type carries a daily allowance of these requests per user. Ordinary flows never come close, but a high-frequency flow (say, one polling a system every minute, or looping over thousands of records) can hit throttling limits. When that happens, the fix is usually better flow design — batching, filtering at the source, avoiding needless loops — rather than more licences. It’s worth knowing the limits exist so a badly-designed flow doesn’t get misdiagnosed as a licensing shortfall.

The practical takeaway: build flows that do the minimum work necessary, and you’ll stay comfortably inside your entitlement. Efficient design is a cost-control lever in its own right.

Security: data loss prevention isn’t optional

Because Power Automate can connect almost anything to anything, it introduces a real data-governance question: what stops someone building a flow that pushes confidential data from a business system into a personal email or a consumer service? The answer is Data Loss Prevention (DLP) policies — rules that classify connectors as “business” or “non-business” and prevent the two groups being mixed in a single flow. DLP is part of governing the platform, not a paid add-on, but it must be configured deliberately. In any automation programme of meaningful size, DLP policy design belongs in the plan from the start — it protects you from the flip side of Power Automate’s greatest strength: how easily it connects things.

Governance: keeping Power Automate costs under control

• Separate the two meters. Track attended (per-user Premium) and unattended (per-process) automation independently — they scale on different things.
• Don’t over-provision Process bots. A single bot can often handle several sequential processes; parallelism, not process count, is what drives extra licences.
• Right-host unattended RPA. Hosted machines vs self-managed VMs is a real cost lever — pick based on volume and your infrastructure appetite.
• Run a Centre of Excellence. Microsoft’s free CoE Starter Kit surfaces every flow, its owner and its connectors — essential to prevent ungoverned automation becoming a security and cost liability.

Costly Power Automate licensing mistakes

• Buying Premium for unattended jobs. Unattended automation needs Process, not per-user Premium — a common blocker discovered late.
• Buying Process for one person’s attended tasks. At $150/bot it’s overkill for a single user driving their own desktop app — Premium is cheaper.
• Forgetting the machine. Unattended RPA needs a bot licence and a machine to run on — budget both.
• Paying for what M365 already includes. Standard-connector cloud flows are usually already covered.
• No centre of excellence. Sprawling ungoverned flows create security and cost risk — establish ownership and monitoring early.

Building the automation business case

The right way to decide any Power Automate spend is to compare it against the cost of not automating. A simple, honest business case has four inputs:

1. Volume — how many times the process runs (per day, week, month).
2. Time per run — how long it takes a person to do it manually, end to end.
3. Error rate — how often manual handling causes mistakes, and what those cost to fix.
4. Time-sensitivity — whether delays have a downstream cost (late invoices, missed SLAs, customer impact).

Multiply volume by time per run and you have the monthly hours a bot would give back; weigh that against the licence plus machine cost, and the decision usually makes itself. Crucially, this framing also tells you which processes not to automate — low-volume, low-value tasks rarely justify even a $40 seat, and automating them is a common way to waste money and effort. Automation pays when it’s pointed at high-volume, repetitive, error-prone work; the business case is how you find those processes rather than guessing.

It’s also why we resist the temptation to “automate everything.” The goal is not the most flows, it’s the highest return — a handful of well-chosen automations on the right licences will out-perform a sprawl of trivial ones every time.

How PraviMinds helps

We build automation across the Power Platform — cloud flows, attended and unattended RPA — and license it correctly from day one. We map each automation to the right plan (seeded, Premium, or Process), build the business case from the manual baseline, right-host the bots, and set up governance so your automation programme scales without surprises. If you’re weighing an RPA or workflow project, we’ll size it properly before you commit.

About the author

Devansh Parmar

Technical Director, Dynamics 365 — PraviMinds

Devansh leads PraviMinds’ Microsoft Dynamics 365 practice, helping businesses implement, customise, and integrate D365 CRM and ERP. He writes practical guides on getting real business value from the Microsoft stack.

Connect on LinkedIn →

Frequently asked questions