UiPath vs Automation Anywhere vs Power Automate in 2026: Enterprise RPA Compared

Three vendors dominate the enterprise RPA shortlist in 2026: UiPath, Automation Anywhere, and Microsoft Power Automate. They overlap on the core capability of recording, scheduling, and managing software bots, but they diverge sharply on price model, AI roadmap, and which IT team typically owns the platform. This guide compares the three across pricing, architecture, AI features, governance, and total cost of ownership for a mid-market estate.

Numbers in this guide are pulled from the UiPath pricing page, Automation Anywhere pricing, and the Microsoft Power Automate plans page as of Q1 2026. Numbers from analyst writeups are flagged inline.

At-a-glance comparison

Pricing

UiPath publishes per-bot pricing in the Pro tier: roughly $135/bot/month for attended, $420/bot/month for unattended, with Orchestrator included. The Enterprise tier moves to bundled licensing and is custom-quoted; analyst firm AIMultiple reports list prices typically run 20-40% above actual deal prices on three-year commits.

Automation Anywhere's Cloud Starter Pack lands around $750/month and includes a small bot allowance. Each additional unattended bot is roughly $500/month and each attended bot roughly $125/month. Larger deployments typically start near $50,000/year for 5 unattended bots and scale up.

Power Automate is priced on Microsoft's familiar per-user per-process model. Attended desktop RPA is $15/user/month; the Power Automate Process plan is $150/month per process and includes unattended automation. Many Microsoft 365 E3 and E5 customers already have basic cloud flow capabilities included, which is why Power Automate often shows up as the default cheap option even when its RPA capabilities are less mature.

For a 50-bot estate, the rough 2026 envelope is:

• UiPath: $250K-$400K/year
• Automation Anywhere: $200K-$350K/year
• Power Automate: $90K-$200K/year (heavily dependent on existing M365 licensing)

Editor's Note: Across 4 client RPA refresh projects in 2025-26 (200, 350, 800, and 1,400 desktops), Power Automate landed cheapest only when the customer already held Microsoft 365 E5 licences for every bot operator; once we costed in net-new licences, UiPath came in within 8 percent on the 350-desktop estate. The genuinely cheaper option in two of those four reviews was reducing bot count rather than switching vendor: process re-design eliminated 22 of 60 bots in one finance shared-services case. Caveat: small sample, all UK and Ireland headquartered. — Rafal Fila, ShadowGen

Architecture

UiPath is the most modular of the three. Studio (developer IDE), Orchestrator (control plane), Robots (execution agents), Action Center (human-in-the-loop), and AI Center (model serving) are separately licensable components. Self-hosted, on-prem deployments are still common in financial services and government.

Automation Anywhere shifted to a cloud-native architecture in the A360 release; the Control Room runs in AWS-hosted Automation Anywhere Cloud, with bot runners deployed on customer-managed Windows VMs. On-prem Control Room deployments still exist but are increasingly the exception.

Power Automate runs on Azure inside Microsoft's tenancy. Cloud flows execute in Microsoft's environment; desktop flows run on a Windows machine with the Power Automate desktop client and are coordinated through machine groups. The architecture is least flexible of the three but also requires the least dedicated platform-team effort.

AI features

UiPath markets Autopilot as the agentic layer across Studio, Apps, and Test Manager. Document Understanding handles structured and semi-structured extraction; Communications Mining handles email and chat triage.

Automation Anywhere ships Automation Co-Pilot for in-app assist and a separate Document Automation product. The AI Agent Studio, launched in 2024, focuses on building agentic flows that combine RPA actions with LLM reasoning.

Power Automate slots into Copilot Studio and AI Builder. The AI advantage here is integration with Microsoft 365 Copilot and Dynamics, not the underlying model quality.

All three vendors are converging on the same agentic-RPA narrative; the practical differentiator in 2026 is which vendor's AI is wired into the rest of your stack.

Governance and observability

UiPath Orchestrator and Automation Anywhere Control Room both offer queue-level monitoring, asset management, role-based access, and audit logs. UiPath's Insights and Automation Hub add CoE-level reporting and idea pipelines. Automation Anywhere's CoE Manager covers a similar surface.

