You have a Microsoft 365 licence, you know there is something called Power Automate sitting somewhere in your admin console, and you are wondering if it can take the Monday morning chore of copying data from one tool to another off your plate. So what is power automate? It's a workflow automation tool from Microsoft that builds chains of actions across your apps with little or no code. Whether it costs you extra depends on more than one thing, and the most common trigger is which connectors your flows touch.
What Power Automate actually does
Microsoft describes the tool as a way to organise business processes and automate repetitive tasks, using an intuitive interface and many connectors so you can create workflows without knowing how to code. In practice, that means you drag steps together in a visual editor: when this happens, then do this. You might route new invoices from your email into a SharePoint list. Or notify the ops team on Teams when stock drops below a set number. Maybe move files from one folder to another and log them in Excel.
Building anything requires a Microsoft work or school account first. Most Microsoft 365 accounts are work accounts, so check which account you sign in with.
Where it fits in a UK business day
Chores repeat weekly: chasing a signature, reconciling two exports, sending a reminder. If each step lives inside Microsoft or a service with an API connector, Power Automate can chain them into one flow that runs while you are not looking at the screen. The value isn't cleverness. It removes the human hand from a task where mistakes creep in when someone is tired or interrupted.
Cloud flows versus desktop flows
There are two main kinds of flow, and they do different jobs. A cloud flow triggers automatically, instantly, or on a schedule, running entirely against API endpoints. You set up the trigger ("new email arrives") and the actions ("save attachment to SharePoint"), then it fires in Microsoft's infrastructure without anyone touching a keyboard.
A desktop flow works differently. It automates tasks on the web or the desktop by simulating clicks and keystrokes. That is how you get into legacy applications, terminal emulators, local Excel files, or folders that have no API. This is sometimes called robotic process automation (RPA), because a software bot performs physical interface actions rather than calling services over a network.
Attended versus unattended
Desktop flows run in one of two modes. An attended flow runs with human supervision: someone sits at the PC, starts the flow, and watches it go. An unattended flow runs on its own, on a registered machine, so no person is present when it executes. That distinction matters for licensing, as we will see in the cost section.
Which one do you start with?
In our experience, most businesses should begin with cloud flows. They are faster to build, easier to maintain, and they do not tie up a user's screen while they run. Desktop flows earn their place when you need to automate software that has no connector: an older ERP front end, a banking portal that only works in a browser, or any line-of-business app that predates modern APIs. If every step of your chore can be done through an API, stay in the cloud flow world.
What is included without paying extra
This is where readers get confused, because Microsoft's own documentation says other licences across Microsoft 365, Dynamics 365, and the Power Platform include a limited set of Power Automate capabilities. In plain terms: some of what you can do with Power Automate comes bundled with the licence you already hold for your email or calendar.
The free tier
Microsoft also offers a Free licence that lets users create cloud flows using standard connectors. And if you want to trial the full experience before committing, there is a 30-day trial of UI-based cloud flows and standard connectors.
That is not always the case. The safest habit is to check your own licence view first, then build. Before you build a flow with steps you're unsure about, stop and confirm with IT whether your tenant covers them.
What trips a flow into a paid licence
Microsoft separates connectors into standard, premium, and custom categories, each carrying a different entitlement. A connector is simply the piece of plumbing that links your flow to an external service: the Word connector talks to Microsoft Word documents, the SharePoint connector moves files between libraries. If every connector in your flow is standard, and you are using a licence that covers standard connectors, the flow runs within whatever action limits apply to that plan.
But the moment one step requires a premium connector, the whole flow needs a premium entitlement. One Reddit user put it bluntly: "How come all the Word connectors are premium connectors on the Power Automate????". That frustration is understandable. Check each connector in your flow before you build, because one poster found the Word connectors were premium.
What the premium user licence gives you
With a Power Automate Premium per-user licence, you can create, run, and share unlimited cloud flows within action limits, using standard, premium, and custom connectors. That is the key upgrade: it removes the connector-type restriction so your flow does not care which category each step falls into.
The governance layer on top of licences
Separate from pricing, an IT admin can block specific connectors entirely across the tenant. One user reported that after about a year, their IT department blocked all connectors, including non-premium ones, and employees now had to individually request use of each connector they needed. That is not a licensing issue; it's a governance decision. Before you invest time building flows, ask your admin which connectors are enabled in your tenant so you do not build something that is technically valid but administratively blocked.
What Power Automate costs in the UK
Microsoft lists three paid plans on its UK pricing page, all billed yearly and excluding VAT. We checked these figures on 18 November 2026; Microsoft notes that prices shown are for marketing purposes only and may differ at checkout depending on currency, country, regional, and organisational variant factors.
| Plan | Price per month (ex VAT) | Who it is for |
|---|---|---|
| Power Automate Premium | £11.50 per user | People who build and run flows that use premium connectors |
| Power Automate Process | £115.30 per bot | Unattended desktop flows or high-volume API flows running on a machine you control |
| Power Automate Hosted Process | £165.30 per bot | The same, but hosted in Microsoft's infrastructure rather than your own server |
Per-user versus per-bot: where the decision lands
Power Automate supports both user licensing and capacity (per-bot) licensing. The per-user Premium plan is straightforward: each person who needs to build or run flows with premium connectors pays £11.50 a month. If you have five people automating their own chores, that's roughly £57.50 before VAT.
The Process and Hosted Process plans shift the model from "who builds it" to "what runs it." Each Process licence includes up to 250,000 actions per day, and you can stack multiple licences on one flow or share a single licence across a group of flows. Flows must be packaged in a solution for a Process licence to be assigned. When that licence is attached to a machine, it becomes an unattended bot capable of running one desktop flow at a time.
A worked example
Say your finance team has a legacy banking portal with no API. You need two unattended flows to run every morning: one downloads the transaction file, the other posts line items into a SharePoint list. That is one machine, two sequential desktop flows, running without anyone present. In this hypothetical, one Process licence at £115.30 per month (ex VAT) could cover that setup, provided your total daily actions stay within the 250,000 limit. A Power Automate Premium user would need to register the machine before the licence can be allocated to it. If you later add a third flow on the same machine, it still runs one at a time under the single bot licence; you would need a second licence only if two flows must run simultaneously.
What we tell clients
The per-user price is easy to budget for and simple to understand. The per-bot pricing is easy to misjudge, because the cost adds up as you add bots. In most of the projects we have scoped, the decision isn't "which calculator do I use?" but "am I automating someone's repetitive clicks, or am I running a service that processes thousands of records overnight?" The first is usually per-user Premium; the second is Process or Hosted Process.
When Zapier or n8n makes more sense
We will be straight with you: if your stack is heavily Microsoft, Power Automate is the natural choice. You already have the licence infrastructure, the admin console, and the compliance story aligned to one vendor. A commenter on Reddit captured a practical split that we find useful in our own work: "keep PA for the MS compliance, and use a node-based tool like n8n for the heavy API lifting". That's one person's view, but it matches what we see across clients who run a mixed estate.
Where a neutral tool wins
If most of your apps are not Microsoft products, or if you need complex branching, webhooks into third-party APIs, and self-hosting for data residency reasons, a platform-agnostic tool may be simpler to set up and cheaper at scale. Zapier is the low-friction option, and our n8n guide describes n8n as offering more control over logic and self-hosting. We have written separate guides on what is Zapier for a plain-English look at that side, and what is n8n if you want the self-hostable alternative. Our Zapier vs n8n comparison walks through the trade-offs in more detail.
Where Power Automate wins
When your flows touch SharePoint, Teams, Outlook, Word, or Dynamics 365, the native connector set is faster to configure than wiring equivalent steps into a third-party tool. And because the platform sits inside the Microsoft admin centre, you get tenant-wide policy controls, such as blocking connectors, and licence management in one place rather than juggling two vendor consoles.
The hardest part of automation projects is rarely the technology. It is deciding which tool owns which process so that nobody has to maintain two copies of the same logic.
Our workflow automation case study is one example of automating admin work. If you would rather talk through your specific stack before committing to either path, our automation service is where we help you map the chore, pick the tool, and build the first flow.
In practice · Case study
Workflow Automation
Giving the editorial team their time back — permanently.
Read the case studyKey terms
- cloud flow
- An automation that Microsoft runs in its own infrastructure. It is triggered automatically, instantly or on a schedule, and calls services through their APIs.
- desktop flow
- An automation that works through the screen of a web or desktop app, clicking and typing the way a person would. It is the route into software that has no API.
- premium connector
- A connector that needs a premium entitlement before a flow can use it. The connector type decides which licence a flow needs.
- robotic process automation (RPA)
- Software bots that carry out repetitive tasks in an application by copying the actions a person would take on screen.
- unattended bot
- A licensed machine that runs a desktop flow with no one present. Under a Process licence it runs one desktop flow at a time.
Frequently asked questions
Is Power Automate free?
What is Power Automate used for?
Why does my flow need a premium licence?
Can my IT team block connectors?
Do I need a developer to use Power Automate?
Sources
- What is Power Automate?, Microsoft Learn (accessed 18 Nov 2026)
- Introduction to desktop flows, Microsoft Learn (accessed 18 Nov 2026)
- Types of Power Automate licenses, Microsoft Learn (accessed 18 Nov 2026)
- Power Automate pricing, Microsoft (accessed 18 Nov 2026)