Automation articles
Power Automate licensing for small business: seeded rights, Premium seats and Process capacity
Power Automate licensing for small business has three layers: the rights already seeded into every Microsoft 365 seat, Power Automate Premium at Microsoft’s list price of $15 per user per month, and Power Automate Process capacity at $150 per bot per month. Most teams need nothing extra until a flow touches a premium connector — and that cliff, not the seat count, is what decides the bill.
What your Microsoft 365 plan already covers
Every licensed Microsoft 365 user already holds seeded Power Automate rights. Those rights let anyone create and run cloud flows built on standard connectors — SharePoint, Outlook, Teams, OneDrive, Forms, Excel Online and the built-in Approvals connector — inside a daily allowance Microsoft’s licensing tables put at 6,000 Power Platform requests per user. For a routine approval, a document-filing routine or a notification chain, that is the whole license story.
What seeded rights deliberately exclude is just as important: premium and custom connectors, the on-premises data gateway, business process flows, AI Builder, process mining, and every form of desktop RPA. Microsoft’s seeded-license documentation (opens in new tab) sets out the entitlement table line by line, including the one exception worth knowing — a premium-connector flow can ride on a seeded Power Apps or Dynamics 365 license when it is in-context and associated with that app, which does not apply to a plain Microsoft 365 seat.
One more seeded right catches people out in a useful way: Windows licenses cover local, attended execution of desktop flows on the machine itself, with no cloud orchestration. You can automate a legacy application on one PC for free; scheduling that automation from a cloud flow is a paid capability.
The premium-connector cliff
The cliff is per flow, not per tenant. A flow stays free on seeded rights until it adds a premium connector, and then the whole flow needs cover. In small-business builds, the usual triggers are a SQL Server database, an HTTP call to a line-of-business API, a custom connector, an on-premises data gateway reaching a server in the closet, Dataverse tables, or a desktop flow driving software with no API at all.
Once a flow crosses that line, one of two things has to pay for it. Either the people who own and trigger the flow hold Power Automate Premium seats, or a Power Automate Process license is allocated to the flow so the automation carries its own entitlement. Which of those is cheaper has nothing to do with company size and everything to do with the ratio of premium flows to the people who touch them.
Seeded rights vs Premium vs Process, side by side
The table below compares the three ways a small business pays for Power Automate: the rights bundled into Microsoft 365 seats, the Premium user license, and Process capacity. Prices are Microsoft list prices for annual billing, and the daily action limits are the published entitlements — Microsoft notes those requests run under higher limits during the current transition period.
| Dimension | Microsoft 365 seeded rights | Power Automate Premium | Power Automate Process |
|---|---|---|---|
| List price | Included with the Microsoft 365 seat | $15 per user / month | $150 per bot / month |
| What is licensed | The user | The user | A cloud flow or a machine |
| Standard connectors | Included | Included | Included |
| Premium & custom connectors | Not included | Included | Included |
| On-premises data gateway | Not included | Included | Included |
| Attended RPA (desktop flows) | Not included | One attended bot per seat | Not included |
| Unattended RPA | Not included | Not included | One unattended bot, allocated to a machine |
| AI Builder credits | Not included | 5,000 per month | 5,000 per month |
| Process mining | Not included | Included | Not included |
| Daily action limit | 6,000 per user | 40,000 per user | 250,000 per license, stackable up to 10 |
| Best fit | Approvals and notifications on Microsoft data | Makers who need premium connectors or attended RPA | One shared flow used by many people, or unattended RPA |
Premium per user or Process per bot?
Count people against flows, not headcount against budget. Premium licenses a person: every maker who builds or edits premium-connector flows needs one, and each seat carries a single attended RPA bot. Process licenses an automation: allocated to a cloud flow that sits in a solution, it lets unlimited users in your organization run that flow regardless of their own licenses, with 250,000 actions a day behind it.
Two practical rules fall out of that. When a handful of makers each build their own premium flows, seats win — five Premium licenses cost $75 a month, half the price of a single Process license. When one important flow serves the whole company, capacity wins, because $150 covers everyone who triggers it instead of $15 for each of them. The crossover sits at ten people: ten Premium seats and one Process license both list at $150 a month.
Unattended RPA removes the choice entirely. A desktop flow that runs overnight with nobody signed in needs Process capacity allocated to the machine — Premium only ever carries an attended bot. Note the pairing rule too: when a cloud flow triggers a desktop flow, the user whose connection runs it still needs a Premium license, so unattended automation is usually one Process license plus at least one seat, not capacity alone. Microsoft’s Power Automate license types documentation (opens in new tab) is the reference to check before any purchase order goes in.
A worked example
Illustrative scenario — not a client. A 40-person distributor wants invoice approvals that read order data from an on-premises SQL Server and post the result back to SharePoint. The SQL connector and the gateway both sit on the paid side, and every person who submits an invoice triggers the flow.
Licensing it per user means 40 Premium seats at $15 — $600 a month, $7,200 a year, for one flow. Licensing the flow instead means one Process license at $150 plus one Premium seat for the maker who builds and maintains it: $165 a month. Same automation, same connectors, a quarter of the cost, purely because the entitlement was attached to the flow rather than to everyone who touches it. Flip the scenario — three departments each building their own SQL-backed flows — and three Premium seats at $45 a month beat any capacity purchase.
Where licensing meets the build
Licensing is the recurring half of the decision; the build is the one-time half. Our Power Automate consulting scopes are written with the license position stated up front — each flow marked as covered by your existing Microsoft 365 rights, as needing a Premium seat, or as needing Process capacity — so the renewal never surprises you. If you are still choosing a platform, Power Automate vs Zapier compares seeded rights against per-task billing, and replacing email approvals shows what the seeded tier alone can deliver. Teams weighing which processes justify a paid seat at all should start with the processes worth automating first.
Reporting licenses follow a different logic entirely — per-viewer rather than per-flow — so if the same renewal covers dashboards, read Power BI licensing for small business alongside this guide rather than assuming the two products price the same way. And if you are moving off a legacy workflow tool, our Nintex to Power Automate migration services mark every rebuilt workflow against these same entitlements before work starts.
FAQ
Questions we get on every automation scope
Partly. Every Microsoft 365 seat carries seeded Power Automate rights: cloud flows built on standard connectors such as SharePoint, Outlook, Teams, Forms and Approvals, within a daily action allowance. Premium and custom connectors, the on-premises data gateway, desktop RPA and AI Builder are not included and need a paid plan.
Premium connectors cover SQL Server, Azure services, most third-party line-of-business systems, and HTTP actions; custom connectors and the on-premises data gateway sit on the same paid side. The moment a flow adds one, seeded Microsoft 365 rights stop covering it and someone needs Premium or Process capacity.
Microsoft lists Power Automate Premium at $15 per user per month, paid yearly. That seat covers standard, premium and custom connectors, one attended RPA bot, process mining, the on-premises data gateway, AI Builder credits, and a daily action limit of 40,000 requests per user.
Microsoft renamed it. The Power Automate Process license replaced the per-flow plan and lists at $150 per bot per month. Allocated to a cloud flow, it licenses the automation itself — premium connectors included, unlimited users inside your organization, 250,000 actions a day — rather than the people running it.
For standard-connector flows, seeded Microsoft 365 rights cover both the maker and the people the flow touches. For premium-connector flows, licensing follows the owning and triggering users — unless a Process license is allocated to the flow, which covers unlimited users in your organization regardless of their own licenses.
Entitlements are counted in daily Power Platform requests, not runs. Microsoft's tables allocate 6,000 per day to a Microsoft 365 seeded user, 40,000 to a Premium user, and 250,000 to each Process license, which can be stacked. A busy multi-step flow consumes several requests per run.
Related reading
Decide what to build before you buy seats
Power Automate vs Zapier
Seeded rights and seats against per-task billing — which model costs less for a Microsoft 365 team.
Power BI Licensing Explained
The reporting side of the same renewal: Pro, Premium Per User and Fabric capacity for a small team.
Fixed-Fee Automation Service
One written price, senior US-based engineers, and the license position for every flow stated in the scope.
Book a free consultation
Get more from the Microsoft tools you already pay for
Tell us what you’re trying to fix — a report, an approval process, an intranet, a Copilot rollout. We scope it as a fixed-fee project, you approve, and a senior engineer delivers in 2–4 weeks.
- Fixed-fee scope agreed before any work starts
- Senior, US-based Microsoft engineers — no handoffs
- Typical 2–4 week delivery
- 30 days of post-delivery hypercare included
The fastest way to reach us is the form — tell us the task and we’ll reply within one business day.