Skip to main content

Buyer guide

Power Automate Licensing & Capacity Checklist

Pick the license each flow runs under, from Microsoft 365 rights, Premium, Process, flow groups, and pay-as-you-go, and check it against request limits.

Reading time
3 min read
Sources
17 cited
In this piece
Power Automate−6 Mixed

License each flow by its connectors and how often it runs. Microsoft 365 rights cover standard connectors, Premium covers the people who build premium flows, Process covers a busy flow or bot, and pay-as-you-go covers occasional runs. Agent flows and AI steps bill Copilot Credits on top.

When you need this

  • A flow needs a premium or custom connector, or must run unattended on a desktop.
  • A flow is throttled, or is owned by a service principal or a shared account.
  • Teams add AI Builder steps or agent flows, which draw Copilot Credits.

Evaluation criteria

  1. Standard connectors first

    Does the flow use only standard connectors?

    Look forUse Microsoft 365 rights for standard connectors, with 6,000 Power Platform requests per user a day. A free Power Automate license also lets work or school accounts build and run standard-connector cloud flows, though they cannot share them. Check each action, because one premium action changes the license. One small organization found that its reminder flows and Word templates needed Premium.

  2. Premium per maker

    Who builds premium, custom-connector, or attended desktop flows?

    Look forPremium costs US$15 per user per month, paid yearly. It includes premium and custom connectors, one attended bot, process mining with 50 MB per license, and a daily limit of 40,000 Power Platform requests for each user. Instant flows use the triggering user's license. One organization with 1,000 users faced Premium licenses for everyone triggering a flow with one premium HTTP connector.

  3. Process per core process

    Does a core process need its own capacity, unattended bots, or independence from any one user?

    Look forAssign a Process license, US$150 a month on a yearly plan, to a solution-aware flow or a machine. Each license provides 250,000 actions a day. Stack up to 10 licenses on one flow or share one across a flow group of up to 25 flows. One consultant set up groups for a client running 400,000 actions a day across about 50 flows.

  4. Pay-as-you-go for occasional runs

    Do premium flows run rarely or unpredictably?

    Look forLink a pay-as-you-go environment to Azure. Premium cloud or attended runs cost US$0.60 each. Unattended runs cost US$3.00. Standard-connector flows are free, as are designer tests and resubmitted failed runs. Keep Process-licensed flows in another environment. Microsoft ignores Process licenses in pay-as-you-go environments.

  5. Service accounts and multiplexing

    Does one licensed account run flows on behalf of many users?

    Look forEach person who triggers a premium flow through a shared service account still needs their own license, unless the flow has a Process license; people who only receive its output do not. A maker syncing a database into SharePoint for several apps found that their service-account setup would breach Microsoft's multiplexing rules. Premium flows owned by a service principal need Process, a flow group, or a designated licensed user.

  6. Request limits

    Which flows run near their daily action limits?

    Look forDuring its current transition period, Microsoft applies Premium limits per flow at 200,000 requests a day. After it, the per-user Premium limit applies. Microsoft says it will start enforcing the per-user limits no sooner than six months after Power Automate usage reporting reaches general availability. Find the flows and users over their official limits now under Licensing, Power Automate, Usage in the Power Platform admin center, and give them a Process license or a flow group. Power Automate turns off a flow that is throttled consistently for 14 days.

  7. AI and agent credits

    Which flows call AI Builder or run as agent flows?

    Look forBudget Copilot Credits at US$0.01 each on pay-as-you-go. Agent flows use 13 per 100 actions. Document processing uses 8 per page. Prompts use 0.1 to 10 per 1,000 tokens, depending on model tier. Licenses bought or renewed from November 1, 2026 include no seeded AI Builder credits.

Questions to ask vendors

  1. Which of our flows use premium connectors, and whose license does each run under?
  2. Do we still renew per-flow plans, which Microsoft replaced with Process?
  3. Which processes would share a flow group, and are all their child flows in it?
  4. Who watches Copilot Credit use by AI Builder steps and agent flows?

Red flags

  • One licensed service account running premium flows for a whole department.
  • Pay-as-you-go turned on in an environment whose flows hold Process licenses.
  • A parent flow in a flow group with its child flows left out.
  • AI Builder steps running on seeded credits with no plan for the next renewal.

Products in this piece

Sources

Official documentation
10
Public source
7
  1. Microsoft Power Automate pricingOfficial documentationmicrosoft.com
  2. Microsoft Learn: Types of Power Automate licensesOfficial documentationlearn.microsoft.com
  3. Microsoft Learn: Power Automate licensing FAQOfficial documentationlearn.microsoft.com
  4. Microsoft Learn: Requests limits and allocationsOfficial documentationlearn.microsoft.com
  5. Microsoft Learn: Pay-as-you-go metersOfficial documentationlearn.microsoft.com
  6. Microsoft Learn: Limits of automated, scheduled, and instant flowsOfficial documentationlearn.microsoft.com
  7. Microsoft Learn: Support for service principal owned flowsOfficial documentationlearn.microsoft.com
  8. Microsoft Learn: AI Builder licensing overviewOfficial documentationlearn.microsoft.com
  9. Microsoft Learn: AI Builder licensing and Copilot CreditsOfficial documentationlearn.microsoft.com
  10. Microsoft Learn: Copilot Studio billing rates and managementOfficial documentationlearn.microsoft.com
  11. Reddit r/PowerAutomate: Premium licenses or a Process license? (Aug 12, 2025)Public sourcereddit.com
  12. Reddit r/PowerAutomate: flow groups for a client running about 50 flows (Aug 15, 2026)Public sourcereddit.com
  13. Reddit r/sysadmin: Power Automate licensing seen through an RPA trial (Jan 2, 2026)Public sourcereddit.com
  14. Reddit r/MicrosoftFlow: Did Microsoft move most of Power Automate behind a paywall? (Jan 11, 2026)Public sourcereddit.com
  15. Power Platform Community: the premium HTTP connector for 1,000 users (Nov 26, 2025)Public sourcecommunity.powerplatform.com
  16. Reddit r/MicrosoftFlow: a desktop flow built in hours, then a second license to run it unattended (May 12, 2025)Public sourcereddit.com
  17. Reddit r/PowerAutomate: AI Builder under Copilot Credit licensing (Dec 2, 2025)Public sourcereddit.com

Keep reading

  1. Buyer guidePower Automate Rollout PlaybookThe environments, ownership rules, review practice, and licensing to settle before business teams build flows that others depend on.
  2. Buyer guidePower Automate Admin, Data & Copilot Controls ChecklistData policies, Managed Environments, ownership, run history, regions, and the Copilot settings to review before flows touch sensitive data.
  3. Buyer guidePower Automate Agent Flows, Copilot & RPA GuideUse a cloud flow for triggers and schedules, an agent flow or Copilot Studio workflow when an agent calls it, and a desktop flow for screens with no API. Each bills differently.
Read the research