Power Automate Licensing — How Far Microsoft 365 Gets You for Free, and When You Need Premium

“Power Automate comes with Microsoft 365, so it’s free, right?” Companies that start automating on that assumption often come to us some time later. “I tried to connect to SQL Server and got a ‘premium’ warning.” “The flow I built as a trial stopped working after 90 days.” “I’ve been told the flow will stop when the person who built it leaves.” All of these come down to how the licensing works.

And they are half right. A Microsoft 365 license does include use rights (so-called seeded rights) that let you build Power Automate cloud flows at no additional cost, and approval flows, notifications, and SharePoint list integration really can be built within the free tier. The problem is that the boundary of that tier is drawn connector by connector, and it is hard to notice until you have started building and hit the wall. This article organizes Power Automate’s licensing structure starting from “what do you want to do”: the free tier, the moment premium becomes necessary, how to choose a paid plan, and the points people trip over in practice.

Note that this article does not cover prices themselves. Prices get revised, whereas the structure of “which tier of license lets you do what” is relatively stable. Always confirm the current terms on Microsoft Learn and the official pricing pages.

1. The Bottom Line First

• A Microsoft 365 license includes creating and running cloud flows (automated, scheduled, and button-triggered) that use standard connectors. Automation around SharePoint, Outlook, Teams, Forms, and Excel Online can be built at no additional cost.¹²
• However, these use rights are positioned as “extending Microsoft 365 for personal productivity,” they carry a cap of 6,000 actions per user per day, and they do not include premium connectors, custom connectors, the on-premises data gateway, RPA, or AI Builder.¹³
• Dataverse, SQL Server, HTTP (the general-purpose HTTP action), and custom connectors are all premium. “It’s just calling an external web API, so it must be free” does not hold.⁴⁵
• Paid plans fall broadly into two families: Power Automate Premium, assigned to a user, and Power Automate Process, assigned to a flow or a machine (the successor to the old per-user plan, per-flow plan, and unattended RPA add-on). Structurally, it is a question of whether counting by people or by processes comes out cheaper.⁶⁷
• Automated and scheduled flows run under the flow owner’s license, while button-triggered instant flows run under the license of the person who runs them. If you share a button flow containing a premium connector across a department, everyone who runs it needs Premium (or you assign Process to the flow).⁸
• Approvals store their data in Dataverse, but the Approvals connector itself is a standard connector. You can build approval flows on a Microsoft 365 license.⁹
• The 90-day trial (Power Automate Trial) can be activated by users themselves and lets you try almost every premium feature. Convenient as that is, a classic accident is drifting into production use while still on the trial, and having flows stop when it expires.⁶¹⁰

2. The Big Picture — What Microsoft 365’s “Seeded” Rights Actually Are

Power Automate licensing is made up of two families: user licenses (assigned to people) and capacity licenses (assigned to the automation itself, such as a flow or a machine).⁶

Within the user license family, there are limited use rights that come bundled as an “extra” with licenses for other products such as Microsoft 365, Dynamics 365, and Windows. Microsoft’s documentation calls these seeded licenses. This is what “Power Automate is included in 365” actually refers to.³

Here is what the Microsoft 365 seeded rights let you do.¹

• Creating and running automated flows, scheduled flows, and button flows
• Using standard connectors
• Up to 6,000 actions per user per day

Conversely, what is not included is spelled out explicitly.¹³

• Premium connectors
• Custom connectors
• The on-premises data gateway
• RPA (desktop flow orchestration)
• AI Builder

Microsoft Learn positions these use rights as “limited use rights that allow users to customize and extend Office 365 for personal productivity scenarios,” and explicitly recommends Premium licenses for enterprise usage.¹ In other words, Microsoft’s own framing is that “the Power Automate included in 365” is a right intended for automation that stays within Microsoft 365, and was never intended from the outset to serve as a business automation platform reaching into in-house systems and external services.

The 6,000 actions per day cap is another figure that is easily misread. It counts not the number of flow runs, but the execution of each individual trigger and action within a flow. Actions inside a loop are counted on every iteration, so even a simple flow like “save the attachment from each email” can consume a surprising amount when the volume is high. Exceeding the cap does not stop things immediately; runs are throttled in proportion to how far over you are.⁸

3. Standard vs. Premium Connectors — This Is Where the Line Sits

Connectors come in two tiers, Standard and Premium, and which tier a connector belongs to is fixed per connector. Organizing the ones commonly used by small and mid-sized businesses gives the following.

