Microsoft Power Automate occupies an awkward spot for buyers. The entry price looks trivial next to dedicated RPA vendors, but the licensing model has enough moving parts that teams routinely budget one line item and pay for three. This review covers Microsoft's published 2026 pricing, the documented throughput limits that decide whether a workflow survives production, and the work the product is actually built for.
A note on method: every figure below comes from Microsoft's current pricing and licensing documentation or from public aggregate review data, linked inline. Nothing here is drawn from a private test rig.
What You Are Actually Buying
Power Automate is three products sharing a portal. Cloud flows are API-driven automations that connect services through standard, premium, and custom connectors. Desktop flows are robotic process automation — the component that drives legacy Windows applications by simulating keyboard and mouse input when no API exists. Process mining analyzes event logs to find where a business process is actually losing time.
The distinction matters because the licensing is organized around it. Microsoft splits licenses into user licenses, assigned to a person, and capacity licenses, allocated to an automation — a cloud flow, a machine, or a hosted machine group. Confusing the two is the most common source of surprise invoices.
Power Automate Pricing in 2026
Per the official Power Automate pricing page, the current published rates are:
- Power Automate Premium — $15.00 per user/month, paid yearly. Cloud flows, attended desktop flows, process and task mining (50 MB), and Dataverse capacity of 250 MB database plus 2 GB file storage.
- Power Automate Process — $150.00 per bot/month, paid yearly. Cloud flows and unattended desktop flows, with 50 MB database and 200 MB file storage.
- Power Automate Hosted Process — $215.00 per bot/month, paid yearly. The same as Process, plus a Microsoft-hosted virtual machine so you run RPA without maintaining infrastructure.
- Power Automate Process Mining add-on — $5,000.00 per tenant/month, paid yearly, for 100 GB of data storage. It requires a Premium base license.
- Microsoft Copilot Studio — $200.00 for 25,000 Copilot Credits/month, paid yearly.
All three main tiers include 5,000 AI Builder credits per month, standard, premium and custom connectors, business process flows, and on-premises gateways, according to the Microsoft Learn license comparison.
The Free and Trial Tiers Are Narrower Than They Look
The Power Automate Free license covers creating and running cloud flows without sharing them, plus authoring and running desktop flows locally in attended mode — standard connectors only. The 30-day free trial on the pricing page is similarly limited to UI-based cloud flows and standard connectors. Separately, a 90-day Power Automate trial license grants Premium-equivalent capability minus AI Builder credits and storage capacity, and it does include unattended desktop flow runs. That is the tier worth using for a genuine proof of concept.
Where Costs Escalate
Two documented rules drive most budget overruns. First, capacity licenses do not replace user licenses. Registering a machine for unattended RPA still requires a Power Automate Premium user, and triggering a desktop flow from a cloud flow running under a Process license requires the connection owner to hold Premium. Several monitoring surfaces in the portal — the work queue page, machine list, desktop flow list — are only visible to Premium users at all.
Second, parallelism is bought, not configured. One Process license equals one unattended bot running one desktop flow at a time. Running five unattended automations concurrently means five Process licenses. At $150 each, a modest RPA program reaches five figures annually before anyone writes a flow.
One caveat buyers should verify against their own tenant: Microsoft's documentation notes that the Hosted Process "superset" behavior — applying a Hosted Process license to standard machines and cloud flows — is not yet available, and advises organizations with Process overage that would be covered by Hosted Process licenses to disregard that overage in the interim.
Performance: The Limits That Actually Govern Throughput
Power Automate does not throttle on wall-clock speed so much as on Power Platform requests (PPR), where nearly every action counts — connector calls, HTTP actions, and built-in actions down to initializing a variable. Failed actions, retries, and pagination all count too. Microsoft's request limits documentation publishes these official daily allocations:
- Power Automate Premium: 40,000 requests per user per 24 hours
- Process and Hosted Process: 250,000 requests per license
- Power Automate Free and Office 365 seeded licenses: 6,000 requests per user
A separate five-minute ceiling of 100,000 requests applies regardless of license. Two details work in buyers' favor: desktop flow executions do not consume Power Platform requests at all, and up to 10 Process licenses can be stacked on a single cloud flow, each adding 250,000 daily actions, provided the flow lives in a solution.
Crucially, all organizations are currently in a transition period with more generous enforced limits — 200,000 per cloud flow for Premium, 500,000 per license for Process — and Microsoft states enforcement will not tighten until at least six months after admin center usage reporting reaches general availability. Architect against the official numbers, not the transitional ones.
Use Cases Worth Licensing For
The product's documented strengths map to patterns rather than industries. Approval routing across Teams, Outlook and SharePoint is the canonical starting point, since those standard connectors are reachable even on seeded Microsoft 365 entitlements. Document-heavy intake work suits the included AI Builder credits, which cover form processing and text extraction. Legacy system bridging — driving a terminal emulator or an ERP client with no API — is what justifies Process or Hosted Process licenses, with Hosted Process suiting teams who would rather not manage VMs.
Where Reviewers Consistently Push Back
G2 lists Power Automate at roughly 4.4 out of 5 across approximately 1,000 reviews, and the recurring criticisms are consistent across review platforms: vague error messages that make failed runs hard to trace to a specific step, inconsistent performance on flows with complex branching or many connectors, and a steep difficulty curve once automations move past simple notification and approval patterns. Reviewers new to the Microsoft ecosystem also describe onboarding as overwhelming.
What Is Landing Through September 2026
The 2026 release wave 1 plan, covering April through September 2026, concentrates on four areas: self-healing desktop automations that adapt when target systems change, Copilot Studio-powered actions plus the ability to call desktop flows directly from Copilot Studio, object-centric process mining with native Microsoft Fabric integration and an MCP server, and consolidated licensing and usage reporting in the Power Platform admin center. That last item is the one to watch, since improved reporting is the stated precondition for stricter limit enforcement.
The Verdict
Power Automate is the rational default for organizations already standardized on Microsoft 365, where seeded entitlements let teams prove value before spending anything. At $15 per user, Premium is inexpensive for cloud automation. The honest warning is that RPA at scale is a different purchase entirely — one priced per concurrent bot, dependent on Premium user licenses underneath it, and governed by daily action limits that most teams do not model until a flow starts throttling. Estimate your actions per run multiplied by runs per day before committing, and treat the transition-period limits as temporary headroom rather than capacity you own.