Power Automate Pricing and Premium Connectors

Power Automate Pricing and Premium Connectors

· by Panayot Dimkov

Power Automate pricing for businesses confuses people because the short answer and the long one contradict each other. The short one is "you already pay for it". The long one is "until you stop, and then the jump is not small". Understanding where that line sits is what separates a realistic budget from a surprise three months in.

The line has a name: premium connectors. As long as your flows use standard connectors (Outlook, SharePoint, Teams, Excel, lists), the Microsoft 365 licence you already pay for covers them. The moment just one needs a premium connector, such as SQL Server, Salesforce or an HTTP call, you start paying: £11.50 per user per month with Power Automate Premium, or £115.30 per bot per month if the process has to run unattended (Microsoft's UK list prices, paid yearly, excluding VAT; €13 and €130 in Spain).

This article covers what each plan costs, when you start paying extra, which licence makes sense depending on who triggers the flow and how the bill grows without anyone noticing. If you are after the total cost of a project, including analysis and development, see how much it costs to automate a process with AI.

1What is already paid for and where it ends

Almost any Microsoft 365 business plan includes seeded Power Automate capacity. It is not a trial or a demo: it is real functionality, and for many administrative processes it is enough. Windows 11 adds another piece at no cost, Power Automate for desktop, which automates personal tasks on your own computer (attended RPA), although its flows cannot be shared or launched from the cloud.

✅
What is covered at no extra cost
Flows triggered by an email, a form, a file in SharePoint or a message in Teams. Moving information between those applications, generating documents, requesting approvals and notifying. In other words: a good share of everyday administrative automation. Standard connectors also include third-party services such as Gmail, Dropbox or Slack.
⚠️
Where it ends
The moment the flow needs a premium connector. And one is enough: it does not matter that the other nine steps are standard. If the flow touches a SQL Server database, Salesforce or SAP, uses a custom connector or makes an HTTP call, that flow now requires a paid licence. There is also a volume limit: with Microsoft 365, each user gets 6,000 actions a day, and a flow that exceeds them is slowed down.
👥
And who it affects
This is the nuance that breaks most budgets. If the flow is automated or scheduled, only its owner needs a Premium licence. But if each person launches it (from a button or an app), Microsoft requires Premium for every user who runs it: a premium flow launched by forty people means forty licences, unless a Process licence is assigned to the flow itself.
Before designing anything, ask this: can this flow be built with standard connectors, or does it need a premium one? The answer changes the cost by a large factor, and sometimes the flow can be redesigned to stay standard.

2Power Automate pricing by plan

These are the list prices Microsoft publishes on its UK website, per month, paid yearly and excluding VAT (on its Spanish site they are €13, €130 and €186.30; in the US, $15, $150 and $215). The final price in your contract may vary depending on the agreement, the partner and the commitment term, so use them to size, not to budget.

TierWhat it unlocksList price
Included with Microsoft 365 Cloud flows with standard connectors, Microsoft or third-party. No extra cost
Premium Premium and custom connectors, attended desktop flows (RPA) and basic process mining. £11.50/user/month
Process Unattended RPA: the process runs with nobody signed in. Licensed per bot, and it can also be assigned to a cloud flow to cover it for all its users. £115.30/bot/month
Hosted Process The same but with the virtual machine hosted by Microsoft, no infrastructure of your own. £165.30/bot/month

The jump that catches almost everyone out is the third. Going from attended to unattended is not an incremental upgrade: it changes the licensing model from "per person" to "per robot" and multiplies the figure. It is worth asking whether the process genuinely needs to run at three in the morning with nobody there, or whether running when someone arrives is enough.

The flip side of that jump is a detail few people take advantage of: a Process licence can be assigned to a cloud flow, or to a group of up to 25 flows within a solution, and it then covers the flow whoever triggers it. For the flow used by forty people, that is £115.30 a month instead of £460.

Watch out if your flows use AI (reading invoices, classifying emails): from 1 November 2026, new or renewed Premium licences no longer come with AI Builder credits, and those features draw on Copilot Credits, which are bought separately. Credits already purchased are honoured until the end of the contract.

3How the bill grows without you noticing

01
The connector that slips in
Someone adds a step to query a database and the whole flow becomes premium. If the person editing it starts a free trial, it works until the trial expires; when the owner has no Premium licence, Microsoft slows the flow down, sends a notice and turns it off after 14 days if nobody acts.
02
The flow that catches on
A manually launched premium flow starts in one department and ends up used by half the company. Per-user pricing turns internal success into a growing bill, unless someone moves it to a Process licence.
03
Unnecessary unattended
An unattended bot is bought because "then it runs on its own", when the process could perfectly well run during working hours. The most expensive mistake on this list.
04
Uncontrolled sprawl
Dozens of small flows created by different people, with no inventory and no owner. They consume capacity, overlap and nobody knows which are still needed.
None of these four problems is technical: all four are governance. An inventory of flows with an owner and periodic review costs very little and prevents almost every billing surprise.

4When Power Automate is worth paying for

The tool is neither good nor bad in the abstract: it fits or it does not, depending on where your process lives.

SituationFit
The company already uses Microsoft 365 and the process moves between email, SharePoint, Teams and Excel Very good
Two or three external applications need integrating occasionally Good, with a premium licence
The process lives outside Microsoft and needs complex logic or many transformations Worth comparing
Full control is needed over where data resides, or self-hosting is required Consider alternatives

That last point deserves a note. Some organisations need, by internal or sector regulation, to know exactly where their data is processed and to deploy on their own infrastructure. There, tools with a self-hosting option change the equation, even if operating them is no longer just a licence cost.

5What to ask before signing

  • Which connectors will each flow use? Have the supplier list them one by one and mark which are premium. That is the information that decides the cost.
  • How many people will run each flow? Not how many build it: how many trigger it. If the flow is launched manually, that is the number that multiplies; above ten, compare it with a Process licence.
  • Is unattended genuinely needed? Ask what would happen if the process ran at nine in the morning instead of three at night. Sometimes the answer is "nothing".
  • Can it be redesigned to stay standard? Often a design change avoids the premium connector without losing functionality. Worth asking explicitly.
  • Who maintains the inventory? An owner with a quarterly review prevents silent sprawl.

Prices and licensing terms change fairly often. Before closing numbers, check them on the official Power Automate pricing page or with your Microsoft partner.

Frequently asked questions

Is Power Automate included in Microsoft 365?

Partly. Almost every Microsoft 365 business plan lets you build cloud flows with standard connectors: Outlook, SharePoint, Teams, Excel or Forms, and also third-party services such as Gmail or Dropbox. Premium connectors and RPA launched from the cloud are not included and are paid for separately.

What exactly is a premium connector?

It is a connector Microsoft reserves for paid licences: databases such as SQL Server, HTTP calls, custom connectors and systems such as Salesforce or SAP. One is enough to make the flow premium: if it is automated or scheduled, its owner needs Premium; if each user triggers it, every one of them does, unless the flow has a Process licence.

How much does Power Automate unattended RPA cost?

Unattended RPA, which runs processes with nobody signed in, is licensed per bot with Power Automate Process: £115.30 per bot per month on Microsoft's UK list price (€130 in Spain, 150 dollars in the US), paid yearly and excluding VAT. The Hosted Process option, with the machine hosted by Microsoft, costs £165.30. Confirm the current price with your partner or on the official portal.

Which is cheaper, Premium per user or a Process licence?

It depends on how many people trigger the premium flow. Premium costs £11.50 per user per month; a Process licence assigned to the flow costs £115.30 and covers everyone. At ten users they cost about the same; beyond that, the Process licence is cheaper.

How does the bill grow without you noticing?

Three common ways: adding a premium connector to a flow that many people trigger, moving from attended to unattended automation without recalculating, and piling up flows with no inventory or owner. Review licences and consumption periodically, not only when you sign up.

In short

Power Automate is very cheap while your flows use standard connectors, and stops being cheap the moment they need a premium one. All cost planning boils down to knowing which side of that line each flow falls on, how many people will run it and whether it genuinely needs to run unattended.

With those three answers you can estimate the licence before building anything. And if the process does fall on the expensive side, it is almost always worth asking whether it can be redesigned back to the cheap side. That is part of what we do in the analysis that precedes automating.

What licences would your automation need?

Tell us which process you want to automate and which applications it has to talk to. We will tell you what your current licence covers, what would need adding and whether it can be avoided.

Request a process assessment