Limits and configuration in Power Automate
This topic contains information about the current limits and configuration details for flows.
Check out the pricing for details on the different plans that are available.
These are limits for a single outgoing request.
|Request Timeout for synchronous calls||120 Seconds|
|Request Timeout for Async calls||Configurable. Max is 30 days.|
If you test a flow that runs for longer than 10 minutes, you may get a timeout message in Power Automate, even though the flow continues to run in the background. If this happens, reopen the view to receive the current status.
|Message size||100 MB||Not all APIs support the full 100MB.|
|Expression evaluation limit||131,072 characters||
|Retry attempts||90||The default is 2. To change the default, use action settings.|
|Retry max delay||1 day|
|Retry min delay||5 seconds|
Run duration and retention
These are the limits for a single flow run.
|Run duration||30 days||Includes workflows with pending steps like approvals. After 30 days, any pending steps time-out.|
|Storage retention||30 days||This is from the run start time.|
|Min recurrence interval||1 minute|
|Max recurrence interval||500 days|
|Max run history retention||28 days, per GDPR rules.|
|Minimum postpone interval - Free and Plan 1 license||5 seconds|
|Minimum postpone interval - Plan 2 license||1 second|
Individual connectors may have their own limits as well.
Looping and debatching limits
These are limits for a single flow run. For daily limits, refer to the requests limits and allocations.
|Apply to each items - Office 365 and Free licenses||5,000||You can use the filter action to filter larger arrays as needed.|
|Apply to each items - Plan 1, Plan 2, Per User, and Per Flow licenses||100,000||You can use the filter action to filter larger arrays as needed.|
|SplitOn items - Office 365 and Free licenses||5,000|
|SplitOn items - Plan 1, Plan 2, Per User, and Per Flow licenses||100,000|
|Apply to each Parallelism||50||By default, loops run in sequence (essentially, parallelism is 1). You can configure up to 50 in parallel.|
|Actions executions per 5 minutes – Free, Office365, Plan 1 licenses, and trials||2,000||Also, you can distribute a workload across more than one flow as needed.|
|Actions executions per 5 minutes – Paid Plan 2, Per User, and Per Flow licenses||100,000||Also, you can distribute a workload across more than one flow as needed.|
|Actions concurrent outgoing calls – Free, Office 365, Plan 1 licenses and trials||~500||Reduce the number of concurrent requests or reduce the duration as needed.|
|Actions concurrent outgoing calls – Plan 2, Per User, and Per Flow licenses||~2,500||Reduce the number of concurrent requests or reduce the duration as needed.|
|Runtime endpoint - Number of read calls allowed per 5 minutes – Free, Office 365, Plan 1 licenses and trials||6,000|
|Runtime endpoint - Number of read calls allowed per 5 minutes – Paid Plan 2, Per User, and Per Flow licenses||60,000|
|Runtime endpoint: Invoke calls per 5 minutes – Free, Office 365, Plan 1 licenses and trials||4,500|
|Runtime endpoint: Number of invoke calls per 5 minutes – Paid Plan 2, Per User, and Per Flow licenses||45,000|
|Amount of throughput allowed per 5 minutes – Free, Office 365, Plan 1 licenses and trials||600 MB|
|Amount of throughput allowed per 5 minutes – Paid Plan 2, Per User, and Per Flow licenses||6 GB|
|Amount of content flows are allowed to produce (actions inputs/outputs) per hour - Free, Office 365, Plan 1, Plan 2, Per User, and Per Flow licenses||200 GB|
These are limits for flows.
|Actions per workflow||500||You can add nested workflows to extend this as needed.|
|Allowed action nesting depth||8||You can add nested workflows to extend this as needed.|
|Max characters per expression||8,192|
|Solution-agnostic flows per user||600|
There are limitations on how you can use Microsoft SharePoint with Power Automate and Power Apps.
IP address configuration
The IP address from which Power Automate requests are sent depends on the region where the environment that contains the flow is located. We don't currently publish FQDNs available for flow scenarios.
Some calls a flow makes may come from IP addresses that are listed in the Logic apps documentation. Some examples of these calls include HTTP or HTTP + OpenAPI.
Calls made from a flow go directly through the Azure Logic App service. Some examples of these calls include HTTP or HTTP + OpenAPI. Please reference the Logic apps documentation for which IP addresses are used by that service.
Calls made from a connector in a flow (for example, the SQL API or the SharePoint API) will come from the IP addresses listed here:
|Asia Pacific||188.8.131.52 - 184.108.40.206, 220.127.116.11 - 18.104.22.168, 22.214.171.124, 126.96.36.199|
|Australia||188.8.131.52 - 184.108.40.206, 220.127.116.11, 18.104.22.168 - 22.214.171.124, 126.96.36.199|
|Canada||188.8.131.52 - 184.108.40.206, 220.127.116.11 - 18.104.22.168, 22.214.171.124, 126.96.36.199 - 188.8.131.52, 184.108.40.206|
|Europe||220.127.116.11 - 18.104.22.168, 22.214.171.124, 126.96.36.199 - 188.8.131.52, 184.108.40.206, 220.127.116.11|
|India||18.104.22.168 - 22.214.171.124, 126.96.36.199, 188.8.131.52 - 184.108.40.206, 220.127.116.11, 18.104.22.168 - 22.214.171.124, 126.96.36.199|
|Japan||188.8.131.52 - 184.108.40.206, 220.127.116.11, 18.104.22.168 - 22.214.171.124, 126.96.36.199|
|South America||188.8.131.52 - 184.108.40.206, 220.127.116.11 - 18.104.22.168, 22.214.171.124, 126.96.36.199|
|United Arab Emirates||188.8.131.52 - 184.108.40.206, 220.127.116.11 - 18.104.22.168, 22.214.171.124|
|United Kingdom||126.96.36.199 - 188.8.131.52, 184.108.40.206, 220.127.116.11 - 18.104.22.168, 22.214.171.124|
|United States||126.96.36.199 - 188.8.131.52, 184.108.40.206, 220.127.116.11 - 18.104.22.168, 22.214.171.124, 126.96.36.199 - 188.8.131.52, 184.108.40.206, 220.127.116.11 - 18.104.22.168, 22.214.171.124, 126.96.36.199 - 188.8.131.52, 184.108.40.206|
|Preview (United States)||220.127.116.11 - 18.104.22.168, 22.214.171.124, 126.96.36.199 - 188.8.131.52, 184.108.40.206|
For example, if you must authorize IP addresses for your Azure SQL database, you should use these addresses.
The following table lists the services to which Power Automate connects. Ensure none of these services are blocked on your network.
|management.azure.com||https||Access to the Azure Resource Manager.|
|login.microsoft.comlogin.windows.netlogin.microsoftonline.comsecure.aadcdn.microsoftonline-p.com||https||Access to Active Directory Authentication Library (ADAL).|
|graph.microsoft.com graph.windows.net||https||Access to Azure AD Graph API - for getting user information such as a profile photo.|
|*.azure-apim.net||https||Access to the Runtime for Connectors.|
|*.flow.microsoft.com||https||Access to the Power Automate site.|
|*.powerapps.com||https||Access to the Power Apps site.|
|*.azureedge.net||https||Access to the Power Automate CDN.|
|nps.onyx.azure.net||https||Access to NPS (Net Promoter Score).|
|webshell.suite.office.com||https||Access to Office for header and search. Please see the Office 365 urls and ranges for more details|
Approval email delivery
Please see the approvals email delivery article for details about approvals email routing.
UI flows required services
The following table lists endpoint data requirements for connectivity from a user's machine for a successful UI flows installation and runs.
|http||Access to the CRL server for the public cloud.|
|U.S. Government GCC and GCC High endpoints||ocsp.digicert.com
|http||Access to the CRL server for US government cloud.|
|21Vianet operated endpoints||crl.digicert.cn
|http||Access to the CRL servers for 21Vianet operated cloud.|
|https||Access to UI Flows WebDriver downloaders.|