Microsoft Power Automate logo

Microsoft Power Automate

✓ Verified⭐ Featured

Enterprise automation for Microsoft 365

Visit Microsoft Power Automate →

About Microsoft Power Automate

Microsoft Power Automate is Microsoft's workflow automation tool, and the thing to understand first is that it is not really one product. It is three things sold under one name: cloud flows, which are the Zapier-style automations most people come for; desktop flows, which are robotic process automation that drives Windows applications through their user interface; and process mining, which analyses event logs to tell you which processes are worth automating. They are licensed differently, priced differently, and have different limits. Most of the confusion around Power Automate comes from comparison pages treating them as a single thing.

Common questions

How much does Power Automate cost?
Power Automate Premium is $15/user/month (cloud flows + attended desktop RPA). Process license is $150/bot/month (cloud flows + unattended RPA). Microsoft 365 users get 6,000 API requests/day free with standard connectors only. Premium connectors (Salesforce, SQL Server, HTTP with Azure AD, custom connectors) require a paid license. Licensing is per-user or per-bot, not per-task like Zapier.

What are Power Platform requests?
Every action in a cloud flow consumes a Power Platform request — API calls, HTTP actions, even built-in steps like initializing variables. Premium users get 40,000 requests per user per 24 hours. Process licenses get 250,000 requests per flow per day. Failed actions, retries and pagination all count. This quota resets daily with no rollover, so unused requests don't accumulate.

Can Power Automate replace Zapier?
For Microsoft 365-heavy organizations, yes — Power Automate excels at SharePoint, Teams, Outlook, Excel, Dataverse workflows with native authentication and governance. For multi-vendor SaaS integration, Zapier has broader third-party coverage and simpler per-task pricing. Power Automate's standard vs premium connector split catches teams by surprise when free Office 365 integrations hit premium-connector requirements.

What is desktop flow RPA?
Desktop flows drive Windows applications through their UI — clicking buttons, typing fields, reading screens — for software with no API. Attended flows require a signed-in user; unattended flows run on a Process license without human presence. This is Power Automate's unique capability versus Zapier/Make, useful for legacy systems that will never get modern APIs.

How the billing really works

Power Automate does not bill per task the way Zapier does, or per execution the way n8n Cloud does. It bills per seat or per bot, and then applies a separate daily ceiling called Power Platform requests.

The published plans are:

  • Power Automate Premium — $15.00 per user/month, paid yearly. Cloud flows plus attended desktop flows, 50 MB of process mining storage, and a small Dataverse allocation (250 MB database, 2 GB file).
  • Power Automate Process — $150.00 per bot/month, paid yearly. Cloud flows plus unattended desktop flows. Licensed to a flow rather than a person.
  • Power Automate Hosted Process — $215.00 per bot/month, paid yearly. The same as Process, plus a Microsoft-hosted virtual machine to run the RPA on, so you are not maintaining your own Windows box.
  • Process Mining add-on — $5,000.00 per tenant/month, paid yearly, on top of Premium.

There is a 30-day free trial, and it is limited to standard connectors only.

The second half of the pricing model is the part that bites. Every action in a cloud flow consumes a Power Platform request — and Microsoft's definition is broad. API calls to connectors count, but so do HTTP actions and built-in actions "from initializing variables to a simple compose action." Failed actions count. Retries count. Pagination requests count. A Premium seat is entitled to 40,000 requests per user per 24 hours, on a sliding window. A Process licence gives a flow 250,000 requests per 24 hours regardless of who runs it, and you can stack up to ten Process licences on one flow for 2.5 million. A flow group lets up to 25 solution-aware flows share one Process licence's 250,000. Separately, there is a five-minute ceiling of 100,000 requests that no licence raises.

Two details worth knowing before you plan capacity. The Premium entitlement is 40,000 requests per user per 24 hours — check Microsoft's current enforcement policy on the Power Platform admin centre, as transitional limits may differ from long-term entitlements. Design for the documented per-user limit. Desktop flow executions do not consume Power Platform requests at all — RPA is governed by its bot licence instead.

