Skip to content
Tutorials Center
My learning

Topics

Lesson 35 of 38 ยท Governance and Patterns

Limits, Licensing and Performance

Plan flows that fit the platform: run duration, action and request limits, throttling, standard versus premium connectors, license types, and practical tips for faster, cheaper flows.

Every automation platform has limits, and Power Automate's are generous but real: how long a run may last, how many actions per day your license includes, how much data an action may handle. Knowing them before you design avoids the unpleasant surprise of a flow that works with ten test items and fails with ten thousand. This lesson explains the kinds of limits, how licensing is structured, and what you can do to make flows faster and cheaper.

Numbers and plan names change. The figures here are typical values given as orientation. Before you commit to a design, check Microsoft's current pages: "Limits and configuration" and "Power Platform licensing guide".

The examples are JavaScript stand-ins with made-up numbers, because licensing and quotas cannot be demonstrated on this site.

The kinds of limits

Kind Typical behavior
Run duration A cloud flow run can last at most 30 days. Longer waits fail with a timeout
Action duration A single action has its own limit (HTTP calls about two minutes synchronously)
Actions per run / nesting A flow definition may contain up to about 500 actions in the designer, with limited nesting depth of branches and scopes. Large flows should be split into child flows
Loop size Apply to each processes up to a plan-dependent number of items (from thousands to 100,000)
Message and payload size Actions have size limits for the data they handle (for example a few MB per message and larger for files); connectors differ
Concurrency Parallel iterations and parallel runs are capped (loops up to 50 parallel iterations)
Requests per 24 hours Each license gives a daily quota of Power Platform requests: roughly every action in a flow counts as one request
Connector throttling Each connector limits calls per connection per minute, independent of your license
Run history retention Run details are kept for 28 days
Recurrence frequency The minimum interval of a recurrence trigger depends on the plan (often one minute for premium plans, longer for low plans)

When a limit is hit you see an error (often 429 or a message about request limits), or the flow becomes slow (it is deliberately slowed when a user exceeds the daily request limit).

What counts as a request

In general, every action execution counts, including actions inside loops, trigger checks that find something, and Apply to each iterations. A loop over 1,000 items with three actions per item produces about 3,000 requests. This is why loop-free alternatives and filtering on the server matter for cost as well as for speed.

JS Stand-in: estimating daily requests

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Connectors: standard, premium, custom

Connectors are classified:

  • Standard: included with Microsoft 365 licenses: SharePoint, Outlook, Teams, OneDrive, Planner, Excel Online and many more.
  • Premium: need a Power Automate license (for example HTTP, SQL Server, Dataverse in many cases, Azure services, many third-party systems).
  • Custom connectors: your own wrapper around an API; count as premium.
  • Desktop flows: running desktop flows from the cloud, and unattended RPA, need their own license components.

A single premium connector in a flow makes the flow premium: every user who runs or triggers it needs the right license. This is the most common licensing surprise: a flow built on "free" Microsoft 365 rights stops working after someone adds an HTTP action.

License types, in plain terms

Model Idea
Included with Microsoft 365 (seeded rights) Flows triggered by and acting on Microsoft 365 services, with standard connectors only
Per user plan A user can run unlimited flows (within request limits) using premium connectors; the user must be licensed
Per flow plan Licenses specific flows for use by anyone in the organization, for a few business-critical flows
Process / Hosted RPA / Unattended add-ons Capacity for desktop flows on machines (check current names and how many bots you need)
Pay-as-you-go Billed per run through an Azure subscription, useful for variable workloads

Which model is cheapest depends on the number of users and flows. Ask your admin or license partner, and read the licensing guide; this lesson cannot decide it for you.

JS Stand-in: per-user versus per-flow break-even

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Making flows faster

  1. Filter early and on the server with OData queries, Top Count and selected columns.
  2. Replace loops with Filter array, Select, Join and expressions.
  3. Run independent actions in parallel branches, and use limited concurrency in loops for independent work.
  4. Avoid unnecessary Gets. If a trigger already returned the fields you need, do not fetch them again. Use "Get changes" or trigger outputs.
  5. Choose triggers wisely: push triggers (webhooks, "When an item is created") fire immediately; polling triggers check on a schedule and count runs. Add trigger conditions to skip useless runs.
  6. Use batch operations where available (for example Dataverse "Add multiple rows", or SQL queries that handle many rows at once).
  7. Do heavy transformations outside the flow: a SQL query, an Azure Function or an Office Script is faster than a thousand-step loop.
  8. Cache lookups: read reference data once at the start, not once per item.
  9. Avoid long polling loops: use webhooks or wait actions designed for the job.

Making flows cheaper and safer to run

  • Turn off or delete unused flows; a forgotten recurrence flow still burns requests.
  • Lower the frequency of recurrence triggers.
  • Do not run production flows from personal accounts: use service accounts or service principals, with the right license assigned.
  • Monitor request consumption in the admin center and set alerts when a flow approaches its limits.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. A loop over 500 items with 2 actions per item adds roughly how many requests per run?

    Actions inside loops are counted per iteration.
  2. 2. A flow built with only standard connectors gets an HTTP action added. What is the likely licensing impact?

    One premium connector makes the flow premium.
  3. 3. What is the maximum duration of a single cloud flow run?

    Runs that exceed 30 days time out.
  4. 4. Which change most reduces both run time and request use for a flow that loops over an entire list testing one field?

    Fetching and processing fewer items saves time and requests.

Summary

  • Limits cover run and action duration, loop size, payloads, concurrency, daily requests, throttling and history retention; check the current official numbers.
  • Every action execution counts as a request, including actions in loops.
  • Premium or custom connectors make a flow premium; choose between included rights, per user, per flow, pay-as-you-go and desktop add-ons by the numbers.
  • Speed and cost improve together: filter early, avoid loops, use parallelism with care and move heavy work out of the flow.

Next: Project: An Expense Approval Process