Limits and configuration information for Azure Logic Apps

This article describes the limits and configuration details for creating and running automated workflows with Azure Logic Apps. For Power Automate, see Limits and configuration in Power Automate.

Definition limits

Here are the limits for a single logic app definition:

Name Limit Notes
Actions per workflow 500 To extend this limit, you can add nested workflows as needed.
Allowed nesting depth for actions 8 To extend this limit, you can add nested workflows as needed.
Workflows per region per subscription 1,000
Triggers per workflow 10 When working in code view, not the designer
Switch scope cases limit 25
Variables per workflow 250
Characters per expression 8,192
Maximum size for trackedProperties 16,000 characters
Name for action or trigger 80 characters
Length of description 256 characters
Maximum parameters 50
Maximum outputs 10

Run duration and retention limits

Here are the limits for a single logic app run:

Name Multi-tenant limit Integration service environment limit Notes
Run duration 90 days 366 days Run duration is calculated by using a run's start time and the limit that's specified at start time by the workflow setting, Run history retention in days.

To change the default limit, which is 90 days, see change run duration.

Run retention in storage 90 days 366 days Run retention is calculated by using a run's start time and the limit that's specified at the current time by the workflow setting, Run history retention in days. Whether a run completes or times out, the retention calculation always uses the run's start time. When a run's duration exceeds the current retention limit, the run is removed from the runs history.

If you change this setting, the current limit is always used for calculating retention, no matter the previous limit. For example, if you reduce the retention limit from 90 days to 30 days, a run that's 60 days old is removed from the runs history. If you increase the retention period from 30 days to 60 days, a run that's 20 days old stays in the runs history for another 40 days.

To change the default limit, which is 90 days, see change run retention in storage.

Minimum recurrence interval 1 second 1 second
Maximum recurrence interval 500 days 500 days

Change run duration and run retention in storage

To change the default limit for run duration and run retention in storage, follow these steps. To increase the maximum limit, contact the Logic Apps team for help with your requirements.

Note

For logic apps in multi-tenant Azure, the 90-day default limit is the same as the maximum limit. You can only decrease this value. For logic apps in an integration service environment, you can decrease or increase the 90-day default limit.

  1. Go to the Azure portal. In the portal search box, find and select Logic apps.

  2. Select and then open your logic app in the Logic App Designer.

  3. On the logic app's menu, select Workflow settings.

  4. Under Runtime options, from the Run history retention in days list, select Custom.

  5. Drag the slider to change the number of days that you want.

  6. When you're done, on the Workflow settings toolbar, select Save.

Concurrency, looping, and debatching limits

Here are the limits for a single logic app run:

Name Limit Notes
Trigger concurrency - Unlimited when the concurrency control is turned off

- 25 is the default limit when the concurrency control is turned on, which you can't undo after you enable concurrency. You can change the default to a value between 1 and 50 inclusively.

This limit describes the highest number of logic app instances that can run at the same time, or in parallel.

Note: When concurrency is turned on, the SplitOn limit is reduced to 100 items for debatching arrays.

To change the default limit to a value between 1 and 50 inclusively, see Change trigger concurrency limit or Trigger instances sequentially.

Maximum waiting runs - Without concurrency, the minimum number of waiting runs is 1, while the maximum number is 50.

- With concurrency, the minimum number of waiting runs is 10 plus the number of concurrent runs (trigger concurrency). You can change the maximum number up to 100 inclusively.

This limit describes the highest number of logic app instances that can wait to run when your logic app is already running the maximum concurrent instances.

To change the default limit, see Change waiting runs limit.

Foreach array items 100,000 This limit describes the highest number of array items that a "for each" loop can process.

To filter larger arrays, you can use the query action.

Foreach concurrency 20 is the default limit when the concurrency control is turned off. You can change the default to a value between 1 and 50 inclusively. This limit is highest number of "for each" loop iterations that can run at the same time, or in parallel.

To change the default limit to a value between 1 and 50 inclusively, see Change "for each" concurrency limit or Run "for each" loops sequentially.

SplitOn items - 100,000 without trigger concurrency

- 100 with trigger concurrency