Three points where people commonly trip up:

• HTTP is premium. “Even for a service with no connector, you can call it with the HTTP action as long as it has a web API” is perfectly true — but that general-purpose HTTP connector is treated as premium.⁵¹¹ If you have estimated integration with a core system or a web service on the basis that “calling it over HTTP is free,” that assumption collapses here. Note that in the specific case where the thing you want to call is the SharePoint REST API, you can substitute the “Send an HTTP request to SharePoint” action included in the standard SharePoint connector, with no additional license.¹¹
• The Dataverse connector is premium, but the Approvals connector is standard. Approvals store records in Dataverse behind the scenes, but the Approvals connector itself is a standard connector, and you can create approval flows on a Microsoft 365 license. The Dataverse database that this requires is provisioned automatically the first time you create an approval flow, in the default environment.⁹ The moment you build a configuration that touches Dataverse tables directly through triggers or actions, however, it becomes premium.⁴
• Use rights for the on-premises data gateway are not included in Microsoft 365 either. A configuration where a cloud flow reaches an on-premises SQL Server or file share involves both gateway use rights and premium connectors, so in practice it lives firmly in paid-plan territory.³

Premium connectors are labelled “Premium” in the flow designer, so you can check before you build. If a user without a license tries to run a flow containing a premium connector, it fails with a licensing error called DirectApiAuthorizationRequired.⁵

4. How the Paid Plans Are Structured — Premium or Process, Which Do You Count By?

When premium features become necessary, there are three main options today. The naming was reshuffled a few years ago, so be careful: information using the old names mixes freely into search results. The old per-user plan was replaced by Premium, and the old per-flow plan and old unattended RPA add-on were replaced by Process.⁷

The axis for choosing is simple: do you count by “the number of people using it” or by “the number of business processes”?

• If a specific member of staff simply builds flows that use premium connectors and lets them run automatically, one Premium license for that owner is enough. Automated and scheduled flows run under the owner’s license, so the staff who cause the trigger (the person putting a file in SharePoint, the person answering a Form) need no license at all.⁸
• If everyone in a department uses a button-triggered premium flow, or if there is a core process that consumes a large volume of actions, it is more sensible to assign Process to the flow. A flow with Process assigned passes the license check no matter who runs it.⁸⁶
• Microsoft’s documentation lists unattended RPA, service-principal-owned flows, high action volume, and premium flows triggered by many people as the criteria for applying Process.⁸

Note that Process is strictly a license for flows and machines, and is not a substitute for a user license. The people who build flows and the people who manage desktop flows still need a user-side license.⁶

5. Licensing for RPA (Desktop Flows) — PAD Alone Is Free; Integration Is Where You Start Paying

Power Automate for desktop (PAD) can be used at no additional cost as part of your Windows 10/11 use rights, as long as you are building desktop flows on your own PC and running them attended on that same machine. But this scope is “local execution in the default environment only (no orchestration)” — you cannot share flows, and you cannot create them in an environment other than the default one.³¹

Once you start building it into your business processes, licenses become necessary in the following order.

• Calling a desktop flow from a cloud flow (attended): the user of the connection used to make the call needs Premium. If a user on a Free license tries to add the “Run a flow built with Power Automate for desktop” action, they are prompted to start a trial.⁶¹⁰
• Unattended execution: a Process license assigned to the machine is required. On top of that, registering the machine itself has to be done by a user holding a Premium license, so “just buy Process and unattended RPA works” is not the case.⁶
• If you do not want to own a physical machine: Hosted Process lets you configure unattended execution on a Microsoft-hosted machine.⁶

As an investment decision, the safe route is a staged one: “first confirm the benefit with PAD alone and manual execution, then upgrade to automation with Premium/Process once the value is proven.” How to actually build data entry automation into a core system is covered in “Automating Data Entry Into Legacy Core Systems With Power Automate for Desktop.”

6. AI Builder Credits — AI Features Like OCR Are Consumption-Based

When you build AI Builder actions into a flow — document OCR (form processing), text classification, and so on — they consume a metered allowance called AI Builder credits. A set amount of credits is included with premium licenses such as Power Automate Premium, and they need to be available in the environment where the flow runs.¹² There is also an AI Builder capacity add-on for buying more, but as of 1 November 2025 it is no longer sold to new customers, and we are in a transition period in which add-on renewals for existing contracts and the seeded credits bundled with Premium both end on 1 November 2026. AI Builder’s functionality itself is not going away and remains available through the successor Copilot credits, so if you are adopting it now, plan your costs on the assumption of Copilot credits rather than the add-on.¹³

