Power Automate in Microsoft 365: what's included and where the premium trap begins

The Microsoft 365 license includes Power Automate, but only in a clearly limited tier: standard connectors such as Outlook, SharePoint, Teams and Forms, with a quota of 6,000 actions per user and day. As soon as a flow touches a premium connector, it needs its own Power Automate license, and the premium connectors include, of all things, everyday tools such as SQL Server, HTTP calls, Dataverse and all on-premises and custom connectors. This is exactly where the most common cost shock for SMEs arises. As of: July 2026, facts according to Microsoft Learn licensing documentation.

What the M365 license actually covers

With the usage right included in Microsoft 365, users may build and run flows with standard connectors, that is, automate the core of everyday office work: saving email attachments, obtaining approvals, capturing form data, notifying Teams. The detailed license documentation from Microsoft draws the boundaries clearly: no premium connectors, no cloud-based desktop flow orchestration, no business process flows, and the daily quota of 6,000 actions is reached faster than you'd think for a single busy flow, because every loop iteration counts.

The premium connectors everyone underestimates

• HTTP: the universal building block for any API connection is premium. Anyone who wants to address an external interface leaves the M365 world.
• SQL Server and Azure SQL: connecting your own database is premium, as is virtually every Azure connector.
• Dataverse: Microsoft's own data platform, the foundation of many templates and all model-driven apps, is premium.
• On-premises gateway and custom connectors: connecting to local systems or self-built interfaces: premium.

The full list is provided in the license FAQ from Microsoft. The rule of thumb: anything beyond the Office services costs extra.

What does the step into premium cost?

Two models are available. Power Automate Premium licenses the user: 40,000 actions per day, all premium connectors, plus attended RPA and AI Builder quota. Power Automate Process instead licenses the individual flow: 250,000 actions per day, usable by any number of people, and shareable across up to 25 flows via flow groups, which is often the savings lever for SMEs when a few central flows serve everyone. Euro prices change occasionally; current figures are on the Microsoft pricing page; the underlying system remains stable.

The rules almost nobody knows

Three licensing mechanics regularly cause surprises. First, for automated flows the flow owner's license counts, while for manually triggered flows it's the trigger's license, so anyone who uses a colleague's premium flow may themselves need a license depending on the setup. Second: if the owner loses their premium license, the flow is throttled and disabled after 14 days, a silent cause of outages during staff changes. Third, saving on licenses via a shared service account as multiplexing is expressly not allowed. How to set up your flows independently of individual people is covered in the article about orphaned flows when an employee leaves.

Whether your project fits within the M365 tier or needs premium, and whether per-user or per-flow is cheaper, we work out concretely in the Power Automate license consulting before licenses are purchased.

Frequently asked questions about the Power Automate license

Is Power Automate included free of charge in Microsoft 365?

Yes, every M365 Business and Enterprise license includes Power Automate usage rights for standard connectors with 6,000 actions per user and day. For premium connectors, RPA and higher quotas, Power Automate Premium (per user) or Process (per flow) is additionally required.

How do I know my flow needs a premium license?

By the connector: as soon as a step uses HTTP, SQL, Dataverse, a custom connector or the on-premises gateway, Power Automate requires a premium license and shows this as a license error when saving or running. The premium marking also appears directly on the connector in the designer.

What happens to premium flows when the license lapses?

The flow doesn't simply keep running: after the license is lost it is first throttled and deactivated after 14 days, as documented in Microsoft's license FAQ. During staff changes, the license and ownership question therefore belongs in every offboarding checklist, otherwise processes stop unnoticed.

Is the Process license per flow cheaper than Premium per user?

If a few central flows serve many people, usually yes: the Process license is tied to the flow, not to the users, provides 250,000 actions per day and can be distributed across up to 25 flows via flow groups. If, on the other hand, many individual premium flows of individual power users are running, the Premium license per person pays off. The threshold depends on current pricing, so it's worth doing the concrete calculation before buying.