For triggers that return an array, you can specify an expression that uses a 'SplitOn' property that splits or debatches array items into multiple workflow instances for processing, rather than use a "Foreach" loop. This expression references the array to use for creating and running a workflow instance for each array item.

Note: When concurrency is turned on, the SplitOn limit is reduced to 100 items.

Until iterations - Default: 60

- Maximum: 5,000

Throughput limits

Here are the limits for a single logic app definition:

Multi-tenant Logic Apps service

Name Limit Notes
Action: Executions per 5 minutes 100,000 is the default limit, but 300,000 is the maximum limit. To change the default limit, see Run your logic app in "high throughput" mode, which is in preview. Or, you can distribute the workload across more than one logic app as necessary.
Action: Concurrent outgoing calls ~2,500 You can reduce the number of concurrent requests or reduce the duration as necessary.
Runtime endpoint: Concurrent incoming calls ~1,000 You can reduce the number of concurrent requests or reduce the duration as necessary.
Runtime endpoint: Read calls per 5 minutes 60,000 You can distribute workload across more than one app as necessary.
Runtime endpoint: Invoke calls per 5 minutes 45,000 You can distribute workload across more than one app as necessary.
Content throughput per 5 minutes 600 MB You can distribute workload across more than one app as necessary.

Integration service environment (ISE)

Here are the throughput limits for the Premium ISE SKU:

Name Limit Notes
Base unit execution limit System-throttled when infrastructure capacity reaches 80% Provides ~4,000 action executions per minute, which is ~160 million action executions per month
Scale unit execution limit System-throttled when infrastructure capacity reaches 80% Each scale unit can provide ~2,000 additional action executions per minute, which is ~80 million more action executions per month
Maximum scale units that you can add 10

To go above these limits in normal processing, or run load testing that might go above these limits, contact the Logic Apps team for help with your requirements.

Note

The Developer ISE SKU has no published limits, no capabilities for scaling up, and no service-level agreement (SLA). Use this SKU only for experimenting, development, and testing, not production or performance testing.

Gateway limits

Azure Logic Apps supports write operations, including inserts and updates, through the gateway. However, these operations have limits on their payload size.

HTTP limits

Here are the limits for a single outgoing or incoming HTTP call:

Timeout

Some connector operations make asynchronous calls or listen for webhook requests, so the timeout for these operations might be longer than these limits. For more information, see the technical details for the specific connector and also Workflow triggers and actions.

Name Multi-tenant limit Integration service environment limit Notes
Outbound request 120 seconds
(2 minutes)
240 seconds
(4 minutes)
Examples of outbound requests include calls made by HTTP triggers.

Tip: For longer running operations, use an asynchronous polling pattern or an until loop. To work around timeout limits when you call another logic app that has a callable endpoint, you can use the built-in Azure Logic Apps action instead, which you can find in the connector picker under Built-in.

Inbound request 120 seconds
(2 minutes)
240 seconds
(4 minutes)
Examples of inbound requests include calls received by request triggers and webhook triggers.

Note: For the original caller to get the response, all steps in the response must finish within the limit unless you call another logic app as a nested workflow. For more information, see Call, trigger, or nest logic apps.

Message size

Name Multi-tenant limit Integration service environment limit Notes
Message size 100 MB 200 MB To work around this limit, see Handle large messages with chunking. However, some connectors and APIs might not support chunking or even the default limit.

- Connectors such as AS2, X12, and EDIFACT have their own B2B message limits.
- ISE connectors use the ISE limit, not their non-ISE connector limits.

Message size with chunking 1 GB 5 GB This limit applies to actions that either natively support chunking or let you enable chunking in their runtime configuration.

If you're using an ISE, the Logic Apps engine supports this limit, but connectors have their own chunking limits up to the engine limit, for example, see the Azure Blob Storage connector's API reference. For more information about chunking, see Handle large messages with chunking.

Character limits

Name Notes
Expression evaluation limit 131,072 characters The @concat(), @base64(), @string() expressions can't be longer than this limit.
Request URL character limit 16,384 characters

Retry policy

Name Limit Notes
Retry attempts 90 The default is 4. To change the default, use the retry policy parameter.
Retry max delay 1 day To change the default, use the retry policy parameter.
Retry min delay 5 seconds To change the default, use the retry policy parameter.

Authentication limits

