UiPath and Power Automate compared on capabilities, licensing, AI agents and governance, refreshed from both vendors' documentation in November 2026, with a decision flow and the cases where a workflow tool or API integration beats both.
UiPath and Microsoft Power Automate are two of the most widely used platforms for robotic process automation (RPA): software robots that work through user interfaces and connected apps the way a person would. Both automate data entry, report runs, invoice handling and the copy and paste work that slows teams down, and both now add AI agents on top. They come from different starting points, though, and that still decides where each one fits.
This guide compares the two on capabilities, licensing, agents and governance, with licence details and agent features refreshed from each vendor’s own documentation on 13 Nov 2026. It ends with a decision flow and the cases where neither is the right tool. For the wider picture of RPA, workflow tools and AI agents side by side, see our business process automation guide.
Key takeaways
- Choose Power Automate when your organisation runs on Microsoft 365 and most processes connect cloud apps, with some desktop automation.
- Choose UiPath for large programmes of desktop and legacy automation, with many unattended robots and a central team to run them.
- Both now license AI separately from robots: Microsoft through Copilot Studio credits, UiPath through Platform Units or Agent Units per run or model call.
- Power Automate list prices are published (USD 15 per user and USD 150 or 215 per bot a month, paid yearly, as of 13 Nov 2026); UiPath prices are quoted.
- Choose neither when the systems involved have good APIs: a workflow tool or direct integration is faster, cheaper to run and more reliable.
The short answer
- Choose Power Automate if you already use Microsoft 365, most processes involve Microsoft and common cloud apps, and you want business users to build simpler automations under IT governance.
- Choose UiPath if much of the work is in desktop, legacy or virtualised applications, you plan many unattended robots, or you want a dedicated automation platform that is not tied to one vendor’s stack.
- Choose neither for processes between systems with good APIs. A workflow tool or a direct integration does the job with less to maintain.
Side by side
| Aspect | UiPath | Power Automate |
|---|---|---|
| Origin | A dedicated automation company that started in RPA | Part of Microsoft Power Platform, started with cloud workflows |
| Main strength | Desktop and UI automation at scale, orchestration, central automation programmes | Microsoft 365, Dynamics 365 and Azure integration, with a large library of connectors |
| Building automations | Studio for developers; Studio Web, where agents are built | Browser designer for cloud flows, Power Automate for desktop for desktop flows |
| Running and managing | Orchestrator for robots, queues, schedules and logs, in the cloud or self-hosted | Power Platform admin centre, environments and data policies, plus work queues and machine management |
| AI agents | Agents built in Studio Web; Maestro for workflows that combine agents, robots and people | Agent flows and agents in Copilot Studio, including computer use for UI tasks |
| Licensing | Unified Pricing (Platform Units) or the older Flex plan (several unit types), with user licences | User licences (Premium) and capacity licences (Process, Hosted Process), plus Copilot Studio credits for agents |
| List prices | Quoted by UiPath | Published: from USD 15 per user a month, paid yearly |
Source: UiPath documentation; Microsoft Learn and the Power Automate pricing page; checked 13 Nov 2026
What UiPath is
UiPath is a platform built for automation. Developers design automations in UiPath Studio, and robots run them either attended, alongside a person on their own computer, or unattended, on a server or virtual machine. Orchestrator schedules and monitors robots, manages work queues and credentials, and keeps logs. It runs as a cloud service or on your own infrastructure through Automation Suite, its on-premises platform, which matters to some regulated organisations.
Around that core, UiPath adds document processing, process and task mining, testing, and agents. According to its agent licensing documentation, agents are built and tested in Studio Web and run from Orchestrator, from an API or webhook, or in a conversation on a published channel. Maestro runs workflows that combine agents with automations and steps such as document extraction, per the Maestro licensing page.
What Power Automate is
Power Automate is Microsoft’s automation service, part of Power Platform alongside Power Apps and Power BI. It has two main kinds of automation:
- Cloud flows connect apps and services through connectors. A flow might save email attachments to SharePoint, post an approval in Teams and update a Dataverse table.
- Desktop flows are the RPA part. Built in Power Automate for desktop, they automate legacy applications such as terminal emulators, modern web and desktop apps, Excel files and folders, working through UI elements, images or screen coordinates (Microsoft Learn, updated 23 Aug 2026).
Cloud flows can trigger desktop flows, so one process can combine API connectors with UI automation. AI Builder adds document processing and other models, paid for in AI Builder credits.
Licensing in November 2026
Both vendors revise packaging often. The details below are from their documentation on 13 Nov 2026; confirm current terms before you buy.
Power Automate
Microsoft splits licences into user licences and capacity licences (types of Power Automate licences, updated 22 Sep 2026):
- Free: work or school accounts can create and run cloud flows with standard connectors (without sharing) and author and run desktop flows locally in attended mode.
- Premium (per user): unlimited cloud flows within action limits, standard, premium and custom connectors, one attended bot, process mining, 5,000 AI Builder credits a month and a daily limit of 40,000 actions per user.
- Process (per bot or flow): allocated to a machine it becomes one unattended bot that runs one desktop flow at a time; allocated to a cloud flow it gives premium connectors and up to 250,000 actions a day, whatever licence the users have.
- Hosted Process: one hosted bot on a Microsoft-hosted machine, so you do not manage the virtual machines yourself.
Capacity licences do not replace user licences: the documentation notes that a machine must still be registered by a Premium user, and some monitoring pages show only to Premium users. Pay-as-you-go billing is also available.
| Plan | Price | Unit |
|---|---|---|
| Power Automate Premium | USD 15.00 | Per user a month |
| Power Automate Process | USD 150.00 | Per bot a month |
| Power Automate Hosted Process | USD 215.00 | Per bot a month |
| Process Mining add-on (with Premium) | USD 5,000.00 | Per tenant a month |
Source: Microsoft Power Automate pricing page, checked 13 Nov 2026; Microsoft notes prices are for marketing purposes and may differ at checkout
Source: Power Automate pricing. Copilot Studio, where Microsoft’s agents run, is sold separately in Copilot Credits.
UiPath
UiPath does not publish list prices; plans are quoted. Its commercial licensing documentation describes two plans:
- Unified Pricing uses one consumption unit, the Platform Unit, which can be reallocated as needs change, with user licences such as Express, Basic, Plus, Pro and App Test. A free Community plan has a fixed set of licences and a monthly credit allowance.
- Flex, the other plan, uses separate consumables (AI Units, Apps Units, Robot Units, API Calls and Agent Units) with its own user licences, such as Attended, Citizen Developer and Automation Developer. Customers can move from Flex to Unified Pricing.
When you compare costs, count everything: licences, the machines that run unattended robots, AI consumption, development time and the cost of fixing automations when screens change. The licence is often not the largest part.
Want a second opinion on your plans?
Tell us what you are working on. A specialist will look at it and reply with practical next steps.
Get in touchAI agents on each platform
Both vendors now sell agents that decide which steps to take, alongside robots that follow fixed steps. The design questions are the same on both: what the agent may do alone, what needs approval and how every action is logged. Our explainer on the difference between a chatbot, an AI agent and an RPA bot covers where each one fits.
Microsoft: agent flows and computer use in Copilot Studio
Microsoft’s agent features sit in Copilot Studio rather than in Power Automate licences. Agent flows (documentation updated 3 Nov 2026) are deterministic flows with AI actions, human-in-the-loop approvals and connectors, and every action they run consumes Copilot Studio capacity. An existing Power Automate cloud flow can be converted into an agent flow so that it bills against Copilot Studio instead of Power Automate; the conversion is one-way.
For screen work, computer use (updated 20 Oct 2026) lets an agent operate websites and Windows desktop apps from natural-language instructions, adapting when buttons or screens change. Microsoft bills it per step: 5 Copilot Credits a step with a standard model and 15 with a premium one, so a four-step task uses 20 or 60 credits. Microsoft recommends dedicated machines, least-privilege accounts and allow lists of sites and apps.
UiPath: agents, Maestro and unit-based billing
UiPath agents run on the same platform as its robots. Production runs consume Platform Units on Unified Pricing or Agent Units on Flex; for UiPath-hosted models each LLM call is charged by model tier (for example 0.2 Platform Units per call for a standard-tier model), while customer-managed models are charged once per run. Building and testing in Studio Web does not consume units. Maestro includes a monthly allowance of workflow runs that depends on the platform tier (50,000 on the Enterprise platform under Unified Pricing), with overage at 0.05 Platform Units a run, and bills agents and document extraction inside a workflow separately.
Capabilities compared
Desktop and user interface automation
Both automate Windows desktop applications, browsers, Excel and older systems such as terminal apps. UiPath has the longer track record here, with detailed controls for selecting screen elements in difficult applications. Power Automate for desktop handles most common scenarios. For very complex or unstable interfaces, test both on your own applications, because the gap depends on the specific software.
Integrations and APIs
Power Automate is strong here: its connector library links Microsoft 365, Dynamics 365 and many SaaS products without code, and custom connectors wrap your own APIs. UiPath also calls APIs and offers integration features, but its centre of gravity remains automation across applications.
Document processing
Both extract fields from invoices, receipts, forms and contracts, with confidence scores and human review for uncertain results. Accuracy depends heavily on layout and scan quality, so compare them on your own documents. Our guide to intelligent document processing covers the approach, and our document automation service works with either platform.
Orchestration, monitoring and governance
UiPath Orchestrator is a mature control centre for many unattended robots, with queues, retries, credential storage, schedules and detailed logs. Power Platform governance works through environments, data loss prevention policies and the admin centre, which suits IT teams that already manage Microsoft 365. At large scale with many unattended robots, UiPath’s dedicated tools are often an advantage; where many business users build small flows, Microsoft’s environment and policy model fits naturally.
Which one should you choose?
UiPath, Power Automate or neither?
Question 1: Do the systems in the process have reliable APIs or connectors for every step?
Question 2: Is the process mostly moving data between cloud apps, with approvals and notifications?
- YesUse a workflow tool or Power Automate cloud flows; no RPA needed
- NoBuild a direct integration, with a workflow tool around it if people need to approve steps
Question 3: Is your organisation standardised on Microsoft 365, Teams and Dynamics 365?
Question 4: Will you run many unattended robots on complex desktop or virtualised applications?
- YesTest UiPath against Power Automate on your hardest application before choosing
- NoPower Automate, with desktop flows for the steps without APIs
Question 5: Do you plan a central automation programme with a team to run it?
- YesUiPath
- NoTest both on one real process; consider a workflow tool for the API steps
When UiPath fits better
- You plan an automation programme with many processes and a central team or centre of excellence to run it.
- Much of the work is in desktop, legacy or virtualised applications with no usable API.
- You need many unattended robots with queues, retries and detailed audit logs.
- Your systems come from many vendors and Microsoft is not your main platform.
- You need a self-hosted option for regulatory or data residency reasons.
When Power Automate fits better
- You already use Microsoft 365, Teams, SharePoint, Dynamics 365 or Azure.
- Most processes connect cloud apps that have connectors, with only some UI automation.
- You want business users to build and own simple automations under IT governance.
- You want published per-user and per-bot prices and a small starting cost.
- Approvals and notifications in Teams and Outlook are a big part of the process.
When neither fits
RPA imitates a person using a screen. That is useful when there is no other way in, but robots break when a screen changes, run slower than direct integrations and need monitoring. If the systems involved offer reliable APIs, a workflow automation tool or a direct integration is usually the better choice:
- More reliable: APIs are designed for machines and change less often than screens.
- Faster: data moves in one call rather than at the speed of clicking through forms.
- Cheaper to run: no robot licences or virtual machines per process.
- Easier to secure and audit: scoped API keys and server logs rather than robot accounts that sign in like users.
For API-first processes, workflow tools such as n8n, Zapier and Make are often the better fit, and n8n can be self-hosted on your own infrastructure or in a private cloud (n8n documentation). Our comparison of n8n, Zapier, Make and Power Automate covers how to choose between them. And where the work needs judgement rather than fixed steps, such as reading free-text emails and deciding what to do, an AI agent with narrow permissions may be the right tool; our guide to AI agents for business explains when.
In practice the best design is often a mix: APIs wherever they exist, RPA only for the steps in systems with no other interface, and a workflow layer that ties them together.
Can you use both?
Yes, and some organisations do: Power Automate for Microsoft-centred workflows and approvals that business users build, and UiPath for heavy back-office automation run by a central team. The cost is two platforms to license, govern and support. For most small and mid-sized businesses, one platform plus API integrations is simpler.
How we help
Our RPA services cover process assessment and bot development with tools such as UiPath and Power Automate, and we will say so when an API integration is the sturdier choice. Our workflow automation team connects systems directly through their APIs, and our AI agent development team builds agents with approval points and logs for the steps that need judgement.
Choosing between UiPath and Power Automate?
- Our RPA consultants map your processes, test the hardest one on both platforms and show you the full cost of each option, including when an API integration beats both.
Get new guides by email
Articles and guides from our team, and company news. Unsubscribe at any time.
About AcmaSoft
AcmaSoft designs and builds websites, mobile apps and custom software, and runs SEO and digital marketing for its clients.
- Years of experience
- 17+
- Clients served
- 650+
- Projects delivered
- 2,000+
- Products shipped
- 300+


