Microsoft Power Automate

What it is

Microsoft Power Automate is the automation layer of the Power Platform, and it does two different jobs under one name. Cloud flows are API automations — “when a file lands in this SharePoint library, extract the fields, update Dataverse, post to Teams” — built from more than 1,400 connectors. Desktop flows are RPA: a bot that drives the mouse and keyboard on a Windows machine to operate software that has no API. Process and task mining sit on top for finding what to automate. In category terms it is Zapier and UiPath sold as one licence, inside the tenant’s identity and data-loss-prevention policies.

The 2026 release wave 1 (April to September) pulled it toward agents. Cloud flows can now call Copilot Studio agents as actions, agents can trigger cloud and desktop flows, desktop flows gained AI self-healing that recovers when a button moves (public preview from May, single UI elements only, not in sovereign clouds), and object-centric process mining reached general availability. One distinction trips up buyers: a classic cloud flow runs on Power Automate licences, while an agent flow built in Copilot Studio is billed in Copilot Credits — 13 credits per 100 actions on Microsoft’s current rate card.

Why ops teams end up here

Because the licence is often already paid for. Most Microsoft 365 business and enterprise plans include seeded Power Automate rights, and the free licence for any work account lets people build unshared cloud flows on standard connectors — SharePoint, Outlook, Teams, OneDrive, Forms, Approvals. That covers the approvals and notifications that make up most of a legal-ops or recruiting coordinator’s automation backlog: a contract-request form that routes to the right counsel, an offer approval chain, a weekly pipeline digest. RevOps teams on Dynamics 365 Sales also get Power Automate use inside the Dynamics app context, with a 40,000 daily request allowance. The point where people stop and ask is the first premium connector — Salesforce, HTTP, a custom connector — or the first legacy app that needs a bot.

Pricing reality

List prices, annual billing, checked on Microsoft’s pricing page today:

• Free / Microsoft 365 seeded — cloud flows on standard connectors only; Microsoft 365 licences carry 6,000 requests per user per day.
• Premium — $15/user/month. Premium and custom connectors, one attended RPA bot, process mining with 50 MB storage, 40,000 requests per user per day.
• Process — $150/month per licence. Assign it to a machine and it becomes one unattended bot running one desktop flow at a time; assign it to a cloud flow and that flow gets premium connectors for every user plus 250,000 requests a day. It replaced the legacy $100 per-flow plan, which Microsoft now says to replace rather than renew.
• Hosted Process — $215/month: the same plus a Microsoft-hosted virtual machine.
• Process Mining add-on — $5,000/tenant/month, 100 GB.

What teams actually pay is shaped by who needs Premium. The common pattern is a small maker group on Premium, everyone else on seeded rights, and Process licences on the shared flows. A worked band: 20 makers on Premium plus 3 unattended bots is 20 × $15 × 12 + 3 × $150 × 12 = $9,000 a year; move the bots to hosted VMs and it becomes $11,340. The comparable UiPath contract has a Vendr median of $45,338 a year. The AI line is moving: the AI Builder credits seeded with Premium and Process (5,000 a month) and AI Builder add-on renewals end on 1 November 2026, after which document processing and prompts draw Copilot Credits. Budget that as a new line.

Best for

An IT-adjacent ops lead — legal operations, recruiting operations, finance or RevOps in a Dynamics shop — at a Microsoft 365 organisation of 200-10,000 people automating approvals, document intake and Teams or SharePoint notifications, plus a handful of desktop bots against legacy systems such as an old HRIS or a court e-filing portal. It wins where the security review is the bottleneck: flows inherit Entra identity, DLP policies and the Power Platform admin center that IT already runs.

Not for

A Google Workspace or Slack-first company, a startup whose stack is HubSpot, Notion and twenty SaaS APIs, or a GTM engineering team building multi-step LLM agents. The designer is slower than Zapier’s for simple jobs, error handling is verbose, and for AI-heavy workflows on non-Microsoft systems n8n does more per dollar.

Versus the alternatives

• Zapier — the market-share leader in no-code automation, from $19.99/month. Pick it when builders are non-technical, the apps are SaaS rather than Microsoft, and nobody needs RPA.
• UiPath — the RPA share leader. Pick it when unattended bots are the core of the programme, you run dozens of them across SAP, mainframe and Citrix, and you need orchestration and document understanding Power Automate’s bots don’t match.
• n8n — the fastest-growing entrant, valued at $5.2B in May 2026. Pick it when you have engineers, every system has an API, and you want model-agnostic agent workflows with self-hosting.
• Make and Workato — Make for cheap visual scenarios at $9/month; Workato when integration is an enterprise programme with a six-figure budget.

Watch-outs

• Flows die with their owner. A cloud flow runs on its owner’s connections; when that person leaves and the account is disabled, the flow fails — sometimes weeks later. Guard: put every business-critical flow in a solution, owned by a service account or service principal, with connection references and a named co-owner, and add “which flows does this person own?” to the offboarding checklist.
• One premium action changes the licence of every user. Add a Salesforce or HTTP step to a flow fifty people trigger manually and each of them needs Premium — or the flow needs a Process licence. Guard: audit premium-connector flows in the admin center’s Power Automate usage area before go-live, and attach a Process licence to shared flows instead of buying Premium for the audience.
• Request limits will tighten. Microsoft currently throttles per flow at transition limits (200,000 a day for Premium) and has said enforcement moves to per-user limits — 40,000 for Premium, 6,000 for seeded — at least six months after usage reporting goes GA. Guard: design high-volume flows against the per-user numbers now and move anything above them to a Process licence or a flow group.
• Self-healing is not maintenance-free RPA. It repairs one moved element at a time and is still in preview. Guard: keep desktop flows on stable selectors, alert on every failed run, and keep the maintenance hours in the plan rather than cutting them on the strength of self-healing.

Related: AI agent vs RPA works through when a bot or an agent is the better buy, using Microsoft’s own price list.