If you only have Microsoft 365, you already have a seeded Power Automate entitlement: 6,000 requests per user per 24 hours, standard connectors only.

The standard versus premium connector line

This is the single most common unpleasant surprise. Microsoft splits connectors into standard and premium, and the premium list is where most of the interesting third-party systems live — Salesforce, SQL Server, HTTP with Azure AD, Dataverse and custom connectors among them. The seeded Microsoft 365 entitlement covers standard connectors only. The moment a flow touches a premium connector, everyone who runs it needs a Premium seat or the flow needs its own Process licence. Teams routinely build a pilot on their existing Microsoft 365 licence, then discover the rollout has a per-seat cost attached.

Workflow patterns it suits

Anything inside the Microsoft estate. Approvals routed through Teams, SharePoint list changes, Outlook mail rules, Excel row processing, Dataverse records. If your data already lives in Microsoft 365, the connectors are first-party, the authentication is your existing tenant identity, and governance flows through the Power Platform admin centre. Nothing else competes here.

Approval workflows specifically. The Approvals action with its Teams and Outlook surfaces is genuinely strong and hard to replicate cleanly in Zapier or Make.

Legacy systems with no API. This is the real argument for desktop flows. If a business process depends on a Windows application or a terminal emulator that will never get an API, RPA driving the UI is the only automation available. Unattended desktop flows on a Process licence run without a human signed in.

Governed, auditable automation. Environments, data loss prevention policies, solution packaging and managed deployment pipelines are built in. For a regulated organisation that needs to prove who can connect what to where, this matters more than canvas ergonomics.

Where it gets hard

  • Licensing is genuinely difficult to reason about. Per-user and per-flow entitlements, seeded Microsoft 365 limits, the standard/premium split, Dataverse capacity and the transition period interact. Budget time to model it, and verify against the Power Platform admin centre's usage reporting rather than estimating.
  • Built-in actions consume your quota. Because a Compose or Initialize Variable counts as a request, verbose flows burn entitlement on bookkeeping. A loop over a few thousand rows with several internal actions per iteration consumes requests fast.
  • No rollover. Unused requests expire every 24 hours. They do not accumulate.
  • The editor is heavy. The designer is slower and more modal than Make's or n8n's canvas, and expressions use the Workflow Definition Language, which is powerful but unfriendly — long addDays(utcNow(), ...) strings are normal.
  • Request add-ons cannot be aimed at one flow. The $50,000-requests-per-day add-on applies to a user, not a flow. If a single flow is throttled, the fix is a Process licence or a flow group, not an add-on.

Who should pick it

Pick Power Automate if your organisation already runs Microsoft 365 or Dynamics 365, your automations mostly move data between Microsoft systems, and you need tenant-level governance. On those terms the per-seat price is competitive and the integration depth is unmatched. Pick it also if you genuinely need RPA against legacy Windows software, because few automation vendors offer that at all.

Pick Zapier instead if you want the largest library of third-party SaaS connectors and no licensing analysis. Pick Make if you want a more capable visual canvas for branching and data transformation. Pick n8n if you want per-execution pricing, self-hosting, or batch-shaped work where a per-action quota would be the constraint.

The honest summary: Power Automate is excellent value if you are already paying Microsoft and poor value if you are not.

Best For

Enterprise teams using Microsoft 365

✅ Pros

  • +Deep Microsoft integration
  • +AI Builder included
  • +Enterprise compliance

❌ Cons

  • -Complex licensing
  • -Microsoft ecosystem lock-in

Quick Info

Pricing
freemium
Starting at
$15/mo
Share:

Stay in the loop

Get weekly picks of the best no-code tools — straight to your inbox.

Frequently Asked Questions about Microsoft Power Automate

What is the pricing for Microsoft Power Automate?

Microsoft Power Automate offers a freemium pricing model, starting at 15/month.

What category does Microsoft Power Automate belong to?

Microsoft Power Automate belongs to the Workflow Automation, Automation Platforms categories.

What are the best alternatives to Microsoft Power Automate?

Check out our workflow automation category to discover the best alternatives to Microsoft Power Automate.