Here are the limits for a logic app that starts with a Request trigger and enables Azure Active Directory Open Authentication (Azure AD OAuth) for authorizing inbound calls to the Request trigger:

Name Limit Notes
Azure AD authorization policies 5
Claims per authorization policy 10

Custom connector limits

Here are the limits for custom connectors that you can create from web APIs.

Name Multi-tenant limit Integration service environment limit Notes
Number of custom connectors 1,000 per Azure subscription 1,000 per Azure subscription
Number of requests per minute for a custom connector 500 requests per minute per connection 2,000 requests per minute per custom connector

Managed identities

Name Limit
Managed identities per logic app Either the system-assigned identity or 1 user-assigned identity
Number of logic apps that have a managed identity in an Azure subscription per region 500

Integration account limits

Each Azure subscription has these integration account limits:

  • One Free tier integration account per Azure region

  • 1,000 total integration accounts, including integration accounts in any integration service environments (ISE) across both Developer and Premium SKUs.

  • Each ISE, whether Developer or Premium, is limited to 5 total integration accounts:

    ISE SKU Integration account limits
    Premium 5 total - Standard accounts only, including one Standard account for free. No Free or Basic accounts are permitted.
    Developer 5 total - Free (limited to 1 account) and Standard combined, or all Standard accounts. No Basic accounts are permitted. Use the Developer SKU for experimenting, development, and testing, but not for production or performance testing.

Additional costs apply to integration accounts that you add beyond the integration accounts that are included with an ISE. To learn how pricing and billing work for ISEs, see the Logic Apps pricing model. For pricing rates, see Logic Apps pricing.

Artifact limits per integration account

Here are the limits on the number of artifacts for each integration account tier. For pricing rates, see Logic Apps pricing. To learn how pricing and billing work for integration accounts, see the Logic Apps pricing model.

Note

Use the Free tier only for exploratory scenarios, not production scenarios. This tier restricts throughput and usage, and has no service-level agreement (SLA).

Artifact Free Basic Standard
EDI trading agreements 10 1 1,000
EDI trading partners 25 2 1,000
Maps 25 500 1,000
Schemas 25 500 1,000
Assemblies 10 25 1,000
Certificates 25 2 1,000
Batch configurations 5 1 50

Artifact capacity limits

Artifact Limit Notes
Assembly 8 MB To upload files larger than 2 MB, use an Azure storage account and blob container.
Map (XSLT file) 8 MB To upload files larger than 2 MB, use the Azure Logic Apps REST API - Maps.

Note: The amount of data or records that a map can successfully process is based on the message size and action timeout limits in Azure Logic Apps. For example, if you use an HTTP action, based on HTTP message size and timeout limits, a map can process data up to the HTTP message size limit if the operation completes within the HTTP timeout limit.

Schema 8 MB To upload files larger than 2 MB, use an Azure storage account and blob container.

Throughput limits

Runtime endpoint Free Basic Standard Notes
Read calls per 5 minutes 3,000 30,000 60,000 You can distribute the workload across more than one account as necessary.
Invoke calls per 5 minutes 3,000 30,000 45,000 You can distribute the workload across more than one account as necessary.
Tracking calls per 5 minutes 3,000 30,000 45,000 You can distribute the workload across more than one account as necessary.
Blocking concurrent calls ~1,000 ~1,000 ~1,000 Same for all SKUs. You can reduce the number of concurrent requests or reduce the duration as necessary.

B2B protocol (AS2, X12, EDIFACT) message size

Here are the message size limits that apply to B2B protocols:

Name Multi-tenant limit Integration service environment limit Notes
AS2 v2 - 100 MB
v1 - 50 MB
v2 - 200 MB
v1 - 50 MB
Applies to decode and encode
X12 50 MB 50 MB Applies to decode and encode
EDIFACT 50 MB 50 MB Applies to decode and encode

Disabling or deleting logic apps

When you disable a logic app, no new runs are instantiated. All in-progress and pending runs continue until they finish, which might take time to complete.

When you delete a logic app, no new runs are instantiated. All in-progress and pending runs are canceled. If you have thousands of runs, cancellation might take significant time to complete.

Firewall configuration: IP addresses and service tags