The current comparison table states that 5,000 credits per month are included with each of the Premium, Process, and Hosted Process licenses. Consumption rates differ per scenario: form processing (extracting data from documents) consumes relatively heavily, while simple text extraction consumes less.⁶ Since AI Builder is not included in the Microsoft 365 seeded rights, “just trying out OCR within the free tier” is not possible.¹

Whether 5,000 credits a month is enough depends on your document volume. A concrete design based on OCR of faxed purchase orders, along with how to estimate credit consumption, is set out in “Reading Faxed Purchase Orders With AI Builder.”

7. A Collection of Practical Pitfalls

Drifting Into Production While Still on the 90-Day Trial

Power Automate Trial is a 90-day trial license that users can activate themselves, offering roughly the same capabilities as Premium (excluding AI Builder credits and storage) plus unattended RPA.⁶ Because you are prompted with “would you like to start a trial?” the moment you touch a premium feature, it is not unusual for a trial to have started without the person concerned ever consciously thinking about licensing.¹⁰

The problem arrives 90 days later. A premium flow whose owner has lost their premium license is downgraded to reduced performance, all owners are notified, and if nothing is done, the flow is disabled after 14 days.¹⁴ The typical accident is: “a flow built for evaluation quietly became part of the business, and only when it stopped 90 days later did anyone realize there was a licensing problem.” If you are going to build something substantial on a trial, you should budget for the license cost of full adoption from the outset.

The Relationship Between the Owner’s License and Flow Execution

To repeat: automated and scheduled flows run in the flow owner’s license context, while instant flows (buttons, launches from an app) run under the license of the person who runs them.⁸ Several practical consequences follow.

• For an automated flow, staff who cause the trigger and approvers who respond to approval requests do not need premium licenses. You do not have to buy Premium for every approver.¹⁵
• Conversely, if you share a button flow containing a premium connector, everyone who runs it must have Premium. In that case, consider assigning Process to the flow.⁸
• For a co-owner who has been shared a flow containing premium connectors to edit it or run it manually, that person also needs a license at the premium level.¹⁶
• When an owner leaves the company, the flow loses the owner’s license and enters the 14-day rule described above. A flow contained in a solution can have its owner changed; a flow that is not can be rebuilt via export/import by a co-owner (running as a new flow under the new owner’s license), or rescued by assigning Process.¹⁴

Flow ownership, connections, and handover design are, alongside licensing, the critical points of operation. These are covered in “Preventing Key-Person Dependency in Power Automate — Designing Ownership, Connections, and Handover.”

“Sharing One License Around” Is a Licensing Violation

The idea that “we’ll just buy one Premium, assign it to a shared account, and everyone will use that account” is a configuration Microsoft calls multiplexing, and it is explicitly treated as a licensing violation. Learn’s FAQ states, with a concrete example, that a setup where multiple users share a service account’s credentials and use premium flows through the single Premium license assigned to that account is non-compliant.¹⁵

The rule of thumb for judging is “who receives value from the flow.” Because execution of automated and scheduled flows happens in the owner’s license context, someone who merely adds an item to a list and thereby triggers a flow, or who merely responds to an approval request, does not by that fact alone need a premium license. If the flow just sends an email to the owner, the owner’s license suffices. On the other hand, the same FAQ cites a configuration where a premium flow returns the result (an email) to the person who submitted the item as an example of multiplexing — the submitter is indirectly triggering the flow and receiving value from it, so Premium is needed for that person in addition to the owner. If you are returning the results of a premium flow to a large number of people, the safe answer is simply to license the flow itself with Process.¹⁵

Approval Flows Are Within the Free Tier — but Touching Dataverse Directly Is Not

Approval flows can be built on a Microsoft 365 license (as covered in Section 3).⁹ But go one step further — reading and writing approval history directly through the Dataverse connector, or picking up changes to approval tables with a Dataverse trigger — and you are in premium territory. Knowing about this step change (“approvals were free, but adding reporting on the history turned out to cost money”) will keep your estimates honest. The design of approval flows themselves is set out in “Building an Approval Workflow in Power Automate — Digitizing Paper and Email-Based Approval Requests.”

