Free tool

Power Automate licence cost planner

Premium per-user, Process per-flow or Azure pay-as-you-go? Enter your team size and how often your flows run, and this planner prices all three routes side by side, flags the cheapest option and shows the exact crossover points where the maths flips. No sign-up needed.

Your team & flows

Users running premium flows People who trigger flows with premium connectors (SQL, SharePoint is standard, HTTP, ERP…)

Premium flows Separate flows needing premium connectors or unattended runs

Total flow runs / month All runs added together across those flows

Unattended desktop runs / month Optional RPA runs on a machine with no user watching

Unit prices (edit to your reseller rate)

Premium, per user / month

Process, per flow / month

Pay-as-you-go, per cloud run

Pay-as-you-go, per desktop run

Currency symbol

Route A

Premium per-user

–

per month

Route B

Process per-flow

–

per month

Route C

Azure pay-as-you-go

–

per month

Fill in your numbers above.

Route	Monthly	Annual	How it’s worked out
Premium per-user	–	–	–
Process per-flow	–	–	–
Pay-as-you-go	–	–	–

The crossover maths

–runs/month is where pay-as-you-go stops beating a single Process licence.

–users on one flow is where a Process licence gets cheaper than Premium seats.

–potential saving per month with the cheapest route.

Defaults use Microsoft’s published 2026 list prices: Premium $15 per user/month, Process $150 per flow/month, pay-as-you-go $0.60 per cloud run and $3.00 per desktop run (Azure meter, billed monthly with no licence). Regional and reseller pricing varies, so treat defaults as a starting point and edit to your quote. M365-seeded and Dynamics-based entitlements can change the picture, and daily Power Platform request limits apply per licence, so check the Microsoft licensing FAQ before you commit.

Which Power Automate licence actually fits?

Premium per-user suits people who build and run many flows themselves: one seat gives unlimited cloud flows including premium connectors, plus attended desktop RPA.

Process per-flow suits one important automated flow that serves a whole team: license the flow, not the people.

Azure pay-as-you-go suits low-volume or sporadic flows: you pay per run through an Azure subscription, and below roughly 250 runs a month it undercuts a Process licence.

Rule of thumb from the crossovers above: price the runs, then price the people — the cheaper of the two wins.