Last updated: October 13, 2026
By ZapAI Team
TL;DR: Power Automate vs UiPath comes down to your stack and your scale. Power Automate is the cheaper, simpler pick for Microsoft 365 and Dynamics shops, with attended robotic process automation included in the $15 Premium license. UiPath is the deeper RPA platform for large unattended estates, heavy Citrix work, and self-hosted orchestration, but most of its pricing is quote-only. AI agents now sit on top of both.
Choose Power Automate if you run on Microsoft 365 and want low-cost attended and unattended bots. Choose UiPath if you need enterprise-scale unattended RPA, self-hosted orchestration, or deep Citrix and legacy app automation.
Somebody in finance is still copying invoice numbers from a green-screen system into an ERP. Every day. You already know a bot should do it. The open question is which bot.
For most US mid-market teams, the shortlist is two names. Microsoft Power Automate, which you may already own a piece of through Microsoft 365. And UiPath, the company that made RPA a category. Both changed fast once AI agents started clicking buttons on their own.
Here’s how they compare in October 2026, with current prices, scenario fit, migration, and agents. Bias disclosed early. We’re a Microsoft consulting firm. We’ll still tell you when UiPath is the better call, because sometimes it plainly is.
What Are Power Automate and UiPath in 2026?
Power Automate is Microsoft’s automation service, combining API-based cloud flows with desktop flows for RPA. UiPath is a dedicated automation platform built around robots, an orchestrator, and now agents coordinated by a product called Maestro.
Microsoft’s side has two halves. Cloud flows connect apps through APIs, like routing a SharePoint approval to Teams. Desktop flows are the RPA side, recording and replaying clicks on Windows. Per Microsoft’s desktop flow requirements, the desktop app ships with 400+ prebuilt actions and supports SAP, mainframe and AS/400 terminals, Java apps, and Citrix. Anyone with a free Microsoft account can build and run desktop flows locally. Triggering them from the cloud, sharing them, or running them unattended needs a paid license.
UiPath is broader and more specialized at the same time. Developers build automations in Studio, either the desktop app, the browser-based Studio Web, or inside VS Code, then robots run the work on attended or unattended machines while Orchestrator schedules, monitors, and governs all of it. On top sits Maestro, which models whole processes in BPMN and hands steps to agents, robots, or people. Integration Service and IXP add API connectors and document extraction, all vendor-neutral.
Different philosophies. Microsoft treats RPA as one feature of the Power Platform. UiPath treats it as the foundation.
How Do Power Automate and UiPath Compare Side by Side?
Power Automate wins on price, Microsoft integration, and ease of starting, while UiPath wins on depth of UI automation, orchestration control, deployment choices, and tooling for large bot teams that have outgrown a single admin.
Short version first. Details below.
| Factor | Power Automate | UiPath |
|---|---|---|
| Core building tool | Power Automate for desktop plus the cloud flow designer | Studio Desktop, Studio Web, or VS Code |
| Orchestration | Cloud only, through the Power Automate portal, machine groups, and work queues | Orchestrator in Automation Cloud or self-hosted, plus Maestro for end-to-end processes |
| Pricing | Published for every plan | Published only for Community and Basic |
| Microsoft 365, Dynamics, Dataverse | Native, same tenant and security model | Supported through connectors and activities |
| Citrix and virtual desktops | Supported with an agent on the remote machine | Supported with Remote Runtime on the Citrix servers, mature tooling |
| Self-hosted option | No, the control plane is Microsoft cloud | Yes, on Standard and Enterprise plans |
| AI agents | Copilot Studio agents, including computer use | UiPath Agents, orchestrated by Maestro |
On analyst rankings, be careful with old screenshots. UiPath was named a Leader in the 2025 Gartner Magic Quadrant for RPA for the seventh straight year, per its own announcement. Microsoft was a Leader in earlier editions, but we couldn’t confirm its latest placement publicly. If procurement cares, get the current report, not a vendor slide.
How Much Do Power Automate and UiPath Cost?
Power Automate publishes its prices. Premium is $15 per user per month, Process is $150 per bot per month, and Hosted Process is $215. UiPath publishes only its free Community plan and a Basic plan starting at $25 per month.
These come from the Power Automate pricing page and the UiPath pricing page, both checked October 13, 2026. Microsoft prices are US list, billed yearly.
| Plan | Published price | What you get |
|---|---|---|
| Power Automate Premium | $15 per user per month | Cloud flows, attended desktop flows, process and task mining with 50 MB storage |
| Power Automate Process | $150 per bot per month | One unattended bot on your own machine, running one desktop flow at a time |
| Power Automate Hosted Process | $215 per bot per month | Same as Process, plus a Microsoft-hosted Azure virtual machine |
| Process Mining add-on | $5,000 per tenant per month | 100 GB of process data, Premium required |
| UiPath Community | Free | For learning and small use, community support |
| UiPath Basic | From $25 per month | Limited-scale users and robots, European hosting. UiPath says an updated plan is coming soon. |
| UiPath Standard and Enterprise | Contact sales | Agents, document extraction, governance, no scale limits, regional or on-premises hosting |
Quick math. Ten unattended bots on Process cost $18,000 a year, before the Windows machines you run them on. Hosted Process makes it $25,800 with nothing to patch. Twenty attended users on Premium add $3,600.
No UiPath equivalent here. We looked. UiPath doesn’t publish Standard or Enterprise prices, and third-party estimates online disagree by thousands of dollars per robot. Get a written quote with every robot, user, and add-on itemized. Our Power Platform licensing breakdown covers the Microsoft side in more depth, including Dataverse capacity and Copilot Credits.
Which Handles Legacy Desktop, Citrix, and Mainframe Apps Better?
UiPath has the edge for heavy Citrix and complex legacy UI work. Power Automate handles mainframe terminals, SAP, Java, and Citrix well enough for most mid-market workloads.
Same basic trick, different depth. Both tools reach inside a Citrix session by installing a component on the remote side. Power Automate uses a lightweight agent on the virtual desktop. UiPath installs Remote Runtime on the Citrix Virtual Apps servers, which talks over the ICA virtual channel and gives Studio native selectors for Citrix app elements, according to UiPath’s Citrix automation docs. Without those components, both fall back to image recognition and OCR. Fragile. Slow. Breaks whenever someone changes screen resolution.
Where does UiPath pull ahead? Volume and variety. A shared services center automating 40 screens across an old claims system and three Citrix-published apps will appreciate UiPath’s selector and debugging tools. A 300-person distributor scraping one AS/400 screen into Business Central won’t feel the difference.
One honest caveat. Power Automate’s low barrier to entry makes it easy to ship a recorded, never-cleaned-up flow that dies on the first UI update. That’s build discipline, not the platform.
Which Scales and Governs Better for Unattended Bots?
UiPath, once you pass a few dozen unattended bots or need on-premises control. Power Automate scales fine for small and mid-size estates, with real limits worth knowing before you commit.
Hosted machine groups are genuinely handy. You buy Hosted Process capacity, Microsoft spins up Windows 11 VMs as your queue grows, and then it scales them back down when the queue drains, so you never patch, image, or babysit a bot server yourself. But read the fine print in the hosted machine group docs.
- Ten hosted machine groups per environment, max.
- Each group tops out at 50 bots.
- Idle for three hours? The next run waits 10 minutes or more while a fresh bot is provisioned. That’s fine for nightly batches and painful for anything a customer is waiting on.
- A group with no committed bots that sits unused for 28 days gets deleted automatically, and you rebuild it plus its connections.
- Remote desktop into hosted bots isn’t supported, so debugging happens through logs and run history.
None of that is a deal breaker. UiPath just gives you more knobs. Self-hosted orchestration for regulated workloads, robot infrastructure controls and CI/CD on Enterprise, and a governance model large Centers of Excellence already know.
Attended automation flips the picture. Two hundred employees each running a small bot on their own laptop? Premium at $15 a head is very hard to beat.
How Do AI Agents Change the Power Automate vs UiPath Decision?
Agents don’t replace RPA yet, but they shrink the work that needs a scripted bot. Both vendors now offer AI agents that read screens and decide what to click, with traditional bots handling the predictable steps.
On Microsoft’s side, Copilot Studio’s computer use tool lets an agent operate websites and Windows apps from plain-language instructions, on a machine you register in Power Automate. OpenAI’s CUA model and Anthropic’s Claude Sonnet 4.5 are generally available for it. Billing is per step, at 5 Copilot Credits per step on standard models and 15 on premium ones. A four-step timesheet entry costs 20 credits. Cheap per run. Less cheap at volume.
UiPath hasn’t sat still either, and its pace through the second half of 2026 has been hard to keep up with even for people who track release notes for a living, which is partly why older comparison articles already read as out of date. Its September 2026 Agents release notes list Agents in Flow reaching general availability on September 15, building agents with coding agents going GA a day later, and an Autopilot Agent for building and debugging agents in preview. Maestro is the glue, so one BPMN process can hand a step to an agent, the next to a robot, and an exception to a human.
So which is cheaper for messy, judgment-heavy work? Nobody knows yet at scale, because per-step pricing is easy to estimate for one run and surprisingly hard to forecast across 50,000 runs a month. Our working rule is boring on purpose. Deterministic, high-volume steps stay in RPA, steps that need judgment go to an agent, and exceptions go to a person. For more on where agents belong, see our AI agent development work and our comparison of Copilot Studio vs custom agents.
Which Should You Choose? A Decision Table by Scenario
Match the platform to your stack, your bot count, and your hosting rules. Most Microsoft-centric mid-market teams land on Power Automate. Large, multi-ERP, or regulated estates usually belong on UiPath.
| Your situation | Better fit | Why |
|---|---|---|
| Microsoft 365, Dynamics 365, or Dataverse at the core | Power Automate | Same identity, security, and admin center. No second vendor. |
| Under 25 unattended bots, US cloud hosting is fine | Power Automate | Published prices and hosted bots with no VMs to manage |
| Dozens of Citrix-published apps or complex legacy screens | UiPath | Deeper selector tooling and native Citrix support |
| Orchestration must run on premises | UiPath | Self-hosted options on Standard and Enterprise. Power Automate’s control plane is cloud only. |
| Established RPA Center of Excellence with 100+ bots | UiPath | Mature governance, CI/CD, and infrastructure controls |
| Mixed SAP, Oracle, and Salesforce with little Microsoft | UiPath | Vendor-neutral platform, no Microsoft licensing to justify |
| Already on UiPath and happy, adding Microsoft 365 | Keep UiPath | Use Power Automate cloud flows for Microsoft-side approvals and notifications only |
That last row matters more than it looks. Nothing stops you from running both. Picking one doesn’t have to mean banning the other.
What Does Migrating Between Power Automate and UiPath Involve?
Plan to rebuild, not convert. Bots move logic, credentials, queues, and schedules, and each piece maps differently. Budget the effort per bot and run old and new side by side before cutover.
Most migrations we hear about run from UiPath to Power Automate, usually when a renewal lands next to a Microsoft enterprise agreement. Roughly in order.
- Inventory every bot. Owner, run frequency, apps touched, and what breaks if it stops.
- Rank by value and fragility. Simple, high-volume bots on modern apps first. Citrix monsters last.
- Replace screens with APIs where you can. A bot typing into Dynamics 365 should become a cloud flow with a connector.
- Rebuild the rest as desktop flows. Map Orchestrator queues to Power Automate work queues and stored assets to Azure Key Vault credentials.
- Run in parallel for two to four weeks. Compare outputs before switching off the old bot.
Step three is the hidden win. It’s a rare chance to delete UI automation that should have been an integration all along. Our Power Automate consulting team treats that review as the first deliverable, and our list of real Power Automate use cases shows where cloud flows usually replace a bot outright.
Wrapping Up
Both platforms do RPA well in 2026. The difference is fit. Power Automate is the practical default for Microsoft-centric teams that want published prices, cheap attended bots, and hosted unattended capacity. UiPath earns its premium with large unattended estates, hard Citrix and legacy work, self-hosted orchestration, and mature agentic orchestration through Maestro.
ZapAI is a Microsoft Dynamics 365, Power Platform, Fabric, and AI consulting firm in Irving, Texas, and we build automation for US businesses. If you’re weighing a UiPath renewal against Power Automate, or scoping your first bots, our RPA team can inventory your candidate processes and model both license options side by side before you sign anything.
Questions Teams Ask Before Picking an RPA Tool
Is Power Automate Desktop actually free?
Partly. Anyone with a Windows 10 or 11 PC and a free Microsoft account can build and run desktop flows locally, by hand. Triggering them from cloud flows, sharing them, storing them centrally, or running them unattended takes a paid license, starting with Premium at $15 per user per month.
Why won’t UiPath just publish its prices?
Its Standard and Enterprise plans are quote-based, so only Community (free) and Basic (from $25 per month) show prices. Expect pricing to depend on robot types, user types, add-ons, and term length. Ask for every line itemized.
Can AI agents replace RPA bots entirely?
Not for high-volume, rule-based work today. Agents bill per step and reason through each run, which makes them slower and harder to forecast than a scripted bot repeating the same 12 clicks. They shine on the messy edges, like an odd invoice layout or a changed screen. Expect a mix, with RPA as the hands, agents as the judgment, and document processing in between.
Power Automate vs UiPath for a 500-person company, does it matter much?
Usually the stack decides it. On Microsoft 365 with Dynamics 365 or Business Central, Power Automate is the sensible starting point. On a vendor mix with lots of Citrix, run a two-week proof of concept on your nastiest screen in both tools and let the results talk.
Do hosted bots in Power Automate need our own VMs?
Nope. Hosted Process at $215 per bot per month includes a Microsoft-hosted Azure VM, and you can supply a custom Windows image if your bots need extra software installed.
Can we run Power Automate and UiPath together?
You can, and it’s a reasonable setup. A sensible split is UiPath for back-office unattended bots and Power Automate cloud flows for Microsoft 365 approvals. The cost is two skill sets, two governance models, and two renewals, so decide which tool owns which kind of work.