Power Automate governance lives in the Power Platform admin centre and Microsoft Purview. Data loss prevention policies, environment strategy, and managed environments are the standard controls; teams that already run a mature Microsoft 365 governance practice find this familiar.

Decision flow

flowchart TD
  A[Choosing RPA vendor] --> B{Microsoft 365 E3/E5<br/>already deployed?}
  B -- Yes --> C{Need dedicated<br/>RPA CoE features<br/>process mining,<br/>complex orchestration?}
  B -- No --> D{Cloud-first<br/>or on-prem priority?}
  C -- No --> E[Power Automate]
  C -- Yes --> F[UiPath]
  D -- Cloud-first --> G[Automation Anywhere]
  D -- Mixed / on-prem --> F
  G --> H{Heavy document<br/>automation workload?}
  H -- Yes --> G
  H -- No, light --> E

When to choose UiPath

Choose UiPath when a dedicated Centre of Excellence owns automation, when process mining and task mining are part of the discovery flow, when the estate mixes on-prem and cloud, and when the team values the depth of Studio and Orchestrator over per-seat economics. UiPath remains the deepest stack for organisations whose RPA practice is itself a product.

When to choose Automation Anywhere

Choose Automation Anywhere for cloud-first enterprises, especially those running heavy document-extraction workloads, those that prefer a single vendor for bot platform plus document AI, and those without an existing Microsoft 365 estate to anchor licensing. The Control Room's unified UI is well suited to a centralised IT team running 100 to 1,000 bots.

When to choose Power Automate

Choose Power Automate when the estate is already on Microsoft 365 and Dynamics, when "citizen developer" rollout matters, when most workflows are cloud-flow rather than desktop-RPA, and when the appetite for a separate automation platform team is low. The unit economics are unmatched at small scale.

Total cost of ownership

List price is rarely what an enterprise pays. Three cost lines drive the actual TCO across all three vendors and tend to be missed in initial business cases:

1. Bot infrastructure. Unattended bots run on Windows VMs that need to stay licensed, patched, and accessible to target applications. A 50-bot estate typically requires 30-60 dedicated VMs once you account for parallelism and dev/test environments. At ~$100/VM/month all-in, that is $36K-$72K/year on top of the bot licences.
2. Citizen developer support. Power Automate's per-user model only saves money if those users are productive. Successful Microsoft 365 rollouts we have seen budget 0.5-1 FTE of platform-team time per 100 active makers for office hours, governance, and template curation.
3. Process discovery. UiPath Process Mining and Automation Anywhere Process Discovery are usually charged separately. List prices for process mining add-ons typically run $50K-$150K/year. Skipping them often means automating the wrong processes.

A defensible 2026 three-year TCO model includes licences, bot infrastructure, platform team (1 FTE per 50 bots is a reasonable rule of thumb), training, and the discovery toolchain. Vendors quote line one; the other four lines decide the comparison.

Migration patterns

Three migration patterns are common in 2026. From Blue Prism to UiPath remains the largest single migration cohort because Blue Prism's installed base predates the cloud-first vendors and SS&C's stewardship has slowed feature velocity. The typical Blue Prism estate is 50-300 bots in a regulated industry, and the cutover usually combines a UiPath Orchestrator stand-up with a multi-quarter parallel run.

From UiPath or Automation Anywhere to Power Automate is the second-most common pattern, driven by Microsoft 365 E5 licensing economics on smaller estates (<100 bots). The migration usually drops 20-30% of bot count along the way because Power Automate's per-user model surfaces the bots that should not have existed.

From any RPA vendor to a "no RPA" stack of API integrations and Temporal-style durable workflows is the smallest but fastest-growing cohort, especially in fintech and SaaS where the underlying applications expose APIs.

What rarely works is forklift-replacing a 200-bot estate in a single project. The pattern that works is parallel-running for two quarters, migrating one process family at a time, and treating the cutover as the prompt to retire processes that should not have been bots in the first place.

Bottom line

The three vendors have converged in capability over the last two years, but they have not converged in price model or buying centre. UiPath sells to automation CoEs, Automation Anywhere sells to cloud-first IT, and Power Automate is bundled with the Microsoft estate. The question that ends most evaluations is which of the three already touches the team that will own the platform.