Calculating Power Automate cost for 1,500 monthly runs
By Jordan Ellis Updated 10 min read
As an Amazon Associate I earn from qualifying purchases. That costs you nothing and does not decide what gets recommended. We also earn a commission from some links to partner brands (SentryPC, HappyScribe, Sucuri, IceVPN).
On this page (9 sections)
- The short version
- How Microsoft Power Automate licensing and runs work (concise)
- How run counts scale when processing multiple items (consolidated explanation)
- Official pricing references (must-read)
- Explicit cost summary for 1,500 runs/month using official plan pricing (USD examples)
- Concrete example calculations (USD): compare Per User vs Per Flow
- When pay-as-you-go/consumption might apply and what to check
- Practical recommendations for your 1,500 runs/month scenario
- Questions people still ask
In short: Short answer: For 1,500 runs per month, a single user on the Per User plan at $15/user/month will typically cover that workload; the Per Flow option at $100/flow/month can be better when many unlicensed users run the same flow.
Part of our guide on selecting appropriate plan
Measure your flows (triggers + actions + loop iterations), then compare the Per User vs Per Flow math using the official Microsoft pricing pages linked above to pick the least-cost license for 1,500 runs/month.
| Monthly runs | 1,500 runs (target) |
|---|---|
| Daily flows | Scenario: up to 5 daily flows (constraint) |
| Premium connectors | 3 premium connectors required |
| Primary license options | Per User plan or Per Flow plan (official pricing referenced) |
| Official pricing sources | Microsoft Power Automate pricing pages (links in body) |
The short version
- Runs are counted per trigger and per action; loops and multiple actions per item increase run counts quickly.
- The Per User plan provides access to premium connectors and is commonly priced at $15/user/month (see Microsoft pricing links below).
- The Per Flow plan is priced per flow/month and can be cost-effective when many users share the same automated flows (see Microsoft pricing links below).
- For 1,500 runs/month you can estimate cost by comparing the Per User cost per active user vs Per Flow cost per shared flow; examples are provided.
- Always confirm current prices on Microsoft’s official pricing pages because rates and licensing details change.
How Microsoft Power Automate licensing and runs work (concise)
Microsoft’s primary licensing choices relevant to premium connectors and run volume are the Per User plan and the Per Flow plan. Both provide access to premium connectors, but they are priced differently and suit different usage patterns. Microsoft also offers a pay-as-you-go (consumption) option for some scenarios. See Microsoft’s official pricing pages for the current, authoritative rates (links provided below).
A 'run' is an execution of a flow. Practically, a run includes the trigger plus the actions executed for that trigger. If your flow processes multiple items in a loop, each processed item typically results in additional action counts during that single flow execution: therefore, total run accounting depends on how many triggers and actions (including loop iterations) your flows produce.
Microsoft’s public pricing pages describe plan names, per-user and per-flow prices, and guidance about connector access; they do not define a simple fixed ‘included runs’ bucket that applies in all cases. When people say a plan has 'unlimited runs' it is shorthand for that plan providing flow execution access without a documented per-month run cap on the pricing page: however Microsoft’s documentation and service limits, throttling and consumption policies still apply. Do not treat 'unlimited' as an unconditional guarantee; refer to Microsoft’s capacity and licensing documentation for operational limits and throttling behavior.
How run counts scale when processing multiple items (consolidated explanation)
Count runs by accounting for the trigger and each action executed. If a flow triggers once and then iterates over 50 items in an 'Apply to each' loop, the trigger counts as one run execution and each action inside that loop executes for each item: so total action executions scale by the item count. This is why processing N items in a loop typically multiplies the effective action executions by N. There is more on automate tasks with power automate in a separate guide.
Do not assume a 1:1 relationship between flow executions and overall runs when processing batches. The important measurement for billing and capacity planning is the total number of triggers plus total action executions (including repeated actions from loops).
When planning for 1,500 runs/month, measure your flows in a test window (for example a typical day) and multiply that measured daily consumption by the number of days in your billing month. This gives a practical estimate of monthly run consumption without inventing fixed multipliers.
Official pricing references (must-read)
Microsoft maintains current pricing and plan details on its official pages. Check these pages for the most up-to-date prices and plan wording: There is more on how to get microsoft office cheaply in a separate guide.
1) Microsoft Power Automate pricing page: https://flow.microsoft.com/pricing/ (this page lists Per User and Per Flow plan labels and example prices)
2) Microsoft Power Platform and Power Automate licensing documentation: https://learn.microsoft.com/power-platform/admin/pricing-billing (this is Microsoft’s documentation hub for licensing and billing details)
Because Microsoft updates pricing and plan features from time to time, use those pages to confirm current per-user and per-flow prices and any regional pricing or taxes that may apply. We cover understanding zapier task pricing in its own article.
Explicit cost summary for 1,500 runs/month using official plan pricing (USD examples)
Below are concrete, example calculations using the publicly listed plan price points on Microsoft’s pricing page as of the date you check the links above. The figures below are examples using commonly posted list prices (USD): always verify on Microsoft’s pricing pages for your billing region and currency.
Common list prices used in many Microsoft materials and reseller pages (examples; confirm on the official page):
– Per User plan: commonly shown at approximately $15/user/month (this plan provides access to premium connectors for that licensed user). The other half of this decision is how much does zapier cost per month.
– Per User plan with attended RPA: listed at a higher list price (examples commonly show $40/user/month for the enhanced RPA-enabled user plan).
– Per Flow plan: commonly shown at approximately $100/flow/month (this licenses a flow to be run by multiple users).
Using those representative prices, here are direct cost comparisons for the 1,500 runs/month target and the scenario of 3 premium connectors:
Concrete example calculations (USD): compare Per User vs Per Flow
Example A – Per User plan (single named user executes flows): If one person runs roughly 1,500 runs/month, licensing that person with the Per User plan at $15/user/month covers premium connector access for their flows. The straightforward monthly cost for that single-user scenario is $15 (plus local taxes or currency adjustments). This assumes all premium-workload runs are executed by the licensed named user and that no additional premium features such as attended RPA are required.
If your activity is shared across multiple creators or executors, multiply the per-user price by the number of licensed users who need premium access. For example, 3 users × $15 = $45/month. That still treats runs as unlimited for licensed users within Microsoft’s operational limits (service throttles and concurrency caps may still apply), so 1,500 total runs split between those three users would not add a run-based charge under the Per User licensing itself.
Example B – Per Flow plan (license a flow to be used by many users): The Per Flow option is priced per flow at $100/flow/month on Microsoft’s public list prices. License one flow and any number of users (within allowed usage patterns) can trigger it; license three flows and multiply accordingly. A Per Flow approach becomes attractive when a single automated process is executed by many unlicensed users or by systems where licensing each human user would be more expensive than licensing the central flow.
How these examples relate to 1,500 runs and a simple decision sequence: (1) If one named person performs nearly all runs, choose Per User at $15/user/month – cost $15/month. (2) If several named users each need to author/run premium flows, license each user (e.g., 3 users → $45/month). (3) If many unlicensed users or system accounts invoke the same automated process frequently, consider Per Flow at $100/flow/month per flow and compare total monthly cost to the sum of Per User licenses.
When pay-as-you-go/consumption might apply and what to check
Microsoft documents consumption and capacity guidance that can result in additional charges or throttling if flows generate high volumes or exceed practical service quotas. If your flows generate a burst of runs that goes beyond your normal pattern, check Microsoft’s consumption guidance and analytics to see whether consumption billing or throttling rules apply.
If you expect that processing your items will produce retries or a high number of loop iterations, measure actual run behavior in a test run to better predict monthly costs and to decide between Per User licenses, Per Flow licenses, or other options.
For any official consumption pricing or partner offers, consult the Microsoft pricing pages and your reseller or Microsoft account representative.
Practical recommendations for your 1,500 runs/month scenario
1) Measure: Instrument your flows so you can report daily trigger counts and action executions; multiply daily counts by the days in your billing month to predict monthly runs.
2) Compare license math: If one or a few named users will perform the work, the Per User plan (example list price $15/user/month) is usually the straightforward purchase. If many users need to trigger the same flow and you want to centralize licensing, evaluate the Per Flow plan (example list price $100/flow/month) and compare total cost.
3) Optimize flows: Reduce unnecessary actions, batch items where appropriate, and minimize loop iterations that multiply action counts.
4) Validate official pricing: Before purchasing, confirm current list prices and any regional differences on Microsoft’s pricing pages linked earlier and contact your Microsoft sales representative if you have a complex scenario.
For 1,500 runs/month with 3 premium connectors, a Per User plan (example list price: $15/user/month) is typically the simplest and lowest-cost approach if a single or a small number of licensed users run the flows. If you need flows shared across many users, evaluate the Per Flow plan (example list price: $100/flow/month) and compare total costs using your measured run counts.
Questions people still ask
What exactly counts as a run in Power Automate?
A run equals a flow execution that includes the trigger and the actions executed for that trigger. Loop iterations cause repeated action executions; measure triggers + actions to estimate total run consumption.
Do premium connectors require paid plans?
Yes. Premium connectors require a paid Power Automate license (Per User or Per Flow) or a qualifying add-on. Microsoft’s pricing pages explain which connectors and plans apply.
How do I estimate runs for bulk invoice processing?
Measure a single, representative flow execution: count the trigger + actions executed for processing one invoice. Multiply that count by the number of invoices processed per run and by the number of flow executions per month to get a monthly run total.
Which plan is cheapest for 1,500 runs per month?
If one or a few licensed users perform all runs, the Per User plan (example list price $15/user/month) is typically the lowest-cost path. If many unlicensed users need to trigger the same flows frequently, the Per Flow plan could be more cost-effective. Always run the arithmetic using Microsoft’s current list prices and your measured run counts.
Where can I verify official pricing and licensing details?
Check Microsoft’s official pages: https://flow.microsoft.com/pricing/ and https://learn.microsoft.com/power-platform/admin/pricing-billing for current, authoritative pricing and licensing details.