NotCheap MAKE EVERY CREDIT COUNT
Analyze Your Costs

UiPath vs Microsoft Power Automate vs Automation Anywhere: Real Agentic Automation Cost in 2026

Share this guide

Compare UiPath, Microsoft Power Automate and Automation Anywhere deployment cost by pricing your actual workload, not the vendor's headline number. The bottom line: Microsoft Power Automate is the only one of the three that publishes a clear licensing baseline: $15 per attended user, $150 per unattended Process bot, or $215 per Hosted Process bot per month, billed annually.

The catch is that the other two are harder to pin down. If you ask an enterprise RPA vendor what automation costs, the answer usually begins with an NDA and a three-week discovery call. UiPath advertises an entry-level Basic tier from $25/month with restricted capacity, but its production Standard and Enterprise platforms require custom sales quotes. Automation Anywhere is similarly quote-driven for commercial deployments.

My practical rule of thumb: start with the headcount and concurrent execution slots your workflow actually needs. Then layer in machine infrastructure, AI tokens or credits, and ongoing exception management. The license fee is rarely the whole story.

Published pricing and what it buys

US dollar list prices verified on 25 October 2026, before applicable taxes and negotiated enterprise discounts:

ProductPublished starting priceWhat to check before buying
Power Automate Premium$15/user/month, paid yearlyIndividual cloud and attended desktop automation; connector and request limits still apply
Power Automate Process$150/bot/month, paid yearlyUnattended desktop capacity on your machine, or separately allocated cloud-process capacity
Power Automate Hosted Process$215/bot/month, paid yearlyUnattended capacity with a Microsoft-hosted virtual machine
UiPath BasicFrom $25/monthLimited users, 2 robots, one tenant; hosted in UiPath's European region
UiPath Standard / EnterpriseContact salesSpecify users, robots, agent/document consumption, support and deployment region
Automation Anywhere commercialContact salesSpecify creator and runner capacity, orchestration, document processing and support

A quick note on UiPath Basic: the European hosting region doesn't mean only European businesses can buy it. What to keep in mind is the strict two-robot cap, which makes Basic an entry sandbox rather than a home for mission-critical enterprise workloads. Check its operational limits against your production SLAs before you get attached to the price.

When you request quotes from UiPath or Automation Anywhere, ask them to price the exact same workload and user tier. A proposal that bundles dozens of hours of third-party systems integration can't be compared against pure software licensing, and you'll end up comparing apples to a whole fruit basket. We do not assign an invented annual minimum to either platform.

Three processes do not automatically require three bots

One of the most common budget mistakes in RPA is assuming every distinct workflow needs its own dedicated unattended bot license.

Picture three typical back-office jobs: an automated bank import running at 02:00, a general ledger reconciliation at 03:00, and a supplier catalogue sync at 05:00. Because these desktop scripts run one after another in an off-peak window, a single unattended bot license handles all three with ease. If two desktop tasks must run concurrently at 09:00, though, you need two parallel bot licenses, even if they run the exact same script.

Execution concurrency drives desktop robot licensing. A Power Automate Process license allocated to a cloud flow also follows different allocation rules than desktop execution. So map your schedules, virtual desktop sessions, and API cloud flows separately before committing budget. And leave a generous buffer for retries and slow network queries. A schedule packed to the minute will break at the first upstream timeout, usually at 3 a.m.

A reproducible five-person deployment budget

To keep the numbers realistic, take an operations team of five analysts who need attended desktop automation, supported by three nightly desktop workflows sharing a single unattended robot. The tasks process structured CSV extracts and SQL tables sequentially without calling AI models.

ConfigurationMonthly equivalentTwelve-month software charge
Five Premium users5 × $15 = $75$900
One Process bot$150$1,800
Five users plus customer-managed bot$225$2,700
Five users plus one Hosted Process bot$75 + $215 = $290$3,480