The IP addresses that Azure Logic Apps uses for incoming and outgoing calls depend on the region where your logic app exists. All logic apps in the same region use the same IP address ranges. Some Power Automate calls, such as HTTP and HTTP + OpenAPI requests, go directly through the Azure Logic Apps service and come from the IP addresses that are listed here. For more information about IP addresses used by Power Automate, see Limits and configuration in Power Automate.

Tip

To help reduce complexity when you create security rules, you can optionally use service tags, rather than specify the Logic Apps IP addresses for each region, described later in this section. These tags work across the regions where the Logic Apps service is available:

  • LogicAppsManagement: Represents the inbound IP address prefixes for the Logic Apps service.
  • LogicApps: Represents the outbound IP address prefixes for the Logic Apps service.
  • For Azure China 21Vianet, fixed or reserved IP addresses are unavailable for custom connectors and managed connectors, for example, Azure Storage, SQL Server, Office 365 Outlook, and so on.

  • To support the calls that your logic apps directly make with HTTP, HTTP + Swagger, and other HTTP requests, set up your firewall with all the inbound and outbound IP addresses that are used by the Logic Apps service, based on the regions where your logic apps exist. These addresses appear under the Inbound and Outbound headings in this section, and are sorted by region.

  • To support the calls that managed connectors make, set up your firewall with all the outbound IP addresses used by these connectors, based on the regions where your logic apps exist. These addresses appear under the Outbound heading in this section, and are sorted by region.

  • To enable communication for logic apps that run in an integration service environment (ISE), make sure that you open these ports.

  • If your logic apps have problems accessing Azure storage accounts that use firewalls and firewall rules, you have various options to enable access.

    For example, logic apps can't directly access storage accounts that use firewall rules and exist in the same region. However, if you permit the outbound IP addresses for managed connectors in your region, your logic apps can access storage accounts that are in a different region except when you use the Azure Table Storage or Azure Queue Storage connectors. To access your Table Storage or Queue Storage, you can use the HTTP trigger and actions instead. For other options, see Access storage accounts behind firewalls.

Inbound IP addresses

This section lists the inbound IP addresses for the Azure Logic Apps service only. If you have Azure Government, see Azure Government - Inbound IP addresses.

Tip

To help reduce complexity when you create security rules, you can optionally use the service tag, LogicAppsManagement, rather than specify inbound Logic Apps IP address prefixes for each region. This tag works across the regions where the Logic Apps service is available.

Multi-tenant Azure - Inbound IP addresses

Multi-tenant region IP
Australia East 13.75.153.66, 104.210.89.222, 104.210.89.244, 52.187.231.161
Australia Southeast 13.73.115.153, 40.115.78.70, 40.115.78.237, 52.189.216.28
Brazil South 191.235.86.199, 191.235.95.229, 191.235.94.220, 191.234.166.198
Canada Central 13.88.249.209, 52.233.30.218, 52.233.29.79, 40.85.241.105
Canada East 52.232.129.143, 52.229.125.57, 52.232.133.109, 40.86.202.42
Central India 52.172.157.194, 52.172.184.192, 52.172.191.194, 104.211.73.195
Central US 13.67.236.76, 40.77.111.254, 40.77.31.87, 104.43.243.39
East Asia 168.63.200.173, 13.75.89.159, 23.97.68.172, 40.83.98.194
East US 137.135.106.54, 40.117.99.79, 40.117.100.228, 137.116.126.165
East US 2 40.84.25.234, 40.79.44.7, 40.84.59.136, 40.70.27.253
France Central 52.143.162.83, 20.188.33.169, 52.143.156.55, 52.143.158.203
France South 52.136.131.145, 52.136.129.121, 52.136.130.89, 52.136.131.4
Japan East 13.71.146.140, 13.78.84.187, 13.78.62.130, 13.78.43.164
Japan West 40.74.140.173, 40.74.81.13, 40.74.85.215, 40.74.68.85
Korea Central 52.231.14.182, 52.231.103.142, 52.231.39.29, 52.231.14.42
Korea South 52.231.166.168, 52.231.163.55, 52.231.163.150, 52.231.192.64
North Central US 168.62.249.81, 157.56.12.202, 65.52.211.164, 65.52.9.64
North Europe 13.79.173.49, 52.169.218.253, 52.169.220.174, 40.112.90.39
South Africa North 102.133.228.4, 102.133.224.125, 102.133.226.199, 102.133.228.9
South Africa West 102.133.72.190, 102.133.72.145, 102.133.72.184, 102.133.72.173
South Central US 13.65.98.39, 13.84.41.46, 13.84.43.45, 40.84.138.132
South India 52.172.9.47, 52.172.49.43, 52.172.51.140, 104.211.225.152
Southeast Asia 52.163.93.214, 52.187.65.81, 52.187.65.155, 104.215.181.6
UAE Central 20.45.75.193, 20.45.64.29, 20.45.64.87, 20.45.71.213
UK South 51.140.79.109, 51.140.78.71, 51.140.84.39, 51.140.155.81
UK West 51.141.48.98, 51.141.51.145, 51.141.53.164, 51.141.119.150
West Central US 52.161.26.172, 52.161.8.128, 52.161.19.82, 13.78.137.247
West Europe 13.95.155.53, 52.174.54.218, 52.174.49.6
West India 104.211.164.112, 104.211.165.81, 104.211.164.25, 104.211.157.237
West US 52.160.90.237, 138.91.188.137, 13.91.252.184, 157.56.160.212
West US 2 13.66.224.169, 52.183.30.10, 52.183.39.67, 13.66.128.68

