Power Automate Licensing Explained

Power Automate licensing is one of those topics teams often postpone until after the workflow design starts.

That usually backfires.

In Power Automate, licensing is not just a billing concern. It changes what kind of automation you can build, who can run it, and how independently it can operate.

Why this lesson matters

Licensing decisions affect:

• cloud versus desktop automation
• attended versus unattended RPA
• connector access
• machine setup
• monitoring and management access
• action capacity and scaling

That means licensing has to be understood as part of architecture, not after architecture.

The short answer

As of May 6, 2026, Microsoft's official docs describe two main licensing families for Power Automate:

• user licenses
• capacity licenses

The main user license is Power Automate Premium, which Microsoft recommends for users needing the full set of cloud and desktop automation capabilities.

The main capacity licenses are Process and Hosted Process, which are automation-centric and are used for scenarios like unattended RPA or flow-level capacity.

If you only remember one thing, remember this:

Who owns the automation and how independently it must run usually determines the license model.

User licenses: person-centric automation rights

User licenses are assigned to people.

They are the right mental model when you are asking:

• can this user build flows
• can this user use premium connectors
• can this user run attended desktop automation
• can this user manage or monitor automation resources

Microsoft's docs position Power Automate Premium as the main user license for full cloud and desktop automation.

There are also limited free, trial, or seeded rights in parts of the Microsoft ecosystem, but those are not the same as a full production-ready entitlement model.

Capacity licenses: automation-centric rights

Capacity licenses are allocated to automations rather than to people.

That matters when the question becomes:

• should this cloud flow have its own capacity
• should this machine run unattended desktop automation
• should the automation keep working regardless of which user triggered it

This is where Process and Hosted Process licenses matter.

They are less about a person's toolkit and more about the automation's runtime entitlements.

Premium matters when users need full build-and-run capability

Microsoft's current docs say Premium gives users full cloud and desktop automation capabilities, including premium and custom connectors and attended desktop RPA on a registered machine.

That makes Premium the default production user license for many teams.

If the workflow depends on premium connectors or attended desktop automation, this question appears quickly.

Process matters when the automation itself needs higher autonomy

The Process license matters most in two common situations:

• a cloud flow needs automation-level capacity and premium connector use regardless of the triggering user's license
• a machine needs unattended desktop RPA

Microsoft's docs also note that flows must be in a solution for a Process license to be assigned to a cloud flow.

That means solution-aware design is not just governance advice. It can directly affect licensing viability.

Hosted Process matters when the business wants hosted desktop automation

Hosted Process is the higher-control, less-infrastructure-heavy option in Microsoft's current model.

It is useful when the organization wants hosted machine capacity and RPA at scale without owning as much of the underlying physical machine management.

The exact economics and fit can change over time, but the architectural point is stable:

hosted automation changes the operational model.

Attended versus unattended is one of the biggest licensing forks

This is where many teams get tripped up.

Attended RPA is closer to user-driven automation. Unattended RPA is closer to automation that should run without a human present.

Microsoft's docs tie unattended execution to Process or Hosted Process style capacity.

That means the moment the team wants the workflow to run autonomously on a machine, licensing becomes a different conversation.

Licensing also affects capacity and scale

Power Automate does not just license features. It also licenses operational headroom.

That includes things like:

• action volume
• premium connector usage
• machine-level automation capacity
• monitoring and management access

This is why scaling a successful flow often pushes teams into a licensing review even if the original pilot worked fine.

Common mistakes

Mistake 1: Treating licensing as a purchase-only problem

In Power Automate, licensing is part of system design.

Mistake 2: Assuming seeded or free rights are enough for a production workflow

They are often not enough once premium connectors, sharing, or desktop RPA enter the picture.

Mistake 3: Designing unattended automation before validating the capacity model

That usually creates rework later.

Mistake 4: Ignoring the link between Process licensing and solution-aware cloud flows

This detail can matter operationally.

Mistake 5: Choosing only on sticker price instead of ownership model

The cheapest-looking license is not always the right runtime design.

Final checklist

Before finalizing Power Automate licensing, ask:

1. Is this mainly a user-owned workflow or an automation-owned workflow?
2. Will the process rely on premium connectors or custom connectors?
3. Is the desktop automation attended or unattended?
4. Does the flow need its own capacity at scale?
5. Will the automation be built and assigned inside a solution?
6. Who needs rights to build, run, monitor, and support it?

If those answers are clear, the licensing choice becomes much easier.

FAQ

What is the difference between user and capacity licensing in Power Automate?

User licenses are assigned to people and give them rights to use Power Automate capabilities. Capacity licenses are assigned to automations such as cloud flows or machines and provide automation-level entitlements.

When does a team need Power Automate Premium?

A team usually needs Power Automate Premium when users need full cloud automation, premium connectors, or attended desktop RPA capabilities beyond the limited free or seeded rights.

When does a team need a Process license?

A team usually needs a Process license when it wants unattended desktop automation on a machine or wants to license a cloud flow at the automation level with higher action capacity and premium connector access.

What is the biggest licensing mistake teams make?

The biggest mistake is treating licensing as a procurement detail instead of a design constraint. In Power Automate, licensing changes who can build, run, trigger, monitor, and scale the automation.

Final thoughts

Power Automate licensing gets much easier once you stop thinking in terms of plans alone and start thinking in terms of runtime ownership.

The right license is the one that matches how the automation is actually supposed to behave in production.