When Is the M365 License Enough? 5-Question Self-Test (FAQ)

Many teams work in Power Automate exclusively with the Power Automate entitlement already included in their Microsoft 365 license, without ever consciously choosing a dedicated automation plan. That works fine for a long time, until a flow suddenly needs a connector that can't be added, or an error message about the daily action limit shows up. This self-test walks you through five questions covering the points where, in practice, it's decided whether your M365 license is enough for Power Automate or whether you need to upgrade to Power Automate Premium or a process license. As of: July 2026.

The basis for this comes from Microsoft itself, in the official Power Automate licensing FAQ and in the overview of license types. Answer the five questions in order, and by the end you'll know exactly where your current license hits its limit and what the next sensible tier would be.

Question 1: Are you really only using standard connectors?

With a Microsoft 365 license such as Office 365 E3, E5, Business Standard, or Business Premium, you're allowed to create and run automated, scheduled, and button flows, but exclusively with standard connectors. According to the Power Automate licensing FAQ, premium connectors, custom connectors in app context, on-premises gateways in app context, robotic process automation (RPA), and AI Builder are explicitly not included in these licenses.

Whether a connector is standard or premium is shown directly when you add an action: premium connectors carry their own icon. A complete overview is provided by Microsoft's list of all premium connectors. If you find even a single connector there that your flow needs, such as SQL Server, Salesforce, or many Azure services, the plain M365 entitlement is no longer enough at this point.

• Only SharePoint, Outlook, Teams, OneDrive, Excel Online, and similar Microsoft 365 services in the flow? Then you're usually in standard territory.
• A single premium or custom connector in the flow? Then you need at least a Power Automate Premium license for this flow.

Question 2: Do you reliably stay under the daily action limit?

Every single action in a flow, from the trigger to the last condition, counts against a daily limit. With a Microsoft 365 license, this limit is 6,000 actions per day according to Microsoft, raised to 10,000 actions per day during the currently ongoing transition period. This is stated in the Power Automate licensing FAQ and in the Power Platform request limits. For comparison: with Power Automate Premium the limit is 40,000 actions per day, and with a process license 250,000 actions per day, and stackable.

Important to note: these limits are not pooled across a team. Eight users with an M365 license each get their own 6,000 actions, not a shared 48,000. So anyone running a single, heavily used flow, for example a loop over hundreds of rows in an Excel table several times a day, hits the standard license's limit faster than it might seem at first glance.

Question 3: Do you need RPA, process mining, or AI Builder?

Attended or unattended RPA, meaning automating desktop applications without an API, as well as process mining and AI Builder credits, are, according to the overview of license types, included exclusively in the Power Automate Premium license or in process licenses. An M365 license alone does not cover any of these three areas. So if you want to automate a legacy application without an interface via mouse-click simulation, or have forms read out by AI, that's a clear signal for an upgrade.

Question 4: Does your flow run inside a Dataverse for Teams environment?

There is an exception that is often overlooked in practice: inside a Dataverse for Teams environment, M365 licenses are, according to Microsoft, also allowed to access premium connectors; outside this environment, the restriction from question 1 still applies without limitation. So if your flow is firmly tied to a team in Microsoft Teams and works there with a Dataverse for Teams database, a premium connector can, as an exception, work within this scope without a separate premium license. As soon as the same flow is meant to run outside this context, the regular rule applies again.

Question 5: Are you scaling to many parallel or unattended runs?

For flows that run permanently in the background, automate unattended, or generate a high, predictable volume of actions, the user-based premium license is often not the right answer, but rather a process license. According to Microsoft, it is not tied to a person but to a cloud flow or a machine, though it must be placed in a solution for that, and it brings noticeably more capacity with 250,000 actions per day than an individual's premium license. Up to ten process licenses can, according to the documentation, even be stacked on a single cloud flow.

What to do if one of the five questions was answered with no

If the M365 license is no longer sufficient at at least one point, that doesn't automatically mean the whole team has to upgrade right away. Often it's enough to assign a premium or process license specifically to individual people or individual flows, while the rest of the organization continues to work with the free M365 entitlement. Anyone unsure which license combination makes economic and technical sense for their own setup is best off having that checked as part of NordFlux's Power Automate consulting. That way you keep control over what's actually being paid for and where the standard entitlement is enough.

Frequently asked questions

What exactly counts as one action in Power Automate?

Every single step in a flow, from the connection call through a condition to the final output, counts as its own action, including failed attempts and automatic retries during pagination. A flow with a loop over 500 rows can therefore quickly generate several hundred actions in a single day, even if it was only triggered once.

Is a single premium license enough for the whole team?

No. The Power Automate Premium license is a user license and only applies to the person it's assigned to. For an automated or scheduled flow, the flow owner's license counts; for a manually triggered flow, the license of the person calling it counts. For multiple users who need premium, each individual person needs their own license.

What is the difference between a premium and a process license?

The premium license is tied to a person and intended for the classic everyday office use with occasional automation. The process license, on the other hand, is a capacity license assigned to a single cloud flow or a machine, regardless of who runs it, and is suited for unattended or very action-intensive processes with a significantly higher daily limit.

What does the currently ongoing transition period mean for the action limits?

Microsoft has stretched out the enforcement of the official, lower action limits over time so organizations can analyze their usage and purchase suitable licenses before the stricter limits take effect. During this phase, M365 licenses temporarily get 10,000 instead of 6,000 actions per day. Anyone already working close to the limit today should not plan around the higher transition values, but should use the permanent limits as the benchmark.

Do I have to unlock premium connectors for the whole company if only one flow needs them?

No. It's enough to assign a Power Automate Premium license specifically to the person who owns or triggers that one flow. All other flows in the tenant that work exclusively with standard connectors keep running unaffected under the existing M365 entitlement.