Power Automate licensing confuses nearly every beginner — and getting it wrong means flows that fail in production or budgets that spiral unnecessarily. This lesson cuts through the plan tiers, connector rules, and API limits to give you a clear, practical framework for choosing the right license for any automation scenario.
You've just discovered Power Automate. You've watched a demo, you're excited about automating that repetitive invoice-processing task your team does every Friday afternoon, and you're ready to build your first flow. Then someone in IT asks: "What license do you have?" Suddenly, what felt like a simple tool becomes a bureaucratic puzzle involving plan tiers, per-user vs. per-flow pricing, premium connectors, and something called "attended vs. unattended RPA." You're not alone — licensing is one of the most common stumbling blocks for new Power Automate users, and getting it wrong costs real money.
Here's the good news: once you understand the logic behind how Microsoft structures Power Automate licensing, the whole system starts to make sense. There's a clear rationale behind why certain features cost more, and knowing that rationale helps you make smarter decisions — whether you're a single analyst automating your own workflows or an IT administrator rolling out automation to an entire department. This lesson cuts through the marketing language and gives you a practical, honest map of what each plan actually covers.
By the end of this article, you'll be able to look at any automation scenario and confidently determine which license tier covers it, where the limits are, and how to avoid accidentally building something that breaks when you hit a licensing wall.
What you'll learn:
No prior licensing knowledge is required. You should have a basic familiarity with what Power Automate does — if you've never opened the tool before, take a quick look at Getting Started with the Power Automate Interface: Navigating the Designer, Understanding Flow Structure, and Running Your First Test first. Understanding what a flow, trigger, and action are will help you follow along, but we'll define anything licensing-specific from scratch.
Microsoft licenses Power Automate based on two dimensions: who runs the flow and what the flow connects to. Everything else — the different plan names, the pricing tiers, the add-ons — is a variation on those two ideas.
Think of it like a parking garage. The basic garage (your Microsoft 365 subscription) covers standard parking spots for everyday vehicles. If you bring an oversized truck (a premium connector), you need a bigger spot that costs more. If you want a professional driver to park your car while you're away and the garage is closed (unattended RPA), that's a premium service on top of everything else.
Let's build up from that foundation.
Power Automate has a concept of a licensed user — the person or account under which a flow executes. This matters because Microsoft's usage limits (how many times a flow can run per day, how frequently it can be triggered) are tied to licensing. A flow running under a Per User plan gets a certain number of "API calls" (requests sent to connectors and services) per day. Exceed that, and your flows get throttled — slowed down or queued until the next day's quota resets.
Key insight: Every flow in Power Automate runs in the context of a licensed user or a licensed flow. If you try to share a flow that uses premium features with a colleague who only has a standard license, their copy of the flow will fail the moment it hits a premium connector.
This is the single most important concept to understand before you look at any plan. Power Automate connects to other software through connectors — pre-built integrations for services like SharePoint, Outlook, Salesforce, Twilio, and hundreds of others. Microsoft divides connectors into two categories:
Standard connectors are included with any Microsoft 365 license that includes Power Automate. These cover the Microsoft productivity suite: SharePoint, Outlook, Teams, OneDrive, Excel, Forms, Planner, and many common third-party services like Twitter, Slack, and RSS feeds.
Premium connectors require a paid Power Automate plan. These include connectors for services like Salesforce, ServiceNow, Dataverse (Microsoft's own business database), SQL Server (when accessed directly, not via on-premises data gateway in some contexts), Adobe PDF Services, and hundreds of others. You can recognize a premium connector in the Power Automate designer because it displays a small diamond icon next to its name.
Warning: This is where many beginners get burned. You can build an entire flow using premium connectors in the free trial, publish it, and have it run for 30 days — then watch it fail entirely when your trial expires and your colleagues try to use it on a standard license. Always check your connectors before investing hours in a build.
To see whether a connector is standard or premium, open Power Automate, click on the connector you're interested in, and look for a "Premium" label in the connector details panel. The official connector reference at Microsoft's documentation site also lists every connector's tier.
If your organization uses Microsoft 365 (formerly Office 365), you almost certainly already have access to Power Automate at a basic level. Plans like Microsoft 365 Business Basic, Business Standard, Business Premium, and many enterprise E-tier plans include Power Automate with standard connectors.
This is genuinely useful. You can automate email notifications with Power Automate, build flows that trigger when files are added to SharePoint, send Teams messages based on form submissions, and handle a huge range of everyday productivity automation — all without paying a penny more than your existing Microsoft 365 subscription.
The limits here are:
For a solo analyst who wants to stop manually copying data from one spreadsheet to another or who wants to automatically route incoming emails to folders, the included license is genuinely sufficient. You can build a surprising amount with just standard connectors, especially if your organization lives inside the Microsoft 365 ecosystem.
Tip: Before purchasing any paid plan, spend two weeks mapping out exactly what you want to automate. Most beginners find they can accomplish 70–80% of their goals with what's already included in Microsoft 365. Only the remaining scenarios — typically those involving Dataverse, SQL, or line-of-business SaaS tools — actually require a paid upgrade.
The Power Automate Premium plan, often still referred to by its older name "Per User," is priced per user per month and gives that individual user access to all premium connectors, higher API call limits (40,000 requests per user per day — 20 times the standard limit), and the ability to run attended desktop flows.
This is the right plan when:
Let's make this concrete. Imagine you're a sales operations analyst. Every Monday morning, you need to pull the previous week's closed deals from Salesforce, cross-reference them against a budget spreadsheet in SharePoint, and push summary records into a Dataverse table for executive reporting. That workflow touches two premium connectors (Salesforce and Dataverse). Under a Microsoft 365-only license, it simply won't work. Under a Power Automate Premium per-user license, it runs without issue.
The "attended" desktop automation capability that comes with Premium is worth understanding separately. "Attended" means the desktop flow runs while you're sitting at your computer — it automates mouse clicks and keyboard inputs in a visible window on your screen, with you present. This is useful for automating repetitive tasks in applications that don't have APIs, like legacy insurance systems or older ERP software. For more on what this looks like in practice, the article on Desktop Flows: Automate Legacy Applications with RPA in Power Automate walks through the mechanics in detail.
This plan — sometimes called Power Automate Process or the RPA add-on depending on when Microsoft last renamed it — includes everything in Premium plus unattended desktop automation.
"Unattended" means the flow runs on a machine when no one is logged in. The automation happens in the background, typically on a dedicated machine or virtual machine, without requiring a human operator to be present. This is true enterprise RPA (Robotic Process Automation) — the kind that runs overnight batch jobs against legacy systems, processes invoices at 2 AM, or crawls through on-premises applications on a schedule.
Unattended RPA requires a dedicated machine (physical or virtual) running the Power Automate Desktop agent, and the license is priced per bot/process, not per human user. If you want three bots running simultaneously on three different virtual machines, you pay for three Process licenses.
Key insight: The attended vs. unattended distinction isn't just a feature flag — it reflects a fundamentally different operational model. Attended automation augments individual human workers. Unattended automation replaces repetitive human labor entirely by running autonomously on infrastructure you manage.
This plan is appropriate when your automation needs to run on a schedule without human involvement, particularly against desktop applications that can't be reached via cloud APIs.
Here's where the math gets interesting. Instead of licensing by the person, the Per Flow plan licenses a single flow to run for unlimited users within the organization. You pay for the flow itself, not for each person who triggers or benefits from it.
When does this make sense? Consider a document approval workflow used by your entire 500-person company. Every employee submits expense reports through a SharePoint form, which triggers a Power Automate flow that routes the report to their manager, collects approval, and writes the result to Dataverse. Under a Per User model, every one of those 500 employees who triggers that flow would need their own premium license. Under a Per Flow model, you pay for the flow once, and all 500 employees can trigger it regardless of their individual license level.
The Per Flow plan typically requires a minimum purchase of five flows per month. The break-even point compared to per-user licensing depends on how many people interact with each flow — for broadly shared organizational flows with many users, Per Flow wins. For specialized flows used by just one or two people, Per User wins.
Tip: Use Per Flow licensing for flows that are part of shared business processes — approval workflows, IT service desk automations, onboarding sequences. Use Per User licensing for flows that belong to specific power users or analysts doing specialized data work. Mixing both strategies in a single organization is completely normal and often optimal.
Every Power Automate plan comes with a daily API request limit. An "API request" is roughly equivalent to one action step in a flow — each time a connector talks to an external service, that's a request. A flow that reads 100 rows from SharePoint, transforms each one, and writes them to Dataverse could consume hundreds or even thousands of API requests per run.
Here's a rough breakdown by plan:
| Plan | Daily API Requests |
|---|---|
| Microsoft 365 (included) | 2,000 per user |
| Power Automate Premium | 40,000 per user |
| Power Automate Process | 250,000 per flow |
For straightforward flows that run a few times a day on small datasets, even the basic 2,000 limit is more than enough. Where you'll hit the ceiling is in scenarios like handling pagination and throttling when querying large datasets, processing email attachments in bulk, or running flows that loop through thousands of records.
When your flow gets throttled, it doesn't fail — it waits. Actions queue up and execute when capacity becomes available. The practical result is delayed automation, which in time-sensitive scenarios can be a real business problem. If your invoice processing flow needs to complete within 30 minutes and throttling pushes it to the next day's quota window, that's a problem that licensing solves.
Warning: Throttling is silent by default. Your flow will show as "succeeded" even when throttled, but the timestamps will reveal significant delays between actions. If you're building time-sensitive automation, test under realistic volume conditions before deploying to production.
Microsoft offers a few ways to explore Power Automate without immediately committing to paid licensing:
The 90-day trial gives you full premium access, including all premium connectors and RPA capabilities. It's ideal for evaluating whether premium features are genuinely needed for your use cases. Sign up through the Power Automate homepage with a work or school account.
The Developer Plan (also called the Power Apps Developer Plan) gives individual developers an ongoing free environment with premium connectors for development and testing purposes — but explicitly prohibits using it for production flows or business-critical automation. It's perfect for learning, experimentation, and building prototypes.
Think of the trial as your 90-day window to build everything you're considering, test whether premium connectors are actually required, and gather the data you need to justify purchasing the right plan to your manager or procurement team.
Let's work through a realistic licensing assessment together. Imagine you're setting up automation for a small HR team of 8 people. Here's what they want to automate:
Scenario 1: When a new employee onboarding form is submitted via Microsoft Forms, automatically create a task in Planner and send a welcome email from Outlook.
Scenario 2: When a manager submits a salary review request via a SharePoint form, route it through a multi-step approval process and write the final approved amount to a Dataverse table for payroll integration.
Scenario 3: Every night at 11 PM, an unattended bot should log into the legacy HR system (a desktop application with no API), extract headcount numbers, and paste them into an Excel report in SharePoint.
Now let's audit each scenario:
Scenario 1 analysis: Microsoft Forms, Planner, Outlook — all standard connectors. This runs entirely on the included Microsoft 365 license. License cost: $0 additional.
Scenario 2 analysis: SharePoint (standard) and Dataverse (premium). The approval routing itself is standard (you can learn how approval flows are built in the article on building approval workflows with Power Automate), but writing to Dataverse requires premium. Since this flow is shared across the whole HR team, a Per Flow plan makes more sense than buying premium licenses for all 8 users. License cost: one Per Flow license.
Scenario 3 analysis: Unattended desktop automation against a legacy system. This requires a Power Automate Process (RPA unattended) license plus a dedicated machine or virtual machine to run the bot. License cost: one Process license, plus infrastructure for the bot machine.
Result: For this HR team, the recommended licensing stack is:
This is a dramatically cheaper outcome than purchasing 8 Premium per-user licenses for everyone, which would be the instinctive (and wrong) approach.
Mistake 1: Assuming everyone who triggers a shared flow needs a premium license This is the most expensive mistake in Power Automate licensing. When a flow is licensed under the Per Flow plan, any user can trigger it regardless of their own license level. Only the flow itself needs the premium license — not the individual human pressing "submit."
Mistake 2: Building in a trial, forgetting to re-license before go-live Your trial gives you 90 days of premium access, and it's easy to build flows that use premium connectors without tracking that dependency. Create a simple habit: in the notes field of every flow you build, document which connectors it uses and whether they're standard or premium. This makes the licensing conversation with IT much cleaner.
Mistake 3: Ignoring API limits until throttling causes production issues If your automation runs against large volumes — thousands of records, hundreds of emails — calculate your estimated API consumption before choosing a plan. The math is straightforward: number of actions per flow run × number of runs per day = daily API requests. Compare that to plan limits and size up accordingly.
Mistake 4: Using the Developer Plan for production automation It's tempting to use the free developer environment indefinitely. Microsoft's terms of service prohibit this for production use, and more practically, developer environments can be reset or reclaimed by Microsoft with little warning. Don't build anything business-critical on a developer plan.
Mistake 5: Overlooking the cost of the machine for unattended RPA The Process license covers the Power Automate rights for unattended automation, but it doesn't include the infrastructure. You need a Windows machine (physical or virtual) running constantly. Factor in VM costs, Azure compute pricing, or the cost of a dedicated on-premises machine when calculating the true cost of unattended RPA.
Licensing doesn't have to be a maze. Once you understand that Power Automate licensing is fundamentally about two things — what connectors you need and how many people run each flow — the right plan becomes much clearer.
Here's the decision framework in brief:
Your next steps should be practical: pull up the Power Automate connector list, catalog the services your planned automations need to touch, and classify them as standard or premium. That single exercise resolves 90% of licensing decisions.
From here, you might want to get hands-on with building your first actual flow. If you're ready to start, Your First Power Automate Flow: Automated Email Notifications That Actually Work walks through a complete, working automation end-to-end. If you're thinking about organizing flows across a team or department, Organizing and Reusing Logic with Power Automate Environments, Connections, and Flow Templates covers how environments map to licensing boundaries — an important consideration once you're past the individual-user stage.
Licensing is infrastructure. Get it right once at the start, and everything you build on top of it runs smoothly.