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

Power Automate per user plan is a Commercial, per-user purchasing option for Microsoft Power Automate, because the source pack lists the product as available in the Commercial segment with a per-user plan title. The source pack confirms monthly and annual purchasing options, but it does not include the detailed Microsoft entitlement map for flows, connectors, desktop automation, AI Builder, Dataverse, or capacity.

Commercial customers can choose a monthly commitment with monthly billing or an annual commitment with either annual or monthly billing, because those are the options listed in the source pack. The source pack shows the current catalog entries as unchanged, but it does not provide any future price guarantee.

No trial SKU is listed for this product in the source pack, because every Commercial catalog entry is marked as a paid, non-trial option. If you need to evaluate the plan before purchase, confirm with IT Partner whether Microsoft has any separate trial, evaluation, or tenant-level option available outside this SKU listing.

The source pack confirms Commercial availability, per-user purchasing, and monthly or annual commitment options, because those details are explicitly listed for SKU CFQ7TTC0LH3L. It does not confirm the detailed feature entitlements, so connector rights, cloud-flow limits, desktop-flow rights, AI Builder, Dataverse, and capacity should be verified before deployment.

Do not assume premium connector coverage from the source pack alone, because the source pack does not list standard or premium connector entitlements. Before buying for a connector-specific scenario such as Salesforce, SQL, ServiceNow, SAP, or an on-premises data gateway workflow, confirm the current Microsoft entitlement mapping for this SKU with IT Partner.

Possibly, but it should not be positioned as an RPA solution until entitlements are confirmed, because the source pack does not state whether attended desktop flow rights are included. Unattended automation, bot capacity, and process-wide automation often have separate licensing considerations, so those scenarios should be reviewed before purchase.

The source pack does not confirm AI Builder credits or Dataverse seeded capacity, so you should not assume either is included for your scenario. If your automation uses document processing, predictions, generative AI features, Dataverse tables, or high-volume environments, confirm whether separate capacity or add-ons are required.

Power Automate can commonly be used with Teams-based workflows, but the source pack does not define the Teams-specific entitlements for this SKU. Users may still need the appropriate Microsoft Teams and Microsoft 365 licenses for the services they access, because Power Automate licensing does not automatically license every connected Microsoft service.

The source pack does not state any Copilot entitlement, because it only lists the Power Automate per user plan purchasing options and not detailed feature rights. If your rollout depends on Copilot-assisted flow creation or other AI capabilities, confirm the required Power Automate, Microsoft 365, Copilot, and AI Builder licensing before scoping the project.

Yes, connected-service licensing must be validated separately, because a Power Automate license does not automatically grant rights to Microsoft 365, Dynamics 365, Power Apps, third-party applications, databases, or line-of-business systems. For example, a user or service account may need separate rights to the mailbox, data source, CRM system, or API that the flow reads or updates.

A per-user plan is normally assigned to named users who create, own, or run covered automations, because the product is listed as a per-user plan. The exact create, own, run, and sharing rights for this SKU should be verified before rollout, especially when flows are triggered by many users, service accounts, shared mailboxes, or application identities.

Yes, Power Automate services are subject to Microsoft service limits and capacity rules, but the source pack does not list those limits for this SKU. If you expect high flow run volume, frequent API calls, large file processing, many environments, or business-critical automation, confirm current limits and whether extra capacity or a different licensing model is needed.

Security is managed through Microsoft tenant controls such as identity, environment permissions, connector governance, and data loss prevention policies, because Power Automate runs inside the Microsoft cloud tenant governance model. The license purchase alone does not design those controls, so administrators should review environments, DLP policies, connector approvals, and access roles before enabling broad automation.

A Commercial buyer should verify the Microsoft cloud region, connector behavior, data movement, retention, and compliance requirements for each automation, because the source pack does not include compliance or residency commitments for this SKU. Flows can move data across connected services, so regulated workloads should be reviewed against Microsoft documentation, tenant configuration, and the customer’s compliance obligations.

Start by inventorying existing flows, owners, connectors, environments, run volumes, and any desktop automation, because those details determine whether the per-user plan is sufficient. Then assign licenses to the required users, validate connector and capacity rights, test in a controlled environment, and only then move production flows or ownership.

A CSP partner transfer or reseller relationship change is typically an administrative licensing and billing change, not a tenant data migration, so it should not interrupt existing flows when the same tenant, users, and subscriptions are maintained correctly. IT Partner should still review the current subscription term, renewal date, seat counts, and SKU mapping before the transfer to avoid accidental cancellation or entitlement gaps.

The underlying Microsoft catalog SKU and commitment structure can be matched when the same product, segment, term, and billing option are used, because CSP pricing is tied to the Microsoft catalog offering. The actual invoice can still depend on partner billing practices, promotions, taxes, fees, and any changes you make during the move, so confirm the quote before authorizing the transfer.

You can generally add seats during an active CSP subscription, because per-user cloud subscriptions are designed to support changing user counts. Reductions, cancellations, and refunds depend on the subscription term, billing cadence, Microsoft commerce rules, and timing, so confirm the specific change window with IT Partner before committing to an annual term.

At renewal, the subscription normally continues under the selected term and billing arrangement unless it is changed according to Microsoft commerce rules, because the source pack lists defined monthly and annual commitments. Cancellation flexibility is usually greater for monthly commitment than annual commitment, so review renewal date, auto-renew status, seat count, and cancellation windows before the next term starts.

This page is for the Commercial Power Automate per user plan, because the selected segment is Commercial even though the source pack also shows Charity, Education, and Government segments exist. Government customers should verify GCC versus GCC High availability and residency requirements; nonprofits should confirm charity eligibility and any grant context; and Education customers should confirm student, faculty, or staff licensing rules before using a non-Commercial offer.