Power Automate per flow plan — Pricing, Plans & What's Included

Power Automate per flow plan is a flow-based Power Automate subscription for Commercial tenants, because it is intended to license a specific automation scenario rather than license every user with a per-user plan. Final fit depends on Microsoft’s current rules for the flow, users, connectors, environment, ownership model, and connected services.

Choose a per-flow approach when one centrally managed automation serves a defined business process, because licensing the flow can be more appropriate than licensing every person who benefits from that automation. If many users each build or run unrelated automations, a per-user or other Power Automate option may fit better and should be reviewed before purchase.

Power Automate per flow may support premium-connector scenarios when the flow and environment meet Microsoft’s current licensing requirements, because this plan is designed for licensed flow execution rather than basic Microsoft 365-only automation. However, connector-specific terms, connected-service licensing, API limits, and environment requirements can still apply, so IT Partner should validate the exact connectors before checkout.

Power Automate per flow plan is not a per-user Power Automate license, because it is assigned and evaluated around eligible flows rather than granting every user broad standalone automation rights. It also does not automatically cover every app, connector, service account, RPA scenario, AI Builder feature, Dataverse requirement, or separately licensed Microsoft service.

Yes, this SKU is subject to Microsoft’s current minimum purchase and assignment rules, because per-flow licensing has historically been governed differently from per-user licensing. Confirm the current requirement in the live CSP configurator and with IT Partner before buying, especially if you are licensing only one or a small number of flows.

Not automatically, because Microsoft’s current rules determine who can trigger, run, own, administer, or benefit from a licensed flow. A per-flow plan can be appropriate for organization-wide process automation, but the exact users, apps, service accounts, and connected systems should be reviewed against Microsoft’s current licensing terms.

Yes, a Teams-related flow may be eligible if the automation, connectors, and users satisfy Microsoft’s current Power Automate licensing rules, because Teams is often one of several services involved in a workflow. Teams licensing itself, premium connectors, Dataverse usage, or connected third-party services may still require separate licenses or validation.

No, you should not assume Microsoft 365 Copilot includes Power Automate per flow rights, because Copilot licensing and Power Automate standalone flow licensing are separate licensing areas. If the automation is created or invoked through Copilot, Copilot Studio, Teams, or another Microsoft app, validate the required Power Automate, connector, and service licenses before deployment.

Not by default for every scenario, because AI Builder capacity, desktop flow, unattended or attended RPA, and related add-ons have separate licensing rules that can change by use case. If the flow uses document processing, generative AI actions, UI automation, desktop automation, or bots, confirm the required add-ons and capacities with IT Partner.

Do not assume full Dataverse coverage, because Dataverse storage, tables, environments, apps, and capacity can require separate licensing or capacity depending on the scenario. If the flow reads from or writes to Dataverse, IT Partner should confirm whether the per-flow plan, environment, app licenses, and capacity are sufficient.

Possibly, but it must be validated, because Microsoft licensing, security, and operational guidance can treat service accounts, owners, makers, and run-only users differently. Before using a shared account or automation account, confirm the supported ownership model, required licenses, conditional access impact, and audit requirements.

Power Automate uses Microsoft cloud security, identity, and governance controls, because flows run within the Microsoft Power Platform and are governed through Microsoft Entra ID, environments, data loss prevention policies, connectors, and admin controls. Security still depends on tenant configuration, connector permissions, least-privilege design, and monitoring, so administrators should review policies before enabling business-critical flows.

Compliance depends on the tenant, environment region, connectors, and data path, because a flow can move data across multiple Microsoft and non-Microsoft services. Commercial buyers should verify Microsoft compliance documentation, Power Platform environment location, connector behavior, retention, audit, and any regulatory requirements before licensing or deploying sensitive workflows.

Start by identifying the exact flow or process to license, because per-flow licensing should be mapped to a specific automation scenario before purchase and assignment. IT Partner can help confirm term and billing choice, tenant eligibility, minimum requirements, assignment approach, connector dependencies, and whether the tenant shows this legacy plan name or an updated successor name in admin portals.

Often the flow design can remain, because licensing usually affects entitlement and assignment rather than requiring the logic to be rebuilt. However, you should test the flow after licensing changes, because connector permissions, owner accounts, environment policies, premium actions, and API limits can affect whether an existing automation runs as expected.

A CSP transfer is typically a billing and partner-of-record change rather than a data migration, because the Power Automate service, tenant, environments, and flows remain in Microsoft’s cloud tenant. IT Partner should coordinate the transfer timing and subscription mapping so service continuity is maintained and current Microsoft/CSP terms are confirmed.

Moving to IT Partner should not change the underlying Microsoft cloud service, because the subscription remains a Microsoft CSP subscription tied to the customer tenant. The final commercial terms still must be confirmed in the live configurator, because pricing can depend on term, billing frequency, promotions, taxes, currency, and tenant eligibility.

The rules depend on the selected commitment and Microsoft’s current CSP commerce policies, because month-to-month and annual commitments have different flexibility. In general, annual commitments are less flexible than month-to-month options, and reductions or cancellations may be limited outside Microsoft’s allowed cancellation window, so confirm renewal settings and quantity needs before checkout.

Not necessarily, because Microsoft separates Commercial, Charity, Education, and Government purchasing eligibility and catalogs. Nonprofits should check Charity eligibility and grant context, schools should distinguish student and faculty licensing needs, and government agencies should use the appropriate Government channel rather than assuming the Commercial SKU is the right offer.

A government organization should not default to the Commercial plan when it needs GCC, GCC High, or government-specific residency and compliance commitments, because those are separate Microsoft cloud and licensing contexts. Confirm the correct Government segment, tenant type, environment availability, residency requirements, and connector support with IT Partner before purchasing.