A useful workflow can use several Microsoft tools and still fit within limited existing entitlements. Another workflow may need additional licensing because of one connector or the way people run it.

The starting question is not how complicated the flow looks. It is which systems it accesses, how it starts, who owns it, and who uses it.

Microsoft guidance reviewed September 4, 2026. Confirm the terms for the proposed design and your exact agreement before purchasing or deploying.

Inventory the workflow

Write down every trigger, action, connector, and connection account. Include a gateway, custom API, desktop application, or document-processing step if the design needs one.

Microsoft's licence-type overview distinguishes limited included rights, Premium user licensing, and Process capacity. An existing Microsoft 365 subscription should not be treated as blanket entitlement to all Power Automate features.

Check current connector classifications and intended use. A workaround that avoids one premium connector can still introduce costs, support problems, or licensing questions.

Check who runs it

Microsoft's Power Automate licensing FAQ makes several important distinctions:

  • Automated and scheduled flows use the owner's licensing context.
  • For a standalone instant flow using premium connectors, each invoker generally needs Premium unless the flow has suitable Process coverage.
  • A person who only responds to an approval does not need Premium solely for that response.
  • Flows used within a licensed Power Apps or Dynamics 365 application need the appropriate app association and context.

A shared account does not automatically license everyone who uses a process. Document the ownership arrangement and what happens when an employee leaves. Check the specific scenario rather than applying a rule from a superficially similar workflow.

Compare a user licence with process capacity

Premium is assigned to a user. Process capacity can be assigned to eligible flows or machines, with requirements that depend on the design. Hosted Process adds Microsoft-hosted machine capacity.

Use those distinctions to examine the proposed operation: who invokes it, whether it needs unattended desktop automation, and how it will be maintained. Confirm allocation rules and necessary builder or administrator entitlements. A headline monthly price is not enough information to choose a plan.

Treat AI Builder as a separate check

AI Builder introduces usage capacity as well as a potential licensing dependency. Current Microsoft documentation is inconsistent on whether adding an AI Builder action alone makes a Power Automate flow premium: the licensing overview says it does, while the credit-management page says it does not.

Do not budget on an assumption that Premium is unnecessary. Confirm both the flow entitlement and available AI Builder or Copilot Credits with Microsoft or your licensing provider for the exact design.

Those pages also describe changes to seeded AI Builder credits in November 2026. A design relying on included credits needs a current check of its continuing entitlement and usage costs.

Put the answer into the project scope

Before building, record the proposed licences, owner, users, connector tiers, expected usage, and unresolved questions. Keep that record with the solution's operating documentation and revisit it when the design changes.

For examples of what to map, see five workflow patterns.

An initial 30-minute consultation is free and can help establish whether further work makes sense. Detailed investigation, analysis, and implementation are paid follow-on services, with scope and fees agreed before work starts.