Commercial disclosure: The product links are direct, non-tracked official links. ChoiceRidge does not currently earn commission from them, and commercial arrangements do not determine this verdict.
Decide the execution and ownership model first
Power Automate deserves a shortlist when your process belongs in a Microsoft environment and the organization can govern the connections, identities and operating support. Before comparing prices, separate cloud automation from desktop work, identify who invokes the process, and determine who owns the unattended outcome. A Microsoft 365 subscription or an existing flow is not evidence that every proposed scenario is licensed.
Research update — October 16, 2026: the licensing and flow-limit documentation linked below informed this evaluation framework. Existing price references remain August 12, 2026 research; this update is not a new quote. ChoiceRidge has not run an enterprise tenant, desktop automation benchmark or licensing audit for this review.
| Work to automate | Design question | Acceptance evidence |
|---|---|---|
| Cloud workflow using service connections | Which identity owns the flow, connections and required permissions? | Approved connectors, account lifecycle, license scope and a recovery owner |
| Desktop interaction | Does a person attend the session, or must it execute without one? | Confirmed execution entitlement, machine/session availability, credentials and exception handling |
| Business process shared across people | How is the process licensed and supported beyond its original maker? | Written user/process scope, environment ownership and an administrator-approved handover |
| Long-running approval | What happens when no one responds before the run expires? | Durable business state, explicit timeout/escalation and a tested resume or restart procedure |
Example: an approval that must survive an absent approver
Consider a hypothetical purchase request that waits for manager approval before creating an external order. Store the request’s business status and identifier in a suitable durable record. Validate the approval response against the current request, then make the external write with a duplicate-prevention strategy. Avoid using a long-lived workflow run as the only record of what the business owes someone.
Microsoft documents duration and concurrency limits for cloud flows, including pending approvals. Design an explicit escalation and expiration policy against the current limits; do not assume an approval can wait indefinitely. Keep enough context to decide whether a restart would repeat an already completed external action.
Test a rejected request, a delayed response, a disabled connection and a timeout after the destination accepts the order. For each, record the business status, notification, repair action and owner. These are proposed acceptance checks, not a report of ChoiceRidge’s hands-on results.
Governance that belongs in the purchase decision
Ask the administrator to approve the environment, connector/data policy, identity model and deployment path. Separate test connections and data from production. Record which changes need review, how connection references and configuration travel between environments, and who can restore a previous version without replaying business transactions.
Measure workload in the units that apply to your design and licensing model. Request entitlements, connector throttling, concurrency and desktop capacity are different constraints. A plan name alone does not prove throughput. Compare the required number of users/processes/machines and operational support; do not normalize them to a generic Zapier task or Make credit.
Decision rule
Choose Power Automate when the Microsoft integration benefit survives the licensing review and there is a funded owner for failures and account changes. If the process is a small SaaS integration outside that governance model, compare the operating burden with Make versus Power Automate. For a desktop-dependent process, assess whether a supported API can remove the desktop dependency before committing to UI automation.
Sources reviewed October 16, 2026: types of Power Automate licenses and cloud flow limits. Obtain a current scenario-specific licensing answer before purchase.
Microsoft Power Automate spans cloud workflows, approvals, connectors, process automation, and desktop robotic process automation. It is most attractive to organizations already operating Microsoft 365, Azure, Dynamics, Dataverse, Entra, and Power Platform governance. It is also fundamentally different from SaaS-only workflow tools because desktop flows can automate Windows and legacy interfaces. That breadth creates licensing complexity: user, Process, Hosted Process, connectors, capacity, environments, and attended versus unattended RPA must be mapped before purchase.
Commercial disclosure: The product links are direct, non-tracked official links. ChoiceRidge does not currently earn commission from them, and commercial arrangements do not determine this verdict.
Quick verdict
Power Automate is best for Microsoft-centric businesses and teams that need cloud automation plus desktop RPA.
Microsoft Power Automate at a glance
| Area | Finding | Decision impact |
|---|---|---|
| Premium | $15/user/month paid yearly | Cloud flows and attended RPA development |
| Process | $150/bot/month paid yearly | Unattended RPA or business processes |
| Hosted Process | $215/bot/month paid yearly | Microsoft-hosted machine capacity |
| Trial | 30 days listed | Validate licensing and connectors |
Pricing and licensing explained
Premium is user-oriented; Process licenses an automation bot or business process; Hosted Process adds hosted machine capacity. Unattended desktop flows require appropriate Process coverage. Connector classification, action limits, environments, AI Builder, and user context can change the complete license requirement.
Features and operating model
Cloud flows
Automated, scheduled, instant, and approval workflows across connectors.
Desktop flows
Attended and unattended RPA for Windows and legacy interfaces.
Microsoft governance
Environments, DLP, Entra identity, solutions, and administration.
AI and process tools
Copilot, AI Builder, and process mining have separate eligibility and capacity considerations.
Security, governance, and reliability
Microsoft provides enterprise governance tools, but administrators must design environments, DLP policies, identities, service accounts, machine security, logging, and lifecycle management.
Who should choose Microsoft Power Automate?
Choose Power Automate
Microsoft-first organizations and desktop RPA programs.
Choose another
Teams seeking simpler cross-SaaS pricing or self-hosting.
Test carefully
Unattended RPA, premium connectors, AI Builder, and high-volume flows.
Pros and cons
| Pros | Cons |
|---|---|
| Cloud and desktop automation in one family | Licensing requires careful interpretation |
| Strong Microsoft ecosystem alignment | Environment governance adds administration |
| Enterprise DLP and identity path | Not the simplest fit for small cross-SaaS teams |
Final verdict
Power Automate is the strongest choice in this cluster when Microsoft governance or desktop RPA is a real requirement, not merely a familiar brand.
Explore the automation library or use the Automation Tool Selector.
Methodology and research limits
ChoiceRidge checked official pricing and product documentation on August 12, 2026. No controlled reliability benchmark or numerical score is claimed.
Read our Methodology, Editorial Policy, and How We Make Money.
Frequently asked questions
Does Power Automate include desktop RPA?
Yes, but attended and unattended scenarios require different licensing.
What does Premium cost?
$15 per user per month paid yearly on the verified page.
Is it only for Microsoft apps?
No, but Microsoft ecosystem alignment is its clearest advantage.