What it does

Power Automate licensing splits two ways: user licences assigned to people, and capacity licences allocated to an automation — a cloud flow, a machine, a hosted machine, a hosted machine group. A user licence grants that person entitlements; a capacity licence grants the automation its own entitlements regardless of who touches it.

Key facts

• The current standalone user licence is Power Automate Premium. Alongside it sit Power Automate Free, a self-service Trial lasting 90 days, and admin-managed 30-day trials of Premium, Process or Hosted Process.
• The current capacity licences are Power Automate Process and Power Automate Hosted Process.
• Power Automate Per-user plan and Per-flow plan are legacy. They still work but shouldn't be renewed — Premium and Process replaced them. P1 and P2 are grandfathered and haven't been purchasable since the end of 2020.
• Seeded rights come from Microsoft 365, Dynamics 365 Enterprise, Dynamics 365 Professional, Dynamics 365 Team Member, Power Apps licences and Windows licences. Microsoft 365 seeded rights cover standard connectors only.
• Power Apps and Dynamics 365 seeded licences do include premium and custom connectors, but only when the flow is in-context and associated with the app the licence comes from. An isolated flow needs a standalone Power Automate licence.
• Windows licences give attended desktop flows for personal productivity in the default environment only, with no sharing, no other environments, and no cloud flows.
• Automated and scheduled flows run under the owner's licence context. Instant flows run under the invoking user's.
• Guest users need a licence from either the host tenant or their home tenant. Licences aren't recognised across different Azure clouds.
• Microsoft defers the full entitlement detail to the Power Platform Licensing Guide PDF, and that document is the contractual reference rather than the Learn pages.

When to use / skip

Microsoft's own recommendation is Premium for every user and a Process licence per business process or per unattended machine, and as a starting position for sizing that's reasonable. In reality most clients have a large seeded population who genuinely only need standard connectors in-context, and a much smaller group who need premium. The work is identifying which is which before someone buys Premium for everyone or, worse, builds the whole solution on seeded rights and discovers at UAT that it isn't licensed.

Configuration decisions

• Whether the premium requirement is covered per user or moved onto the flow with a Process licence, which usually turns on how many people invoke it.
• Whether flows run under a service account or service principal, because a service principal owner pushes the flow onto the non-licensed user pool rather than a user entitlement.
• Whether auto-claim policies assign Premium automatically when a user hits a premium requirement, which reduces manual assignment but also removes a natural cost gate.
• Whether pay-as-you-go environments are in scope as an alternative to upfront licences.
• Which environments are Managed, given Managed Environments require premium use rights for their users.

Gotchas

• "In-context and associated with the app" is the phrase that decides whether seeded premium rights apply. It's a real technical association, not a description of intent, and clients consistently assume the looser reading.
• Flow ownership determines the licence context for automated and scheduled flows, so a flow built by a departing contractor carries their licence position until ownership changes.
• If the owner loses their Premium licence, the flow is downgraded to lower performance, owners are notified, and it's turned off after 14 days if nothing is done.
• Dynamics 365 base-plus-attach licensing only grants request limits on the base licence. Attach licences add nothing.
• The Free licence can't share flows at all, which surprises people who assumed it was simply a lower tier.
• Trial licences aren't available in government clouds.

Consultant notes

• Do the licensing assessment during design, not before UAT. The most expensive Power Platform conversation is the one where a working solution turns out to need a licence the client didn't budget for.
• Never quote prices from memory or from a Learn page. Point the client at the Power Platform Licensing Guide and their Microsoft account team, and put that in writing.
• Watch for premium creep. A flow that started on standard connectors and gained one HTTP action is now a premium flow, and nobody logged the change.
• Where a flow is invoked by many people, moving the licence onto the flow is usually both cheaper and simpler to administer than licensing every invoker.
• Licensing changes more often than the product does. Date your advice and say when it was checked.

---

Worth revisiting each release wave, and immediately if the client is approaching a renewal — this area changes faster than the rest of the platform.