These list prices are monthly equivalents billed as annual upfront commitments, not month-to-month subscriptions. The $225 customer-managed configuration also means your team provisions, patches, and manages a dedicated host machine, and those infrastructure and admin costs aren't in the license fee. Microsoft's Hosted Process tier absorbs VM hosting and OS management, though solution maintenance is still on you.

If growth demands a second concurrent unattended execution slot, the customer-managed licensing cost steps up from $225 to $375/month equivalent. In real-world production, peak concurrency drives the licensing bill far more than the number of workflows in your repository.

Where AI Builder and Copilot Credits enter the bill

Adding intelligent document extraction or conversational agents brings in usage-based capacity meters. Microsoft distinguishes AI Builder credits from Copilot Credits. They are different meters: one million of one currency must not be presented as one million of the other.

Microsoft's licensing framework has gone through a couple of structured shifts:

  • Since 1 November 2025, new AI Builder customers must acquire Copilot Credits; legacy AI Builder capacity add-ons are available to existing customers through the applicable renewal or true-up rules.
  • A further change takes effect on 1 November 2026: new or renewed eligible Power Platform and Dynamics 365 licenses no longer receive seeded AI Builder credits. Eligible contracts purchased or renewed before that date retain their seeded allocation through the applicable contract term.

For optical character recognition and document parsing, pin down the specific processing action, monthly page count, per-transaction credit consumption, and any existing tenant capacity before buying add-on packs. Please don't tack an arbitrary $500 monthly AI surcharge onto every automation budget. Our structured data scenario processes plain CSV and database records without invoking cognitive models, so its AI consumption line is $0. If your pipeline routes scans through generative models, budget that consumption as its own line item.

Pay-as-you-go uses different run meters

For sporadic or highly seasonal automations, Microsoft offers Azure subscription billing. Microsoft's documented preview meters distinguish $0.60 for a premium cloud or attended run from $3.00 for an unattended run. This is not a flat desktop transaction rate.

At this unattended rate:

  • 30 unattended runs cost 30 × $3 = $90 per month.
  • 100 unattended runs cost 100 × $3 = $300 per month.
  • Break-even against a dedicated $150/month Process bot occurs at exactly 50 unattended runs.

Treat that break-even as a financial yardstick, not advice to double-license environments. Microsoft's documentation details how existing Process capacity interacts with pay-as-you-go meters, so check your tenant allocation before flipping any billing switches.

Include the work after launch

Software licensing is only the baseline expense in production RPA. For the $225 customer-managed deployment, break-even against internal labor valued at an illustrative $45/hour requires saving $225 ÷ $45 = 5 hours of manual work per month.

In practice, that figure is an incomplete floor. Add an illustrative $60/month cloud VM hosting budget and 4 hours of monthly engineer time to resolve broken UI selectors and system exceptions, and the realistic monthly operating cost becomes $225 + $60 + 4 × $45 = $465. At that level, the pipeline must deliver 10.33 hours of manual labor savings each month just to break even on operating expenses, before paying off initial development costs.

My advice: record execution times, failure rates, and maintenance tickets during a pilot. Saving ten hours of manual data entry while introducing twelve hours of weekly exception handling is an expensive way to automate a process.

Which option deserves a pilot?

Power Automate is the most direct starting point when your stack centers on Microsoft 365 and Azure, and when published per-seat and per-bot pricing fits your workflow volume. UiPath and Automation Anywhere justify formal enterprise sales evaluations when your environment demands deep computer vision for legacy Citrix sessions, complex multi-tenant orchestration, or specialized regulatory compliance. Whichever way you lean, compare total completed work and ongoing maintenance overhead rather than choosing on a vendor's headline rate.

If your workflows are mostly API-driven rather than tied to legacy desktop user interfaces, review Zapier, Make and n8n alongside traditional RPA platforms. Desktop bots and API integrations solve fundamentally different problems, and picking the right category first can save you real money.

Official sources

PASS IT ON

Useful for your team?

Share this guide with a colleague.