Limits and configuration in Microsoft Flow
This topic contains information about the current limits and configuration details for flows.
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.|
|Message size||100 MB||Not all APIs support the full 100MB.|
|Expression evaluation limit||131,072 characters||
|Retry attempts||90||The default is 4. 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. Timed-out approvals are removed from the approvals center. If someone attempts to approve a timed-out request, they’ll receive an error message.|
|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|
Looping and debatching limits
These are limits for a single flow run.
|Apply to each items - Free license||5,000||You can use the filter action to filter larger arrays as needed.|
|Apply to each items - Plan 1 and Plan 2 license||100,000||You can use the filter action to filter larger arrays as needed.|
|SplitOn items - Free license||5,000|
|SplitOn items - Plan 1 and Plan 2 license||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 and Plan 1 license||2,000||Also, you can distribute a workload across more than one flow as needed.|
|Actions executions per 5 minutes - Plan 2 license||100,000||Also, you can distribute a workload across more than one flow as needed.|
|Actions concurrent outgoing calls - Free and Plan 1 license||~500||Reduce the number of concurrent requests or reduce the duration as needed.|
|Actions concurrent outgoing calls - Free and Plan 1 license||~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 and Plan 1 license||6,000|
|Runtime endpoint - Number of read calls allowed per 5 minutes - Plan 2 license||60,000|
|Runtime endpoint: Invoke calls per 5 minutes - Free and Plan 1 license||4,500|
|Runtime endpoint: Number of invoke calls per 5 minutes - Plan 2 license||45,000|
|Amount of throughput allowed per 5 minutes - Free and Plan 1 license||600 MB|
|Amount of throughput allowed per 5 minutes - Plan 2 license||6 GB|
|Amount of content flows are allowed to produce (actions inputs/outputs) per hour - Free, Plan 1 and Plan 2 license||200 GB|
These are limits for a single flow.
|Actions per workflow||250||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|
There are limitations on how you can use Microsoft SharePoint with Microsoft Flow and PowerApps.
IP address configuration
The IP address from which Microsoft Flow 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||18.104.22.168 - 22.214.171.124, 126.96.36.199 - 188.8.131.52, 184.108.40.206, 220.127.116.11|
|Australia||18.104.22.168 - 22.214.171.124, 126.96.36.199, 188.8.131.52 - 184.108.40.206, 220.127.116.11|
|Canada||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|
|Europe||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|
|India||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|
|Japan||18.104.22.168 - 22.214.171.124, 126.96.36.199, 188.8.131.52 - 184.108.40.206, 220.127.116.11|
|South America||18.104.22.168 - 22.214.171.124, 126.96.36.199 - 188.8.131.52, 184.108.40.206, 220.127.116.11|
|United Kingdom||18.104.22.168 - 22.214.171.124, 126.96.36.199, 188.8.131.52 - 184.108.40.206, 220.127.116.11|
|United States||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, 220.127.116.11, 18.104.22.168 - 22.214.171.124, 126.96.36.199|
|Preview (United States)||188.8.131.52 - 184.108.40.206, 220.127.116.11, 18.104.22.168 - 22.214.171.124, 126.96.36.199|
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 Microsoft Flow connects. Ensure none of these services are blocked on your network.
|management.azure.com||https||Access to the Azure Resource Manager.|
|https||Access to Active Directory Authentication Library (ADAL).|
|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 Microsoft Flow site.|
|*.powerapps.com||https||Access to the PowerApps site.|
|*.azureedge.net||https||Access to the Microsoft Flow CDN.|
|nps.onyx.azure.net||https||Access to NPS (Net Promoter Score).|