8. Decision Table — What You Want to Do, and the License You Need

If you are unsure, check the “Premium” label on the connector in the flow designer, then think through “who triggers this flow (automatically, or by button?)” and “which is larger, the number of users or the number of processes?” — in that order, and you can pin down the license you need almost every time.

9. Summary — Treat License Fees as Development Costs Paid in Instalments

Microsoft 365’s seeded rights genuinely cost nothing extra as long as you stay within standard connectors. The fact that approvals, notifications, and SharePoint integration — the entry points into automation for a small business — all fit inside the free tier is something you should straightforwardly take advantage of. On the other hand, the moment you step out into core systems, external APIs, RPA, or OCR, you enter premium territory, and from there you incur an ongoing cost of “people × monthly fee” or “processes × monthly fee.”

When evaluating that cost, we recommend not looking at the monthly fee alone, but converting it into a total of monthly fee × number of people (or processes) × number of years in use, and comparing that against the alternatives. A few Premium licenses over five years can add up to the price of a small piece of bespoke development; conversely, if the requirements are complex and the flows will keep demanding maintenance effort, building a dedicated system from the start can be cheaper in total. And of course, there are plenty of cases where, compared against the cost of an off-the-shelf package or bespoke development, Power Automate is dramatically cheaper even with the license fees. The important thing is to abandon the “it’s included in 365, so it’s free” assumption early, and make the investment decision about automation on the basis of a total cost that includes licensing.

Which processes to automate at which license tier, and where to switch over to development instead — we can help with everything from that line-drawing discussion through to bespoke development of the parts that Power Automate cannot accommodate.

Related Articles

• Automating Business Processes with Power Automate — Cloud Flows, Desktop Flows, and Robust Error Handling
• Building an Approval Workflow in Power Automate — Digitizing Paper and Email-Based Approval Requests
• Automating Data Entry Into Legacy Core Systems With Power Automate for Desktop
• Reading Faxed Purchase Orders With AI Builder
• Preventing Key-Person Dependency in Power Automate — Designing Ownership, Connections, and Handover

Related Consulting Areas

KomuraSoft LLC handles everything from automation design consulting — including Power Automate license selection — through comparing license costs against development costs, to turning processes that a flow cannot accommodate into proper systems.

• Technical Consulting & Design Review
• Windows App Development
• Contact

References

Related Articles

Recent articles sharing the same tags. Deepen your understanding with closely related topics.

Related Topics

These topic pages place the article in a broader service and decision context.

Frequently Asked Questions

Common questions about the topic of this article.

How far can I get with Power Automate on a Microsoft 365 license alone?

As far as creating and running cloud flows (automated, scheduled, and button-triggered) that use standard connectors such as SharePoint, Outlook, Teams, Forms, and Excel Online. There is a cap of 6,000 actions per user per day. Premium connectors, custom connectors, the on-premises data gateway, RPA (managing and integrating desktop flows), and AI Builder are not included in the Microsoft 365 use rights and require a paid license such as Power Automate Premium.

Can I use the HTTP connector on a Microsoft 365 license?

No. The general-purpose HTTP connector (the HTTP action) is treated as premium, and like SQL Server, Dataverse, and custom connectors it requires a license such as Power Automate Premium. That said, if all you want to do is call the SharePoint REST API, you can substitute the "Send an HTTP request to SharePoint" action included in the standard SharePoint connector, and in that case no additional license is needed.

Should I choose Power Automate Premium or Process?

Premium is a license you assign to a user; Process is a license you assign to a flow or a machine. If a specific member of staff simply builds and runs a handful of flows that use premium features, buy Premium per person. If a button-triggered premium flow is used by a large number of people, or you need unattended RPA or high-volume runs, it is more sensible to assign Process per flow (or per machine), since that removes the need for the person running it to be licensed. Compare which number is larger: the number of people using it, or the number of business processes.

Is Power Automate for desktop free to use?

Within your Windows 10/11 use rights, you can build desktop flows on your own PC and run them attended on that same machine at no extra cost. What is not included is orchestration: creating flows outside the default environment, sharing flows, and calling them from a cloud flow. Cloud flow integration requires Power Automate Premium, and unattended execution requires a Process license on top of that.

Author Profile

Profile page for the article author.

Go Komura

Representative of KomuraSoft LLC

Focused on Windows software development, technical consulting, and investigations into failures that are difficult to reproduce.