Whose License Counts in Power Automate? Manual vs. Automated

Anyone who has ever shared a Power Automate flow with a colleague knows the confusion: one person can start the flow without any problem, while the other immediately gets a licensing error. The reason almost always comes down to the same, often overlooked question: whose license actually counts when a flow runs?

The answer depends solely on the trigger type, not on who originally built the flow, who owns the individual connections, or who is currently logged in. Microsoft's official documentation clearly distinguishes between manually triggered (instant) flows and automated or scheduled flows. This article summarizes the official rule, shows the most important special cases, and helps you avoid licensing errors before they show up in production.

The basic rule: the trigger type decides

According to Microsoft's official Power Automate licensing FAQ, a simple but consequential distinction applies: Automated and scheduled flows always run in the context of the flow owner, regardless of who started the flow or which accounts are used for the connections in the flow. Instant flows, i.e. flows with a manual trigger (button, hybrid trigger), on the other hand run in the context of the calling person, regardless of the connections used in the flow.

In concrete terms, this means: for automated flows, whoever owns the flow is the one relevant for licensing. For manual flows, whoever triggers the flow manually is the one relevant for licensing. Everything else, such as who set up the connections in the flow, plays no role in the licensing question.

Manual trigger: the license of the triggering person counts

For a flow with a manual trigger, for example a button flow, every person who actually starts the flow needs an appropriate license. If the flow uses a premium connector, every triggering person needs a Power Automate Premium license, or the flow itself needs a per-flow plan, as described in the Power Automate triggers troubleshooting guide. It states literally: if your flow uses a manual trigger, the connection of the person who triggers the flow is required.

This has a practical side effect that often causes confusion: even if the flow creator set up all the connections themselves, the person who actually starts the flow at the push of a button must bring their own valid connection. If this connection is faulty or an adequate license is missing, the flow fails for that specific person, while the owner can continue to start it without any problem. Access that previously worked but suddenly fails with a licensing message often points, according to Microsoft, to an expired license of the triggering person.

Automated and scheduled trigger: the flow owner's license counts

For automated flows, for example triggered by a new email or a new record, as well as for scheduled flows with a recurrence trigger, only the license of the flow owner counts. If such a flow uses a premium connector, only the owning person needs a premium license, no one else involved needs their own. The connections in this case also run on the creator's account: if the flow uses the recurrence trigger, it runs on the flow creator's connections, regardless of who originally shared the flow or adjusted it afterwards.

For teams, this is a clear advantage for automated processes: a single, properly licensed flow owner is enough for an automated flow to run for the entire organization, as long as no one else needs to trigger or edit it manually.

Special cases that are often overlooked in practice

Approvals don't need their own premium license

According to Microsoft, anyone who responds to an approval request within a premium flow, i.e. approves or rejects it, does not need a premium license of their own for this. The flow continues to run in the licensing context of the owner or the triggering person; responding to the approval does not count as a separate trigger.

Child flows inherit the context of the parent flow

If an automated parent flow calls a child flow, the child flow generally uses the license of the parent flow's owner, unless the child flow has its own per-flow plan. If the parent flow, on the other hand, is a manual flow, the child flow inherits the context of the person who triggered the parent flow.

Shared manual flows with multiple users

If a manual premium flow is shared with an entire team and every person is allowed to start it themselves, every single person actually needs a premium license, because each call runs in its own licensing context. Microsoft explicitly names this scenario in the licensing FAQ and recommends a per-flow plan for the whole flow instead of individual user licenses in such cases.

Practical tip: per-flow plan instead of individual licenses

As soon as several people need to trigger the same manual flow with premium connectors, a per-flow plan for the flow is often worthwhile instead of a premium license per person. With a per-flow plan, no one needs an individual license, but the capacity is tied to exactly that one flow. For automated flows, on the other hand, this switch is rarely worthwhile, because there only the owning person needs to be licensed anyway. Important to know: this assignment is not automatically enforced by Microsoft, but a recommendation. According to Microsoft, the responsibility for licensing all flows correctly lies with the organization's administrators.

Frequently asked questions

As the flow owner, do I need a premium license if a colleague triggers the flow manually?

No, in this case your license as owner does not count. For manual flows, the person who actually triggers the flow needs the appropriate license for the connectors used, regardless of who created the flow.

Why can I start my shared flow, but a colleague can't?

This is almost always due to missing or faulty connections, or an insufficient license for the triggering person. For manual flows, every person needs their own valid connection, and for premium connectors, an appropriate license as well.

Is a Microsoft 365 license enough to use premium connectors?

No. According to Microsoft, a Power Apps, Dynamics 365, or Microsoft 365 license is not enough to edit or manually trigger a flow with premium connectors. A standalone Power Automate Premium license or a per-flow plan for the flow is required for this.

What happens if the owner of an automated flow leaves the company?

The flow continues to run under the original owner's license as long as nothing changes. For solution flows, an administrator can change the owner; for non-solution flows, co-owners must export the flow and re-import it under a new owner for the new owning person's license to take effect.

Does the license of the person who set up the connections in the flow count?

No. According to Microsoft, who needs a license does not depend on whose connections are used in the flow, but solely on the trigger type: the owner's license for automated and scheduled flows, the triggering person's license for manual flows.