Power Automate Pricing in 2026: Premium vs Process, and the Licensing Rule That Multiplies the Bill
As of October 10, 2026, Microsoft lists Power Automate Premium at $15 per user a month and Process at $150 per bot a month, paid yearly, and many businesses already have a standard-connector version through Microsoft 365. An automated premium flow needs only its owner licensed, but if it sends value back to the people who trigger it, each of them needs Premium; past 10 such users, a $150 Process license on the flow is cheaper.
How much does Power Automate cost? The short answer
As of October 10, 2026, Microsoft lists Power Automate Premium at $15 per user a month, Power Automate Process at $150 per bot a month and Hosted Process at $215 per bot a month, all paid yearly, with a 30-day free trial. Many businesses already have a limited version through Microsoft 365, which runs standard connectors only with 6,000 actions per user a day. The licensing rule that sets the bill: an automated flow with premium connectors needs only its owner licensed, but if the flow sends value back to the people who trigger it, every one of them needs Premium, unless the flow itself gets a $150 Process license.
Prices come from Microsoft's Power Automate pricing page; licensing rules and action limits come from Microsoft Learn's Power Automate licensing FAQ and its Power Platform request limits page. All three were read October 10, 2026. Microsoft notes its listed prices are for marketing purposes and the actual price appears at checkout, so confirm in your own admin center before you buy.
What you may already own through Microsoft 365
Microsoft's licensing FAQ lists Office 365 E1, E3, E5, F1, F3, Business Basic, Business Standard and Business Premium among the licenses that include Power Automate. Microsoft describes that as limited use rights for personal productivity. In practice two limits decide whether it is enough:
- Standard connectors only. Users on Microsoft 365 or the free plan cannot use premium or custom connectors. If a flow does not use a premium connector, Microsoft says a Microsoft 365 license is enough.
- 6,000 actions per user per 24 hours. The same limit applies to the free plan and all trials. Limits do not pool: 8 Microsoft 365 users each get 6,000, not a shared 48,000.
Power Automate plans and prices
| License | Price, paid yearly | Who or what it covers | Connectors | Daily action limit |
|---|---|---|---|---|
| Microsoft 365 (seeded) | Included in the Microsoft 365 license | Each licensed user | Standard only | 6,000 per user |
| Power Automate Premium | $15 per user a month | Each licensed user: cloud flows, attended desktop flows, process mining with 50 MB of data | Standard, premium and custom | 40,000 per user |
| Power Automate Process | $150 per bot a month | One flow, or a group of up to 25 flows, regardless of who runs it; unattended desktop flows | Standard, premium and custom | 250,000 per license, stackable up to 10 on one flow |
| Power Automate Hosted Process | $215 per bot a month | Same as Process, plus a Microsoft-hosted virtual machine | Standard, premium and custom | 250,000 per license |
| Process Mining add-on | $5,000 per tenant a month | Premium plan add-on, 100 GB of process data | Not applicable | Not applicable |
Two other numbers are worth knowing. A Process bot runs one unattended desktop flow at a time, so concurrent desktop runs need more bots. And every flow also has a five-minute ceiling of 100,000 requests, whatever its license.
Who needs a license: the owner rule and the multiplexing rule
This is where Power Automate bills go wrong, in both directions. Microsoft's licensing FAQ sets out three rules:
- Automated and scheduled flows run as their owner. If one uses a premium connector, only the owner needs Premium, no matter who starts it or whose connections it uses.
- Instant flows run as the person who presses the button. If an instant flow (a button, or a flow called from Power Apps) uses a premium connector, every user who runs it needs Premium, or the flow needs a Process license.
- Multiplexing is a license violation. Microsoft's own example: a premium flow that fires when someone adds an item to a SharePoint list and emails only the owner needs only the owner licensed. If the same flow emails the person who uploaded the item, that person is getting value from a premium flow, and they need Premium too.
A worked example: a 25-person firm automating document intake
A 25-person accounting firm already pays for Microsoft 365. Staff save client documents to a SharePoint library; a flow picks each one up, sends it through an AI step that reads the document and fills in the client, form type and tax year, writes the result to a tracking list, and alerts someone. The AI step uses a premium connector. Roughly 600 documents a month come in, and the flow runs about 25 actions per document (trigger, get file, compose, AI call, parse, conditions, list update, email). Here is what the same flow costs under three designs, at Microsoft's listed prices:
| Design | What Microsoft's rules require | Monthly | Yearly |
|---|---|---|---|
| A. Results go to the tracking list; the alert goes to the flow owner only | 1 Premium license (the owner) | $15 | $180 |
| B. Same flow, but it emails each staff member a confirmation for their upload | Premium for everyone who uploads and gets the email: 25 x $15 | $375 | $4,500 |
| C. Design B with a Process license assigned to the flow | 1 Process license; users need no Premium for this flow | $150 | $1,800 |
The finding: one email step moves this flow from $180 a year to $4,500, and the Process license is the cheaper fix once more than 10 people would otherwise need Premium ($150 divided by $15). Fewer than 10, license the people; more than 10, license the flow. Design A is the cheapest of all, and often the better process: put the confirmation in the shared list instead of in 25 inboxes.
The action budget is not the constraint here. 600 documents x 25 actions is 15,000 actions a month, about 500 a day, and even a tax-season week at three times that volume stays well under the 40,000 a day on Premium. Polling is what breaks the cheap tier: a scheduled flow that checks a mailbox every minute and runs 5 actions per check uses 7,200 actions a day, which is over the 6,000 a Microsoft 365 user gets.
The action limits, and the transition period
Every trigger and every action counts toward the daily limit, including built-in steps such as initializing a variable or a compose action, not only connector calls. Desktop flow actions do not count, except the desktop flows you call from a cloud flow. The 24 hours is a sliding window.
Microsoft is currently in a transition period. Until it ends, Microsoft applies limits per cloud flow rather than per user: 10,000 a day per flow for Microsoft 365 and free users, 200,000 per flow for Premium, and 500,000 per Process license. Microsoft tells makers to design for the per-user limits (6,000, 40,000 and 250,000) that take over when the transition ends. Its licensing FAQ also says a flow that stays above the transition limits for 14 consecutive days is suspended, and a premium flow whose owner loses their Premium license is downgraded and turned off after 14 days if nobody acts. Plan the owner of every important flow as carefully as you plan its license.
Power Automate vs Zapier, Make and n8n
Power Automate is usually the cheapest choice for a business that already lives in Microsoft 365: the standard connectors are already paid for, and one Premium owner can run many automated flows. The other platforms bill by usage rather than by who owns the flow, which suits teams outside Microsoft or with workloads that cross many non-Microsoft apps. Our n8n vs Make vs Zapier comparison prices the same workload on each, and our guide to business process automation software covers where each one fits in a stack.
Who can build Power Automate flows for my business?
Simple personal flows (save attachments, post a Teams message, copy a form response into a list) are worth building yourself with the Microsoft 365 license you already have. Bring in a builder when the flow becomes a business process: premium or custom connectors, an AI step reading documents or emails, a solution-aware setup with a service account and a named owner, and a licensing design that stays on the right side of the multiplexing rule. SuperDupr builds that layer, in Power Automate when it is the right tool and in custom code when the volume or the licensing math says otherwise; we do not resell Microsoft licenses. That is an AI workflow automation project for us, published at $10,000 to $25,000, live in 2 to 4 weeks for most AI systems, with support at $200 to $2,000 a month depending on volume. The first step is a free 30-minute strategy session. To compare that with other builders, see our breakdowns of AI automation pricing and the best AI automation agencies.
Sources
- Microsoft Power Automate pricing, microsoft.com/en-us/power-platform/products/power-automate/pricing, read October 10, 2026: Premium $15 per user a month, Process $150 and Hosted Process $215 per bot a month, Process Mining add-on $5,000 per tenant a month (all paid yearly), free trial with standard connectors only, plan contents, Dataverse entitlements, one-run-at-a-time bot footnote, marketing-price disclaimer.
- Power Automate licensing FAQ, learn.microsoft.com/en-us/power-platform/admin/power-automate-licensing/faqs, read October 10, 2026: owner and invoking-user license context, Microsoft 365 standard-connector rule, multiplexing examples, Process license priority and flow groups, daily action limits by license, what counts as an action, 14-day suspension and owner-downgrade rules, Office 365 licenses that include Power Automate.
- Power Platform request limits and allocations, learn.microsoft.com/en-us/power-platform/admin/api-request-limits-allocations, read October 10, 2026: requests per license per 24 hours, transition-period limits per cloud flow, 100,000-request five-minute limit, Process license stacking.
- Worked example: SuperDupr's arithmetic on the published prices and limits above, for an assumed 25-person firm with 600 documents a month.
Frequently Asked Questions
-
As of October 10, 2026, Microsoft lists Power Automate Premium at $15 per user a month, Power Automate Process at $150 per bot a month and Hosted Process at $215 per bot a month, all paid yearly, plus a $5,000-a-month Process Mining add-on. Microsoft notes the final price shows at checkout.
-
A limited version is. Office 365 E1, E3, E5, F1, F3, Business Basic, Business Standard and Business Premium include Power Automate with standard connectors only and 6,000 actions per user per day. Premium and custom connectors need Power Automate Premium, a Process license or another qualifying license.
-
Not always. An automated or scheduled flow runs as its owner, so if it uses a premium connector only the owner needs Premium. An instant flow, such as a button, runs as whoever presses it, so every runner needs Premium. And under Microsoft's multiplexing rule, people who trigger a premium flow and get something back from it, such as a confirmation email, need Premium too.
-
Premium licenses a person ($15 a month) for all their flows with 40,000 actions a day. Process licenses a flow or a group of up to 25 flows ($150 a month) with 250,000 actions a day, regardless of who runs it, and adds unattended desktop automation. Process is cheaper than Premium once more than 10 people would need Premium for the same flow.
-
Per 24 hours: 6,000 actions per user on Microsoft 365 and the free plan, 40,000 per user on Premium and 250,000 per Process license. Every trigger and action counts, including built-in steps like compose. During Microsoft's current transition period the limits are applied per flow instead: 10,000, 200,000 and 500,000. There is also a 100,000-request limit per five minutes.