Azure Government - Inbound IP addresses

Azure Government region IP
US Gov Arizona 52.244.67.164, 52.244.67.64, 52.244.66.82
US Gov Texas 52.238.119.104, 52.238.112.96, 52.238.119.145
US Gov Virginia 52.227.159.157, 52.227.152.90, 23.97.4.36
US DoD Central 52.182.49.204, 52.182.52.106

Outbound IP addresses

This section lists the outbound IP addresses for the Azure Logic Apps service and managed connectors. If you have Azure Government, see Azure Government - Outbound IP addresses.

Tip

To help reduce complexity when you create security rules, you can optionally use the service tag, LogicApps, rather than specify outbound Logic Apps IP address prefixes for each region. This tag works across the regions where the Logic Apps service is available. For managed connectors, you must continue to use the IP addresses.

Multi-tenant Azure - Outbound IP addresses

Multi-tenant region Logic Apps IP Managed connectors IP
Australia East 13.75.149.4, 104.210.91.55, 104.210.90.241, 52.187.227.245, 52.187.226.96, 52.187.231.184, 52.187.229.130, 52.187.226.139 13.70.72.192 - 13.70.72.207, 13.72.243.10, 40.126.251.213, 52.237.214.72
Australia Southeast 13.73.114.207, 13.77.3.139, 13.70.159.205, 52.189.222.77, 13.77.56.167, 13.77.58.136, 52.189.214.42, 52.189.220.75 13.70.136.174, 13.77.50.240 - 13.77.50.255, 40.127.80.34, 52.255.48.202
Brazil South 191.235.82.221, 191.235.91.7, 191.234.182.26, 191.237.255.116, 191.234.161.168, 191.234.162.178, 191.234.161.28, 191.234.162.131 104.41.59.51, 191.232.38.129, 191.233.203.192 - 191.233.203.207, 191.232.191.157
Canada Central 52.233.29.92, 52.228.39.241, 52.228.39.244, 40.85.250.135, 40.85.250.212, 13.71.186.1, 40.85.252.47, 13.71.184.150 13.71.170.208 - 13.71.170.223, 52.228.33.76, 52.228.34.13, 52.228.42.205, 52.233.31.197, 52.237.24.126, 52.237.32.212
Canada East 52.232.128.155, 52.229.120.45, 52.229.126.25, 40.86.203.228, 40.86.228.93, 40.86.216.241, 40.86.226.149, 40.86.217.241 40.69.106.240 - 40.69.106.255, 52.229.120.52, 52.229.120.178, 52.229.123.98, 52.229.126.202, 52.242.35.152, 52.242.30.112
Central India 52.172.154.168, 52.172.186.159, 52.172.185.79, 104.211.101.108, 104.211.102.62, 104.211.90.169, 104.211.90.162, 104.211.74.145 52.172.211.12, 104.211.81.192 - 104.211.81.207, 104.211.98.164, 52.172.212.129
Central US 13.67.236.125, 104.208.25.27, 40.122.170.198, 40.113.218.230, 23.100.86.139, 23.100.87.24, 23.100.87.56, 23.100.82.16 13.89.171.80 - 13.89.171.95, 40.122.49.51, 52.173.245.164, 52.173.241.27
East Asia 13.75.94.173, 40.83.127.19, 52.175.33.254, 40.83.73.39, 65.52.175.34, 40.83.77.208, 40.83.100.69, 40.83.75.165 13.75.36.64 - 13.75.36.79, 23.99.116.181, 52.175.23.169, 13.75.110.131
East US 13.92.98.111, 40.121.91.41, 40.114.82.191, 23.101.139.153, 23.100.29.190, 23.101.136.201, 104.45.153.81, 23.101.132.208 40.71.11.80 - 40.71.11.95, 40.71.249.205, 40.114.40.132, 40.71.249.139
East US 2 40.84.30.147, 104.208.155.200, 104.208.158.174, 104.208.140.40, 40.70.131.151, 40.70.29.214, 40.70.26.154, 40.70.27.236 40.70.146.208 - 40.70.146.223, 52.232.188.154, 104.208.233.100, 104.209.247.23, 52.225.129.144
France Central 52.143.164.80, 52.143.164.15, 40.89.186.30, 20.188.39.105, 40.89.191.161, 40.89.188.169, 40.89.186.28, 40.89.190.104 40.79.130.208 - 40.79.130.223, 40.89.135.2, 40.89.186.239
France South 52.136.132.40, 52.136.129.89, 52.136.131.155, 52.136.133.62, 52.136.139.225, 52.136.130.144, 52.136.140.226, 52.136.129.51 40.79.178.240 - 40.79.178.255, 52.136.133.184, 52.136.142.154
Japan East 13.71.158.3, 13.73.4.207, 13.71.158.120, 13.78.18.168, 13.78.35.229, 13.78.42.223, 13.78.21.155, 13.78.20.232 13.71.153.19, 13.78.108.0 - 13.78.108.15, 40.115.186.96, 13.73.21.230
Japan West 40.74.140.4, 104.214.137.243, 138.91.26.45, 40.74.64.207, 40.74.76.213, 40.74.77.205, 40.74.74.21, 40.74.68.85 40.74.100.224 - 40.74.100.239, 40.74.130.77, 104.215.61.248, 104.215.27.24
Korea Central 52.231.14.11, 52.231.14.219, 52.231.15.6, 52.231.10.111, 52.231.14.223, 52.231.77.107, 52.231.8.175, 52.231.9.39 52.231.18.208 - 52.231.18.223, 52.141.36.214, 52.141.1.104
Korea South 52.231.204.74, 52.231.188.115, 52.231.189.221, 52.231.203.118, 52.231.166.28, 52.231.153.89, 52.231.155.206, 52.231.164.23 52.231.147.0 - 52.231.147.15, 52.231.163.10, 52.231.201.173
North Central US 168.62.248.37, 157.55.210.61, 157.55.212.238, 52.162.208.216, 52.162.213.231, 65.52.10.183, 65.52.9.96, 65.52.8.225 52.162.107.160 - 52.162.107.175, 52.162.242.161, 65.52.218.230, 52.162.126.4
North Europe 40.113.12.95, 52.178.165.215, 52.178.166.21, 40.112.92.104, 40.112.95.216, 40.113.4.18, 40.113.3.202, 40.113.1.181 13.69.227.208 - 13.69.227.223, 52.178.150.68, 104.45.93.9, 94.245.91.93, 52.169.28.181
South Africa North 102.133.231.188, 102.133.231.117, 102.133.230.4, 102.133.227.103, 102.133.228.6, 102.133.230.82, 102.133.231.9, 102.133.231.51 13.65.86.57, 104.214.19.48 - 104.214.19.63, 104.214.70.191, 102.133.168.167
South Africa West 102.133.72.98, 102.133.72.113, 102.133.75.169, 102.133.72.179, 102.133.72.37, 102.133.72.183, 102.133.72.132, 102.133.75.191 13.65.86.57, 104.214.19.48 - 104.214.19.63, 104.214.70.191, 102.133.72.85
South Central US 104.210.144.48, 13.65.82.17, 13.66.52.232, 23.100.124.84, 70.37.54.122, 70.37.50.6, 23.100.127.172, 23.101.183.225 13.65.86.57, 104.214.19.48 - 104.214.19.63, 104.214.70.191, 52.171.130.92
South India 52.172.50.24, 52.172.55.231, 52.172.52.0, 104.211.229.115, 104.211.230.129, 104.211.230.126, 104.211.231.39, 104.211.227.229 13.71.125.22, 40.78.194.240 - 40.78.194.255, 104.211.227.225, 13.71.127.26
Southeast Asia 13.76.133.155, 52.163.228.93, 52.163.230.166, 13.76.4.194, 13.67.110.109, 13.67.91.135, 13.76.5.96, 13.67.107.128 13.67.8.240 - 13.67.8.255, 13.76.231.68, 52.187.68.19, 52.187.115.69
UAE Central 20.45.75.200, 20.45.72.72, 20.45.75.236, 20.45.79.239, 20.45.67.170, 20.45.72.54, 20.45.67.134, 20.45.67.135 20.45.67.28, 20.45.67.45, 20.37.74.192 - 20.37.74.207, 40.120.8.0 - 40.120.8.31
UK South 51.140.74.14, 51.140.73.85, 51.140.78.44, 51.140.137.190, 51.140.153.135, 51.140.28.225, 51.140.142.28, 51.140.158.24 51.140.80.51, 51.140.148.0 - 51.140.148.15, 51.140.61.124, 51.140.74.150
UK West 51.141.54.185, 51.141.45.238, 51.141.47.136, 51.141.114.77, 51.141.112.112, 51.141.113.36, 51.141.118.119, 51.141.119.63 51.140.211.0 - 51.140.211.15, 51.141.47.105, 51.141.124.13, 51.141.52.185
West Central US 52.161.27.190, 52.161.18.218, 52.161.9.108, 13.78.151.161, 13.78.137.179, 13.78.148.140, 13.78.129.20, 13.78.141.75 13.71.195.32 - 13.71.195.47, 52.161.102.22, 13.78.132.82, 52.161.101.204
West Europe 40.68.222.65, 40.68.209.23, 13.95.147.65, 23.97.218.130, 51.144.182.201, 23.97.211.179, 104.45.9.52, 23.97.210.126 13.69.64.208 - 13.69.64.223, 40.115.50.13, 52.174.88.118, 40.91.208.65, 52.166.78.89
West India 104.211.164.80, 104.211.162.205, 104.211.164.136, 104.211.158.127, 104.211.156.153, 104.211.158.123, 104.211.154.59, 104.211.154.7 104.211.146.224 - 104.211.146.239, 104.211.161.203, 104.211.189.218, 104.211.189.124
West US 52.160.92.112, 40.118.244.241, 40.118.241.243, 157.56.162.53, 157.56.167.147, 104.42.49.145, 40.83.164.80, 104.42.38.32 40.112.243.160 - 40.112.243.175, 104.40.51.248, 104.42.122.49, 40.112.195.87, 13.93.148.62
West US 2 13.66.210.167, 52.183.30.169, 52.183.29.132, 13.66.210.167, 13.66.201.169, 13.77.149.159, 52.175.198.132, 13.66.246.219 13.66.140.128 - 13.66.140.143, 52.183.78.157, 52.191.164.250

Azure Government - Outbound IP addresses

Region Logic Apps IP Managed connectors IP
US Gov Arizona 52.244.67.143, 52.244.65.66, 52.244.65.190 52.127.2.160 - 52.127.2.175, 52.244.69.0, 52.244.64.91
US Gov Texas 52.238.114.217, 52.238.115.245, 52.238.117.119 52.127.34.160 - 52.127.34.175, 40.112.40.25, 52.238.161.225
US Gov Virginia 13.72.54.205, 52.227.138.30, 52.227.152.44 52.127.42.128 - 52.127.42.143, 52.227.143.61, 52.227.162.91
US DoD Central 52.182.48.215, 52.182.92.143 52.127.58.160 - 52.127.58.175, 52.182.54.8, 52.182.48.136

Next steps