Limits and configuration reference for Azure Logic Apps

บทความ
09/06/2024

Applies to: Azure Logic Apps (Consumption + Standard)

For Power Automate, review Limits and configuration in Power Automate.

This reference guide describes the limits and configuration information for Azure Logic Apps and related resources. Based on your scenario, solution requirements, the capabilities that you want, and the environment where you want to run your workflows, you choose whether to create a Consumption logic app workflow that runs in multitenant Azure Logic Apps or a Standard logic app workflow that runs in single-tenant Azure Logic Apps or an App Service Environment (v3 - Windows plans only).

Note

Many limits are the same across the available environments where Azure Logic Apps runs, but differences are noted where they exist.

The following table briefly summarizes differences between a Consumption logic app and a Standard logic app.

Hosting option	Benefits	Resource sharing and usage	Pricing and billing model	Limits management
Consumption Host environment: Multitenant Azure Logic Apps	- Easiest to get started - Pay for what you use - Fully managed	A single logic app resource can have only one workflow. All logic apps across Microsoft Entra tenants share the same processing (compute), storage, network, and so on. For redundancy purposes, data is replicated in the paired region. For high availability, geo-redundant storage (GRS) is enabled.	Consumption (pay-per-execution)	Azure Logic Apps manages the default values for these limits, but you can change some of these values, if that option exists for a specific limit.
Standard (Workflow Service Plan) Host environment: Single-tenant Azure Logic Apps Note: If your scenario requires containers, create single-tenant based logic apps using Azure Arc enabled Logic Apps. For more information, review What is Azure Arc enabled Logic Apps?	- More built-in connectors hosted on the single-tenant runtime for higher throughput and lower costs at scale - More control and fine-tuning capability around runtime and performance settings - Integrated support for virtual networks and private endpoints. - Create your own built-in connectors.	A single logic app resource can have multiple stateful and stateless workflows. Workflows in a single logic app and tenant share the same processing (compute), storage, network, and so on. Data stays in the same region where you deploy your logic app.	Standard, based on a hosting plan with a selected pricing tier. If you run stateful workflows, which use external storage, the Azure Logic Apps runtime makes storage transactions that follow Azure Storage pricing.	You can change the default values for many limits, based on your scenario's needs. Important: Some limits have hard upper maximums. In Visual Studio Code, the changes you make to the default limit values in your logic app project configuration files won't appear in the designer experience. For more information, see Edit app and environment settings for logic apps in single-tenant Azure Logic Apps.
Standard (App Service Environment v3) Host environment: App Service Environment v3 (ASEv3) - Windows plans only	Same capabilities as single-tenant plus the following benefits: - Fully isolate your logic apps. - Create and run more logic apps than in single-tenant Azure Logic Apps. - Pay only for the ASE App Service plan, no matter the number of logic apps that you create and run. - Can enable autoscaling or manually scale with more virtual machine instances or a different App Service plan. - Inherit the network setup from the selected ASEv3. For example, when you deploy to an internal ASE, workflows can access the resources in a virtual network associated with the ASE and have internal access points. Note: If accessed from outside an internal ASE, run histories for workflows in that ASE can't access action inputs and outputs.	A single logic app can have multiple stateful and stateless workflows. Workflows in a single logic app and tenant share the same processing (compute), storage, network, and so on. Data stays in the same region where you deploy your logic apps.	App Service plan	You can change the default values for many limits, based on your scenario's needs. Important: Some limits have hard upper maximums. In Visual Studio Code, the changes you make to the default limit values in your logic app project configuration files won't appear in the designer experience. For more information, see Edit app and environment settings for logic apps in single-tenant Azure Logic Apps.

Workflow definition limits

The following tables list the values for a single workflow definition:

Name	Limit	Notes
Workflows per region per Azure subscription	- Consumption: 1,000 workflows where each logic app always has only 1 workflow - Standard: Unlimited, based on the selected hosting plan, app activity, size of machine instances, and resource usage, where each logic app can have multiple workflows	For optimal performance guidelines around Standard logic app workflows, see Best practices and recommendations.
Workflow - Maximum name length	- Consumption: 80 characters - Standard: 32 characters
Triggers per workflow	- Consumption (designer): 1 trigger - Consumption (JSON): 10 triggers - Standard: 1 trigger	- Consumption: Multiple triggers are possible only when you work on the JSON workflow definition, whether in code view or an Azure Resource Manager (ARM) template, not the designer. - Standard: Only one trigger is possible, whether in the designer, code view, or an Azure Resource Manager (ARM) template.
Actions per workflow	500 actions	To extend this limit, you can use nested workflows as necessary.
Actions nesting depth	8 actions	To extend this limit, you can use nested workflows as necessary.
Single trigger or action - Maximum name length	80 characters
Single trigger or action - Maximum input or output size	104,857,600 bytes (105 MB)	To change the default value in the single-tenant service, review Edit host and app settings for logic apps in single-tenant Azure Logic Apps.
Single action - Maximum combined inputs and outputs size	209,715,200 bytes (210 MB)	To change the default value in the single-tenant service, review Edit host and app settings for logic apps in single-tenant Azure Logic Apps.
Expression character limit	8,192 characters
`description` - Maximum length	256 characters
`parameters` - Maximum number of parameters per workflow	- Consumption: 50 parameters - Standard: 500 parameters
`outputs` - Maximum number of outputs	10 outputs
`trackedProperties` - Maximum number of characters	8,000 characters

Run duration and history retention limits

The following table lists the values for a single workflow run:

Name	Multitenant	Single-tenant	Notes
Run history retention in storage	90 days	90 days (Default)	The amount of time to keep a workflow's run history in storage after a run starts. Note: If the workflow's run duration exceeds the retention limit, this run is removed from the run history in storage. If a run isn't immediately removed after reaching the retention limit, the run is removed within 7 days. Whether a run completes or times out, run history retention is always calculated by using the run's start time and the current limit specified in the workflow setting, Run history retention in days. No matter the previous limit, the current limit is always used for calculating retention. For more information, review Change duration and run history retention in storage.
Run duration	90 days	- Stateful workflow: 90 days (Default) - Stateless workflow: 5 min (Default)	The amount of time that a workflow can continue running before forcing a timeout. The run duration is calculated by using a run's start time and the limit that's specified in the workflow setting, Run history retention in days at that start time. Important: Make sure the run duration value is always less than or equal to the run history retention in storage value. Otherwise, run histories might be deleted before the associated jobs are complete. For more information, review Change run duration and history retention in storage.
Recurrence interval	- Min: 1 sec - Max: 500 days	- Min: 1 sec - Max: 500 days

Change run duration and history retention in storage

If a run's duration exceeds the current run history retention limit, the run is removed from the runs history in storage. To avoid losing run history, make sure that the retention limit is always more than the run's longest possible duration.

Consumption
Standard

For Consumption logic app workflows, the same setting controls the maximum number of days that a workflow can run and for keeping run history in storage.

In multitenant Azure Logic Apps, the 90-day default limit is the same as the maximum limit. You can only decrease this value.

For example, suppose that you reduce the retention limit from 90 days to 30 days. A 60-day-old run is removed from the runs history. If you increase the retention period from 30 days to 60 days, a 20-day-old run stays in the runs history for another 40 days.

Portal

In the Azure portal search box, open your logic app workflow in the designer.
On the logic app menu, select Workflow settings.
Under Runtime options, from the Run history retention in days list, select Custom.
Drag the slider to change the number of days that you want.
When you're done, on the Workflow settings toolbar, select Save.

ARM template

If you use an Azure Resource Manager template, this setting appears as a property in your workflow's resource definition, which is described in the Microsoft.Logic workflows template reference:

{
   "name": "{logic-app-name}",
   "type": "Microsoft.Logic/workflows",
   "location": "{Azure-region}",
   "apiVersion": "2019-05-01",
   "properties": {
      "definition": {},
      "parameters": {},
      "runtimeConfiguration": {
         "lifetime": {
            "unit": "day",
            "count": {number-of-days}
         }
      }
   }
}

Looping, concurrency, and debatching limits

The following table lists the values for a single workflow run:

Loop actions

For each loop

The following table lists the values for a For each loop:

Name	Multitenant	Single-tenant	Notes
Array items	100,000 items	- Stateful workflow: 100,000 items (Default) - Stateless workflow: 100 items (Default)	The number of array items that a For each loop can process. To filter larger arrays, you can use the query action. To change the default limit in the single-tenant service, review Edit host and app settings for logic apps in single-tenant Azure Logic Apps.
Concurrent iterations	Concurrency off: 20 Concurrency on: - Default: 20 - Min: 1 - Max: 50	Concurrency off: 20 (Default) Concurrency on: - Default: 20 - Min: 1 - Max: 50	The number of For each loop iterations that can run at the same time, or in parallel. To change this value in multitenant Azure Logic Apps, see Change For each concurrency limit or Run For each loops sequentially. To change the default limit in the single-tenant service, review Edit host and app settings for logic apps in single-tenant Azure Logic Apps.

Until loop

The following table lists the values for an Until loop:

Name	Multitenant	Single-tenant	Notes
Iterations	- Default: 60 - Min: 1 - Max: 5,000	Stateful workflow: - Default: 60 - Min: 1 - Max: 5,000 Stateless workflow: - Default: 60 - Min: 1 - Max: 100	The number of cycles that an Until loop can have during a workflow run. To change this value in multitenant Azure Logic Apps, in the Until loop shape, select Change limits, and specify the value for the Count property. To change the default value in the single-tenant service, review Edit host and app settings for logic apps in single-tenant Azure Logic Apps.
Timeout	Default: PT1H (1 hour)	Stateful workflow: PT1H (1 hour) Stateless workflow: PT5M (5 min)	The amount of time that the Until loop can run before exiting and is specified in ISO 8601 format. The timeout value is evaluated for each loop cycle. If any action in the loop takes longer than the timeout limit, the current cycle doesn't stop. However, the next cycle doesn't start because the limit condition isn't met. To change this value in multitenant Azure Logic Apps, in the Until loop shape, select Change limits, and specify the value for the Timeout property. To change the default value in the single-tenant service, review Edit host and app settings for logic apps in single-tenant Azure Logic Apps.

Concurrency and debatching

Name	Multitenant	Single-tenant	Notes
Trigger - concurrent runs	Concurrency off: Unlimited Concurrency on (irreversible): - Default: 25 - Min: 1 - Max: 100	Concurrency off: Unlimited Concurrency on (irreversible): - Default: 100 - Min: 1 - Max: 100	The number of concurrent runs that a trigger can start 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 this value in multitenant Azure Logic Apps, see Change trigger concurrency limit or Trigger instances sequentially. To change the default value in the single-tenant service, review Edit host and app settings for logic apps in single-tenant Azure Logic Apps.
Maximum waiting runs	Concurrency on: - Min: 10 runs plus the number of concurrent runs (Default) - Max: 100 runs	Concurrency on: - Min: 10 runs plus the number of concurrent runs (Default) - Max: 200 runs	The number of workflow instances that can wait to run when your current workflow instance is already running the maximum concurrent instances. This setting takes effect only if concurrency is turned on. To change this value in multitenant Azure Logic Apps, see Change waiting runs limit. To change the default value in the single-tenant service, review Edit host and app settings for logic apps in single-tenant Azure Logic Apps.
SplitOn items	Concurrency off: 100,000 items Concurrency on: 100 items	Concurrency off: 100,000 items Concurrency on: 100 items	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 For each 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.

Throughput limits

The following table lists the values for a single workflow definition:

Name	Multitenant	Single-tenant	Notes
Action - Executions per 5-minute rolling interval	Default: 100,000 executions - High throughput mode: 300,000 executions	None	In multitenant Azure Logic Apps, you can raise the default value to the maximum value for your workflow. For more information, see Run in high throughput mode, which is in preview. Or, you can distribute the workload across more than one workflow as necessary.
Action - Concurrent outbound calls	~2,500 calls	None	You can reduce the number of concurrent requests or reduce the duration as necessary.
Managed connector throttling	Throttling limit varies based on connector	Throttling limit varies based on connector	For multitenant, review each managed connector's technical reference page. For more information about handling connector throttling, review Handle throttling problems ("429 - Too many requests" errors).
Runtime endpoint - Concurrent inbound calls	~1,000 calls	None	You can reduce the number of concurrent requests or reduce the duration as necessary.
Runtime endpoint- Concurrent inbound calls for API Management REST API		56 calls per 5 minutes	Applies only to API Management REST API calls to the Request trigger in a Standard logic app workflow. Use the callback URL to send the request to the Request trigger in a Standard logic app workflow, rather than use API Management calls, which have a hard throttling limit of 56 calls per 5-minute interval.
Runtime endpoint - Read calls per 5 min	60,000 read calls	None	This limit applies to calls that get the raw inputs and outputs from a workflow's run history. You can distribute the workload across more than one workflow as necessary.
Runtime endpoint - Invoke calls per 5 min	45,000 invoke calls	None	You can distribute workload across more than one workflow as necessary.
Content throughput per 5 min	6 GB	None	For example, suppose the backend has 100 workers. Each worker has a limit of 60 MB, which is the result from dividing 6 GB by 100 workers. You can distribute workload across more than one workflow as necessary.

In single-tenant Azure Logic Apps, a Standard logic app resource uses storage and compute as the primary resources to run workflows.

Storage

Stateful workflows in single-tenant Azure Logic Apps use Azure Table Storage for persistent data storage during runtime, Azure Blob Storage for maintaining workflow run histories, and Azure Queue Storage for scheduling purposes. For example, a single storage account enables handling a substantial number of requests with rates of up to 2,000 requests per partition and 20,000 requests per second at the storage account level. While a single storage account can handle reasonably high throughput, beyond these thresholds, request rates are subject to throttling, and your workflows might experience partition level throttling or account level throttling as workflow execution rate increases. To make sure that your workflows operate smoothly, it's crucial that you understand the possible limitations and the ways that you can address them.

For more information about scaling targets and limitations for the various Azure Storage services, see the following documentation:

Scale your logic app for storage limitations

The following recommendations apply to scaling Standard logic app workflows:

Share workload across multiple workflows.

Single-tenant Azure Logic Apps already minimizes partition-level throttling by distributing storage transactions across multiple partitions. However, to improve distribution and mitigate partition-level throttling, distribute the workload across multiple workflows, rather than rely on a single workflow.

Share workload across multiple storage accounts.

If your workflows require high throughput, you can significantly increase throughput by distributing the workload across multiple storage accounts, rather than rely on a single storage account. You can set up your Standard logic app resource to use up to 32 storage accounts as the limit. To determine the number of storage accounts that you need, use the general guideline of aiming for ~100,000 action executions per minute, per storage account. While this estimate works well for most scenarios, you might use a lower number of action executions if your workflow actions are compute heavy, for example, a query action that processes large data arrays. Make sure that you perform load testing and tune your solution before using in production.

To enable using multiple storage accounts, follow these steps before you create your Standard logic app. Otherwise, if you change the settings after creation, you might experience data loss or not achieve the necessary scalability.

Create the storage accounts that you want to use. Save the connection string for each storage account.

Find and open your Standard logic app, and then edit your logic app's host settings (host.json file) to include the following extensions object, which contains the workflow and settings objects with the Runtime.ScaleUnitsCount setting:

"extensions": {
    "workflow": {
        "settings": {
            "Runtime.ScaleUnitsCount": "<storage-accounts-number>"
        }
    }
}

The following example specifies 3 as the number of storage accounts:

{
    "version": "2.0",
    "extensionBundle": {
        "id": "Microsoft.Azure.Functions.ExtensionBundle.Workflows",
        "version": "[1.*, 2.0.0)"
    },
    "extensions": {
        "workflow": {
            "settings": {
                "Runtime.ScaleUnitsCount": "3"
            }
        }
    }
}

Edit your logic app's application configuration settings (local.settings.json) to add an app setting named CloudStorageAccount.Workflows.ScaleUnitsDataStorage.CU0<storage-account-number>.ConnectionString and the corresponding storage account connection string using the following syntax where the first storage account number is 00 up to the number of storage accounts minus 1, for example:

App setting name	Value
CloudStorageAccount.Workflows.ScaleUnitsDataStorage.CU00.ConnectionString	`<connection-string-1>`
CloudStorageAccount.Workflows.ScaleUnitsDataStorage.CU01.ConnectionString	`<connection-string-2>`
CloudStorageAccount.Workflows.ScaleUnitsDataStorage.CU02.ConnectionString	`<connection-string-3>`

Important

When you have sensitive information, such as connection strings that include usernames and passwords, make sure to use the most secure authentication flow available. For example, in Standard logic app workflows, secure data types, such as securestring and secureobject, aren't supported. Microsoft recommends that you authenticate access to Azure resources with a managed identity when possible, and assign a role that has the least privilege necessary.

If this capability is unavailable, make sure to secure connection strings through other measures, such as Azure Key Vault, which you can use with app settings. You can then directly reference secure strings, such as connection strings and keys. Similar to ARM templates, where you can define environment variables at deployment time, you can define app settings within your logic app workflow definition. You can then capture dynamically generated infrastructure values, such as connection endpoints, storage strings, and more. For more information, see Application types for the Microsoft identity platform.

In your logic app's application configuration settings, update the AzureWebJobsStorage setting value with the same connection string that's in the CloudStorageAccount.Workflows.ScaleUnitsDataStorage.CU00.ConnectionString setting.

Compute

A Standard logic app runs by using one of the available compute plans, which provide different levels of virtual CPU and memory, or by using an App Service Environment v3, which provides more compute options.

Single-tenant Azure Logic Apps dynamically scales to effectively handle increasing loads. Your logic app uses the following primary factors to determine whether to scale.

Note

For a Standard logic app in an App Service Environment v3, dynamic scaling isn't available. You must set scaling rules on the associated App Service Plan. As a commonly used scaling rule, you can use the CPU metric, and scale your App Service Plan to keep the virtual CPU between 50-70%. For more information, see Get started with autoscale in Azure.

Trigger

To determine scaling requirements, the scaler analyzes the trigger that starts each workflow in your logic app. For example, for a workflow with a Service Bus trigger, if the queue length continuously grows, the scaler takes action to add worker instances, which enable processing more messages. Likewise, for a workflow with a Request trigger, if the request latency experiences an upward trend, the scaler increases the number of worker instances to distribute the request load more efficiently. For more information about worker instances, see Azure Logic Apps (Standard) - Runtime Deep Dive.
Workflow job execution delay

At runtime, workflow actions are divided into individual jobs that are queued for execution. Job dispatchers regularly poll the job queue to retrieve and execute these jobs. However, if compute capacity is insufficient to pick up these jobs, they stay in the queue for a longer time, resulting in increased execution delays. The scaler monitors this situation and make scaling decisions to keep the execution delays under control. For more information about how the runtime schedules and runs jobs, see Azure Logic Apps (Standard) - Runtime Deep Dive.

The scaler also considers the minimum and maximum worker instance counter configuration to determine whether to make scaling decisions, such as adding, removing, or maintaining the current number of worker instances. Typically, the scaler makes these decisions at intervals of approximately 15-30 seconds. So, consider this ramp-up time and its impact on your logic app's scaling speed to effectively handle peak loads. For example, if your workload requires scaling your logic app from just 1 worker instance to 100 worker instances, the ramp-up alone might take 25-50 minutes. Single-tenant Azure Logic Apps scaling shares the same Azure Functions scaling infrastructure.

Configure your logic app compute for faster scaling

Share workload across multiple logic apps.

Each logic app can scale independently, so distributing your workload across more than one logic app can significantly accelerate the scaling speed. For example, two logic apps can scale to twice the number of worker instances in the same timeframe as a single logic app. By splitting your workload across multiple apps, you can effectively multiply the scalability and achieve faster scaling results.
Use prewarmed instances.

If your scenario requires quicker ramp-up time, consider using prewarmed instances. If your peak load times are deterministic, you can use an automation task to adjust these prewarm instances on a schedule. For more information, see Manage Azure resources and monitor costs by creating automation tasks (preview).

Multitenant Azure Logic Apps has a default limit on the number of actions that run every 5 minutes. To raise the default value to the maximum value, you can enable high throughput mode, which is in preview. Or, distribute the workload across multiple logic apps and workflows, rather than rely on a single logic app and workflow.

Enable high throughput in the portal

In the Azure portal, on your logic app's menu, under Settings, select Workflow settings.
Under Runtime options > High throughput, change the setting to On.

Enable high throughput in a Resource Manager template

To enable this setting in an ARM template for deploying your logic app, in the properties object for your logic app's resource definition, add the runtimeConfiguration object with the operationOptions property set to OptimizedForHighThroughput:

{
   <template-properties>
   "resources": [
      // Start logic app resource definition
      {
         "properties": {
            <logic-app-resource-definition-properties>,
            <logic-app-workflow-definition>,
            <more-logic-app-resource-definition-properties>,
            "runtimeConfiguration": {
               "operationOptions": "OptimizedForHighThroughput"
            }
         },
         "name": "[parameters('LogicAppName')]",
         "type": "Microsoft.Logic/workflows",
         "location": "[parameters('LogicAppLocation')]",
         "tags": {},
         "apiVersion": "2016-06-01",
         "dependsOn": [
         ]
      }
      // End logic app resource definition
   ],
   "outputs": {}
}

For more information about your logic app resource definition, review Overview: Automate deployment for Azure Logic Apps by using Azure Resource Manager templates.

Data gateway limits

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

Retry policy limits

The following table lists the retry policy limits for a trigger or action, based on whether you have a Consumption or Standard logic app workflow.

Name	Consumption limit	Standard limit	Notes
Retry attempts	- Default: 4 attempts - Max: 90 attempts	- Default: 4 attempts	To change the default limit in Consumption logic app workflows, use the retry policy parameter. To change the default limit in Standard logic app workflows, review Edit host and app settings for logic apps in single-tenant Azure Logic Apps.
Retry interval	None	Default: 7 sec	To change the default limit in Consumption logic app workflows, use the retry policy parameter. To change the default limit in Standard logic app workflows, review Edit host and app settings for logic apps in single-tenant Azure Logic Apps.

Variables action limits

The following table lists the values for a single workflow definition:

Name	Multitenant	Single-tenant	Notes
Variables per workflow	250 variables	250 variables (Default)
Variable - Maximum content size	104,857,600 characters	Stateful workflow: 104,857,600 characters (Default) Stateless workflow: 1,024 characters (Default)	To change the default value in the single-tenant service, review Edit host and app settings for logic apps in single-tenant Azure Logic Apps.
Variable (Array type) - Maximum number of array items	100,000 items	100,000 items (Default)	To change the default value in the single-tenant service, review Edit host and app settings for logic apps in single-tenant Azure Logic Apps.

HTTP request limits

The following tables list the values for a single inbound or outbound call:

Timeout duration

By default, the HTTP action and APIConnection actions follow the standard asynchronous operation pattern, while the Response action follows the synchronous operation pattern. Some managed connector operations make asynchronous calls or listen for webhook requests, so the timeout for these operations might be longer than the following limits. For more information, review each connector's technical reference page and also the Workflow triggers and actions documentation.

Note

For a Standard logic app resource in single-tenant Azure Logic Apps, stateless workflows can only run synchronously.

Name	Multitenant	Single-tenant	Notes
Outbound request	120 sec (2 min)	235 sec (3.9 min) (Default)	Examples of outbound requests include calls made by the HTTP trigger or action. Tip: For longer running operations, use an asynchronous polling pattern or an "Until" loop. To work around timeout limits when you call another workflow that has a callable endpoint, you can use the built-in Azure Logic Apps action instead, which you can find in the designer's operation picker under Built-in. To change the default limit in the single-tenant service, review Edit host and app settings for logic apps in single-tenant Azure Logic Apps.
Inbound request	120 sec (2 min)	235 sec (3.9 min) (Default)	Examples of inbound requests include calls received by the Request trigger, HTTP Webhook trigger, and HTTP Webhook action. Note: For the original caller to get the response, all steps in the response must finish within the limit unless you call another nested workflow. For more information, see Call, trigger, or nest logic apps. To change the default limit in the single-tenant service, review Edit host and app settings for logic apps in single-tenant Azure Logic Apps.

Request trigger and webhook trigger size limits

Name	Multitenant	Single-tenant	Notes
Request trigger (inbound) and webhook-based triggers - Content size limit per 5-minute rolling interval per workflow	3,145,728 KB	None	This limit applies only to the content size for inbound requests received by the Request trigger or any webhook trigger. For example, suppose the backend has 100 workers. Each worker has a limit of 31,457,280 bytes, which is the result from dividing 3,145,728,000 bytes by 100 workers. To avoid experiencing premature throttling for the Request trigger, use a new HTTP client for each request, which helps evenly distribute the calls across all nodes. For a webhook trigger, you might have to use multiple workflows, which split the load and avoids throttling.

Messages

Name	Chunking enabled	Multitenant	Single-tenant	Notes
Content download - Maximum number of requests	Yes	1,000 requests	1,000 requests (Default)
Message size	No	100 MB	100 MB	To work around this limit, see Handle large messages with chunking. However, some connectors and APIs don't support chunking or even the default limit. - Connectors such as AS2, X12, and EDIFACT have their own B2B message limits. To change the default value in the single-tenant service, review Edit host and app settings for logic apps in single-tenant Azure Logic Apps.
Message size per action	Yes	1 GB	1,073,741,824 bytes (1 GB) (Default)	This limit applies to actions that either natively support chunking or let you enable chunking in their runtime configuration. For more information about chunking, see Handle large messages with chunking. To change the default value in the single-tenant service, review Edit host and app settings for logic apps in single-tenant Azure Logic Apps.
Content chunk size per action	Yes	Varies per connector	52,428,800 bytes (52 MB) (Default)	This limit applies to actions that either natively support chunking or let you enable chunking in their runtime configuration. To change the default value in the single-tenant service, review Edit host and app settings for logic apps in single-tenant Azure Logic Apps.

Character limits

Name	Limit	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

Authentication limits

The following table lists the values for a workflow that starts with a Request trigger and enables Microsoft Entra ID Open Authentication (Microsoft Entra ID OAuth) for authorizing inbound calls to the Request trigger:

Name	Limit	Notes
Microsoft Entra authorization policies	5 policies
Claims per authorization policy	10 claims
Claim value - Maximum number of characters	150 characters

Switch action limits

The following table lists the values for a single workflow definition:

Name	Limit	Notes
Maximum number of cases per action	25

Inline Code action limits

The following table lists the values for a single workflow definition:

Name	Multitenant	Single-tenant	Notes
Maximum number of code characters	1,024 characters	100,000 characters	To use the higher limit, create a Standard logic app resource, which runs in single-tenant Azure Logic Apps, either by using the Azure portal or by using Visual Studio Code and the Azure Logic Apps (Standard) extension.
Maximum duration for running code	5 sec	15 sec	To use the higher limit, create a Standard logic app resource, which runs in single-tenant Azure Logic Apps, either by using the Azure portal or by using Visual Studio Code and the Azure Logic Apps (Standard) extension.

Custom connector limits

In multitenant Azure Logic Apps only, you can create and use custom managed connectors, which are wrappers around an existing REST API or SOAP API. In single-tenant Azure Logic Apps, you can create and use only custom built-in connectors.

The following table lists the values for custom connectors:

Name	Multitenant	Single-tenant
Custom connectors	1,000 per Azure subscription	Unlimited
APIs per service	SOAP-based: 50	Not applicable
Parameters per API	SOAP-based: 50	Not applicable
Requests per minute for a custom connector	500 requests per minute per connection	Based on your implementation
Connection timeout	2 min	Idle connection: 4 min Active connection: 10 min

For more information, review the following documentation:

Managed identity limits

Name	Limit
Managed identities per logic app resource	- Consumption: Either the system-assigned identity or only one user-assigned identity - Standard: The system-assigned identity and any number of user-assigned identities Note: By default, a Logic App (Standard) resource has the system-assigned managed identity automatically enabled to authenticate connections at runtime. This identity differs from the authentication credentials or connection string that you use when you create a connection. If you disable this identity, connections won't work at runtime. To view this setting, on your logic app's menu, under Settings, select Identity.
Number of logic apps that have a managed identity in an Azure subscription per region	- Consumption: 5,000 logic apps - Standard: Per Azure App Service limits, if any

Name

Limit

Managed identities per logic app resource

- Consumption: Either the system-assigned identity or only one user-assigned identity

- Standard: The system-assigned identity and any number of user-assigned identities

Note: By default, a Logic App (Standard) resource has the system-assigned managed identity automatically enabled to authenticate connections at runtime. This identity differs from the authentication credentials or connection string that you use when you create a connection. If you disable this identity, connections won't work at runtime. To view this setting, on your logic app's menu, under Settings, select Identity.

Number of logic apps that have a managed identity in an Azure subscription per region

- Consumption: 5,000 logic apps
- Standard: Per Azure App Service limits, if any

Integration account limits

Each Azure subscription has these integration account limits:

One Free tier integration account per Azure region. This tier is available only for public regions in Azure, for example, West US or Southeast Asia, but not for Microsoft Azure operated by 21Vianet or Azure Government.
1,000 total integration accounts

To learn how pricing and billing work, see the Logic Apps pricing model. For pricing rates, see Logic Apps pricing.

Artifact limits per integration account

The following tables list the values for the number of artifacts limited to 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	Premium (preview)
EDI trading agreements	10	1	1,000	Unlimited
EDI trading partners	25	2	1,000	Unlimited
Maps	25	500	1,000	Unlimited
Schemas	25	500	1,000	Unlimited
Assemblies	10	25	1,000	Unlimited, but currently unsupported for export from an integration service environment.
Certificates	25	2	1,000	Unlimited
Batch configurations	5	1	50	Unlimited
RosettaNet partner interface process (PIP)	10	1	500	Unlimited, but currently unsupported for export from an integration service environment.

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 min	3,000	30,000	60,000	This limit applies to calls that get the raw inputs and outputs from a logic app's run history. You can distribute the workload across more than one account as necessary.
Invoke calls per 5 min	3,000	30,000	45,000	You can distribute the workload across more than one account as necessary.
Tracking calls per 5 min	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

The following table lists the message size limits that apply to B2B protocols:

Name	Multitenant	Single-tenant	Notes
AS2	v2 - 100 MB v1 - 25 MB	Unavailable	Applies to decode and encode
X12	50 MB	Unavailable	Applies to decode and encode
EDIFACT	50 MB	Unavailable	Applies to decode and encode

Firewall configuration: IP addresses and service tags

If your environment has strict network requirements and uses a firewall that limits traffic to specific IP addresses, your environment or firewall needs to permit incoming communication received by Azure Logic Apps and outgoing communication sent by Azure Logic Apps. To set up this access, you can create Azure Firewall rules for your firewall to allow access for both inbound and outbound IP addresses used by Azure Logic Apps in your logic app's Azure region. All logic apps in the same region use the same IP address ranges.

Note

If you're using Power Automate, some actions, such as HTTP and HTTP + OpenAPI, go directly through the Azure Logic Apps service and come from the IP addresses that are listed here. For more information about the IP addresses used by Power Automate, see Limits and configuration for Power Automate.

For example, suppose your logic apps are deployed in the West US region. To support calls that your logic apps send or receive through built-in triggers and actions, such as the HTTP trigger or action, your firewall needs to allow access for all the Azure Logic Apps service inbound IP addresses and outbound IP addresses that exist in the West US region.

If your workflow uses managed connectors, such as the Office 365 Outlook connector or SQL connector, or uses custom connectors, the firewall also needs to allow access for all the managed connector outbound IP addresses in your logic app's Azure region. If your workflow uses custom connectors that access on-premises resources through the on-premises data gateway resource in Azure, you need to set up the gateway installation to allow access for the corresponding managed connector outbound IP addresses. For more information about setting up communication settings on the gateway, review these topics:

Firewall IP configuration considerations

Before you set up your firewall with IP addresses, review these considerations:

To help you simplify any security rules that you want to create, you can optionally use service tags instead, rather than specify IP address prefixes for each region. These tags represent a group of IP address prefixes from a specific Azure service and work across the regions where the Azure Logic Apps service is available:
- LogicAppsManagement: Represents the inbound IP address prefixes for the Azure Logic Apps service.
- LogicApps: Represents the outbound IP address prefixes for the Azure Logic Apps service.
- AzureConnectors: Represents the IP address prefixes for managed connectors that make inbound webhook callbacks to the Azure Logic Apps service and outbound calls to their respective services, such as Azure Storage or Azure Event Hubs.
For Standard logic app workflows that run in single-tenant Azure Logic Apps, you have to allow access for any trigger or action connections in your workflows. You can allow traffic from service tags and use the same level of restrictions or policies as Azure App Service. You also need to find and use the fully qualified domain names (FQDNs) for your connections. For more information, review the corresponding sections in the following documentation:
- Firewall permissions for single tenant logic apps - Azure portal
- Firewall permissions for single tenant logic apps - Visual Studio Code
If your logic apps have problems accessing Azure storage accounts that use firewalls and firewall rules, you have various other 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

For Azure Logic Apps to receive incoming communication through your firewall, you have to allow traffic through the inbound IP addresses described in this section for your logic app's Azure region. To help reduce complexity when you create security rules, you can optionally use the service tag, LogicAppsManagement, rather than specify the Azure Logic Apps inbound IP address prefixes for each region. If you're using Azure Government, see Azure Government - Inbound IP addresses.

Note

Some managed connectors make inbound webhook callbacks to Azure Logic Apps. If you use access control on the logic app resource, you must make sure that the calls from these target systems (IP addresses) have permissions to access your logic app. The following connectors make inbound webhook callbacks to Azure Logic Apps:

Adobe Creative Cloud, Adobe Sign, Adobe Sign Demo, Adobe Sign Preview, Adobe Sign Stage, Microsoft Sentinel, Event Grid, Microsoft Form, Business Central, Calendly, Common Data Service, DocuSign, DocuSign Demo, Dynamics 365 for Fin & Ops, LiveChat, Office 365* Outlook, Outlook.com, Parserr, SAP*, Shifts for Microsoft Teams, Teamwork Projects, Typeform, and so on:

Office 365: The return caller is actually the Office 365 connector. You can specify the managed connector outbound IP address prefixes for each region, or optionally, you can use the AzureConnectors service tag for these managed connectors.
SAP: The return caller depends on whether the deployment environment is either multitenant Azure. In the multitenant environment, the on-premises data gateway makes the call back to the Azure Logic Apps service.

Multitenant - Inbound IP addresses

Region	Azure Logic Apps IP
Australia East	13.75.153.66, 104.210.89.222, 104.210.89.244, 52.187.231.161, 20.53.94.103, 20.53.107.215, 20.11.76.135, 20.11.77.54, 4.200.57.191, 20.11.77.111, 4.200.48.30, 4.198.185.192, 4.200.48.37, 4.200.57.70
Australia Southeast	13.73.115.153, 40.115.78.70, 40.115.78.237, 52.189.216.28, 52.255.42.110, 20.70.114.64, 20.211.194.165, 20.70.118.30, 4.198.78.245, 20.70.114.85, 20.70.116.201, 20.92.62.87, 20.211.194.79, 20.92.62.64
Brazil South	191.235.86.199, 191.235.95.229, 191.235.94.220, 191.234.166.198, 20.201.66.147, 20.201.25.72, 20.201.111.44, 20.201.110.210, 20.201.95.184, 20.201.111.106, 20.201.110.239, 20.201.111.218, 20.201.111.204, 4.228.78.206
Brazil Southeast	20.40.32.59, 20.40.32.162, 20.40.32.80, 20.40.32.49, 20.206.42.14, 20.206.43.33, 108.140.19.183, 108.140.16.189, 108.140.19.38, 108.140.17.2, 108.140.19.189, 108.140.20.8, 108.140.19.206, 108.140.20.2
Canada Central	13.88.249.209, 52.233.30.218, 52.233.29.79, 40.85.241.105, 20.104.14.9, 20.48.133.182, 20.175.241.90, 20.116.229.122, 4.172.59.88, 52.237.58.32, 20.116.231.233, 20.116.229.68, 4.172.57.90, 20.116.230.165
Canada East	52.232.129.143, 52.229.125.57, 52.232.133.109, 40.86.202.42, 20.200.63.149, 52.229.126.142, 40.86.205.75, 40.86.229.191, 40.69.102.29, 40.69.96.69, 40.86.248.230, 52.229.114.121, 20.220.76.245, 52.229.99.183
Central India	52.172.157.194, 52.172.184.192, 52.172.191.194, 104.211.73.195, 20.204.203.110, 20.204.212.77, 4.186.8.164, 20.235.200.244, 20.235.200.100, 20.235.200.92, 4.188.187.112, 4.188.187.170, 4.188.187.173, 4.188.188.52
Central US	13.67.236.76, 40.77.111.254, 40.77.31.87, 104.43.243.39, 13.86.98.126, 20.109.202.37
East Asia	168.63.200.173, 13.75.89.159, 23.97.68.172, 40.83.98.194, 20.187.254.129, 20.187.189.246, 20.6.149.94, 4.144.32.35, 20.255.186.54, 20.6.149.151, 20.255.121.88, 20.255.104.187, 20.255.121.57, 20.6.177.230
East US	137.135.106.54, 40.117.99.79, 40.117.100.228, 137.116.126.165, 52.226.216.209, 40.76.151.124, 20.84.29.150, 40.76.174.148, 4.156.26.80, 4.156.25.14, 4.156.25.189, 20.242.168.44, 4.156.241.183, 4.156.243.174, 4.156.242.86, 4.156.243.165, 52.224.145.162, 4.156.242.96, 4.156.243.173, 4.156.241.195, 4.156.242.97, 4.156.242.26, 4.156.242.13, 172.212.37.35
East US 2	40.84.25.234, 40.79.44.7, 40.84.59.136, 40.70.27.253, 20.96.58.28, 20.96.89.98, 20.96.90.28, 20.122.237.191, 52.251.20.210, 20.122.237.232, 20.122.237.221, 4.152.129.54, 4.152.128.241, 20.1.240.241, 4.152.129.229, 4.152.127.230, 4.152.126.158, 4.153.195.56, 4.153.201.240
France Central	52.143.162.83, 20.188.33.169, 52.143.156.55, 52.143.158.203, 20.40.139.209, 51.11.237.239, 20.74.20.86, 20.74.22.248, 20.74.94.80, 20.74.91.234, 20.74.106.82, 20.74.35.121, 20.19.63.163, 20.19.56.186
France South	52.136.131.145, 52.136.129.121, 52.136.130.89, 52.136.131.4, 52.136.134.128, 52.136.143.218, 51.138.154.147, 51.138.152.107, 51.138.154.171, 51.138.154.241, 51.138.154.167, 51.138.152.46, 51.138.154.191, 51.138.154.153
Germany North	51.116.211.29, 51.116.208.132, 51.116.208.37, 51.116.208.64, 20.113.206.147, 20.113.197.46, 20.218.25.193, 20.218.25.211, 20.218.26.154, 20.218.26.185, 20.218.40.222, 20.218.41.149, 20.218.40.115, 20.218.41.77
Germany West Central	51.116.168.222, 51.116.171.209, 51.116.233.40, 51.116.175.0, 20.113.12.69, 20.113.11.8, 98.67.210.83, 98.67.210.94, 98.67.210.49, 98.67.144.141, 98.67.146.59, 98.67.145.222, 98.67.146.65, 98.67.146.238
Israel Central	20.217.134.130, 20.217.134.135, 51.4.2.18, 51.4.2.88, 51.4.2.119, 51.4.2.140, 51.4.2.16, 51.4.2.136, 51.4.2.186, 51.4.2.17
Italy North	4.232.12.165, 4.232.12.191, 172.213.177.28, 172.213.177.95, 172.213.177.111, 172.213.196.142, 172.213.199.113, 172.213.193.254, 172.213.199.195, 172.213.198.5
Japan East	13.71.146.140, 13.78.84.187, 13.78.62.130, 13.78.43.164, 20.191.174.52, 20.194.207.50, 20.18.198.232, 20.18.197.179, 20.18.198.148, 20.18.238.86, 4.189.8.207, 4.189.9.80, 4.189.10.88, 4.189.8.209
Japan West	40.74.140.173, 40.74.81.13, 40.74.85.215, 40.74.68.85, 20.89.226.241, 20.89.227.25, 40.74.129.115, 138.91.22.178, 40.74.120.8, 138.91.27.244, 138.91.28.97, 138.91.26.244, 23.100.110.250, 138.91.27.82
Jio India West	20.193.206.48, 20.193.206.49, 20.193.206.50, 20.193.206.51, 20.193.173.174, 20.193.168.121, 20.207.247.103, 20.244.240.200, 20.244.244.210, 20.244.241.129, 20.244.240.7, 20.244.242.21, 20.244.247.29, 20.244.244.219
Korea Central	52.231.14.182, 52.231.103.142, 52.231.39.29, 52.231.14.42, 20.200.207.29, 20.200.231.229, 20.249.169.92, 20.249.169.87, 20.249.169.155, 20.249.171.205, 4.230.149.190, 20.249.170.248, 20.249.171.120, 20.249.171.7
Korea South	52.231.166.168, 52.231.163.55, 52.231.163.150, 52.231.192.64, 20.200.177.151, 20.200.177.147, 52.231.228.78, 52.231.181.100, 52.231.223.213, 52.231.140.232, 52.231.228.60, 52.231.143.60, 52.231.138.189, 52.231.137.253
North Central US	168.62.249.81, 157.56.12.202, 65.52.211.164, 65.52.9.64, 52.162.177.104, 23.101.174.98, 20.98.61.245, 172.183.50.180, 172.183.52.146, 172.183.51.138, 172.183.48.31, 172.183.48.9, 172.183.48.234, 40.116.65.34
North Europe	13.79.173.49, 52.169.218.253, 52.169.220.174, 40.112.90.39, 40.127.242.203, 51.138.227.94, 40.127.145.51, 40.67.252.16, 4.207.0.242, 4.207.204.28, 4.207.203.201, 20.67.143.247, 20.67.138.43, 68.219.40.237, 20.105.14.98, 4.207.203.15, 4.207.204.121, 4.207.201.247, 20.107.145.46
Norway East	51.120.88.93, 51.13.66.86, 51.120.89.182, 51.120.88.77, 20.100.27.17, 20.100.36.102, 4.235.15.184, 4.235.37.41, 4.235.38.187, 4.235.15.175, 4.235.39.110, 4.235.38.223, 4.235.39.218, 20.251.128.60
Norway West	51.120.220.160, 51.120.220.161, 51.120.220.162, 51.120.220.163, 51.13.155.184, 51.13.151.90, 20.100.74.215, 20.100.75.243, 20.100.74.245, 20.100.75.51, 20.100.72.6, 20.100.74.37, 20.100.72.154, 20.100.76.68
Poland Central	20.215.144.231, 20.215.145.0, 74.248.82.221, 74.248.82.188, 74.248.83.27, 74.248.83.63, 74.248.81.204, 74.248.81.64, 74.248.81.229, 74.248.81.255
Qatar Central	20.21.211.241, 20.21.211.242
South Africa North	102.133.228.4, 102.133.224.125, 102.133.226.199, 102.133.228.9, 20.87.92.64, 20.87.91.171, 20.164.165.201, 20.164.166.18, 20.164.167.236, 20.164.56.217, 20.164.151.72, 20.164.147.113, 20.164.48.40, 20.164.148.191
South Africa West	102.133.72.190, 102.133.72.145, 102.133.72.184, 102.133.72.173, 40.117.9.225, 102.133.98.91, 20.87.177.187, 102.133.70.42, 20.87.176.228, 20.87.178.76, 20.87.176.32, 20.87.176.245, 20.87.176.215, 20.87.178.32
South Central US	13.65.98.39, 13.84.41.46, 13.84.43.45, 40.84.138.132, 20.94.151.41, 20.88.209.113, 172.206.187.62, 172.206.187.92, 172.206.187.101, 172.206.187.135, 52.255.127.211, 52.255.127.201, 52.255.127.24, 52.255.127.243
South India	52.172.9.47, 52.172.49.43, 52.172.51.140, 104.211.225.152, 104.211.221.215,104.211.205.148, 52.140.4.233, 52.172.100.99, 52.140.5.154, 52.140.1.153, 52.172.96.103, 52.140.2.150, 52.172.103.116, 52.172.99.31
Southeast Asia	52.163.93.214, 52.187.65.81, 52.187.65.155, 104.215.181.6, 20.195.49.246, 20.198.130.155, 23.98.121.180, 4.144.200.166, 4.144.203.255, 4.144.203.73, 4.144.201.132, 20.247.196.3, 52.230.58.240, 20.247.197.6, 20.247.198.8, 20.247.195.123, 20.247.197.207, 20.247.197.108, 20.247.198.132
Spain Central	68.221.3.54, 68.221.3.29, 68.221.249.214, 68.221.249.187, 68.221.249.249, 68.221.249.208, 68.221.249.227, 68.221.250.1, 68.221.249.191
Sweden Central	20.91.178.13, 20.240.10.125, 74.241.204.72, 74.241.204.55, 74.241.204.197, 74.241.206.0, 4.225.198.176, 4.225.198.50, 4.225.197.219, 4.225.198.33
Switzerland North	51.103.128.52, 51.103.132.236, 51.103.134.138, 51.103.136.209, 20.203.230.170, 20.203.227.226, 4.226.35.171, 20.250.239.241, 20.250.238.113, 20.250.238.80, 20.250.233.38, 20.250.235.79, 20.250.235.177, 20.250.235.117
Switzerland West	51.107.225.180, 51.107.225.167, 51.107.225.163, 51.107.239.66, 51.107.235.139,51.107.227.18, 20.199.218.139, 20.199.219.180, 20.199.216.255, 20.199.217.34, 20.208.231.200, 20.199.217.39, 20.199.216.16, 20.199.216.98
UAE Central	20.45.75.193, 20.45.64.29, 20.45.64.87, 20.45.71.213, 40.126.212.77, 40.126.209.97, 40.125.29.71, 40.125.28.162, 40.125.25.83, 40.125.24.49, 40.125.3.59, 40.125.3.137, 40.125.2.220, 40.125.3.139
UAE North	20.46.42.220, 40.123.224.227, 40.123.224.143, 20.46.46.173, 20.74.255.147, 20.74.255.37, 20.233.241.162, 20.233.241.99, 20.174.64.131, 20.233.241.184, 20.174.48.155, 20.233.241.200, 20.174.56.89, 20.174.41.1
UK South	51.140.79.109, 51.140.78.71, 51.140.84.39, 51.140.155.81, 20.108.102.180, 20.90.204.232, 20.108.148.173, 20.254.10.157, 4.159.25.35, 4.159.25.50, 4.250.87.43, 4.158.106.183, 4.250.53.153, 4.159.26.160, 4.159.25.103, 4.159.59.224, 4.158.138.59, 85.210.163.36, 85.210.34.209, 85.210.36.40, 85.210.185.43
UK West	51.141.48.98, 51.141.51.145, 51.141.53.164, 51.141.119.150, 51.104.62.166, 51.141.123.161, 20.162.86.241, 20.162.87.200, 51.141.80.175, 20.162.87.253, 20.254.244.41, 20.254.244.108, 20.254.241.7, 20.254.245.81
West Central US	52.161.26.172, 52.161.8.128, 52.161.19.82, 13.78.137.247, 52.161.64.217, 52.161.91.215, 20.165.255.229, 4.255.162.134, 20.165.228.184, 4.255.178.108, 20.165.225.209, 4.255.145.22, 20.165.245.151, 20.165.232.221
West Europe	13.95.155.53, 52.174.54.218, 52.174.49.6, 20.103.21.113, 20.103.18.84, 20.103.57.210, 20.101.174.52, 20.93.236.81, 20.103.94.255, 20.82.87.229, 20.76.171.34, 20.103.84.61, 98.64.193.78, 98.64.194.143, 98.64.198.223, 98.64.198.203, 98.64.208.186, 98.64.209.52, 172.211.196.189, 172.211.195.251, 98.64.154.66, 98.64.156.81, 98.64.156.180, 98.64.156.68, 20.238.229.165, 20.8.128.2, 20.238.230.113, 108.141.139.111, 108.142.111.162, 108.142.111.174, 108.142.111.178, 108.142.111.183, 108.142.111.152, 108.142.111.156, 108.142.111.179, 108.142.111.169, 98.64.203.30, 98.64.156.172, 20.56.202.157, 20.56.203.30, 57.153.19.33, 57.153.59.202, 108.141.95.140, 20.61.147.216, 57.153.83.52, 57.153.38.174, 57.153.3.13, 57.153.1.223, 108.142.29.55, 108.142.31.220, 108.142.31.202, 20.61.153.22, 57.153.7.252, 108.141.83.61
West India	104.211.164.112, 104.211.165.81, 104.211.164.25, 104.211.157.237, 104.211.167.12,104.211.166.35
West US	52.160.90.237, 138.91.188.137, 13.91.252.184, 157.56.160.212, 104.40.34.112, 52.160.68.27, 13.88.168.158, 104.42.40.164, 13.87.207.79, 13.87.204.210, 168.62.9.100, 13.88.169.158, 13.88.171.218, 13.91.81.69, 13.64.215.62, 13.83.10.141, 13.91.40.58, 13.91.103.48, 52.160.93.229, 13.93.215.87, 13.88.177.160, 13.88.18.200, 13.91.105.180, 13.91.18.168, 13.83.15.162, 52.160.32.120, 13.91.35.39, 13.93.177.253, 13.93.180.131, 13.93.179.126, 13.91.130.111, 13.64.236.166, 13.64.239.120, 13.93.233.226, 40.83.133.96, 13.93.239.166, 13.64.240.133, 13.86.209.140, 13.91.40.136, 40.112.147.242, 40.112.136.59, 104.42.142.214, 104.42.128.212, 13.91.65.198, 13.93.193.254, 13.93.211.175, 13.91.46.140
West US 2	13.66.224.169, 52.183.30.10, 52.183.39.67, 13.66.128.68, 20.99.190.19, 20.72.244.108, 4.155.163.32, 172.179.145.245, 4.155.162.75, 4.155.164.225, 4.149.68.5, 172.179.155.215, 4.149.68.80, 4.149.68.115
West US 3	20.150.172.240, 20.150.172.242, 20.150.172.243, 20.150.172.241, 20.106.116.172, 20.106.116.225, 4.227.75.85, 4.227.76.97, 4.236.46.212, 4.236.55.100, 4.227.77.19, 4.227.77.224, 4.227.77.128, 4.227.78.227

Azure Government - Inbound IP addresses

Azure Government region	Azure Logic Apps IP
US Gov Arizona	52.244.67.164, 52.244.67.64, 52.244.66.82, 52.126.52.254, 52.126.53.145, 52.244.187.241, 52.244.17.238, 52.244.23.110, 52.244.20.213, 52.244.16.162, 52.244.15.25, 52.244.16.141, 52.244.15.26
US Gov Texas	52.238.119.104, 52.238.112.96, 52.238.119.145, 52.245.171.151, 52.245.163.42, 52.238.78.169, 52.238.164.135, 52.238.164.111, 52.238.164.44, 52.243.250.114, 52.243.248.33, 52.243.253.54, 52.243.253.44
US Gov Virginia	52.227.159.157, 52.227.152.90, 23.97.4.36, 13.77.239.182, 13.77.239.190, 20.159.220.127, 62.10.96.217, 62.10.102.236, 62.10.102.136, 62.10.111.137, 62.10.111.152, 62.10.111.128, 62.10.111.123
US DoD Central	52.182.49.204, 52.182.52.106, 52.182.49.105, 52.182.49.175, 52.180.225.24, 52.180.225.43, 52.180.225.50, 52.180.252.28, 52.180.225.29, 52.180.231.56, 52.180.231.50, 52.180.231.65

Outbound IP addresses

For Azure Logic Apps to send outgoing communication through your firewall, you have to allow traffic in your logic app's Azure region for all the outbound IP addresses described in this section. If you're using 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 the Azure Logic Apps outbound IP address prefixes for each region. Optionally, you can also use the AzureConnectors service tag for managed connectors that make outbound calls to their respective services, such as Azure Storage or Azure Event Hubs, rather than specify the outbound managed connector IP address prefixes for each region. These tags work across the regions where Azure Logic Apps is available.

If your workflow also uses any managed connectors, such as the Office 365 Outlook connector or SQL connector, or uses any custom connectors, your firewall has to allow traffic in your logic app's Azure region for all the managed connector outbound IP addresses. If your workflow uses custom connectors that access on-premises resources through the on-premises data gateway resource in Azure, you need to set up the gateway installation to allow access for the corresponding managed connector outbound IP addresses. For more information about setting up communication settings on the gateway, review these topics:

Multitenant - Outbound IP addresses

This section lists the outbound IP addresses that Azure Logic Apps requires in your logic app's Azure region to communicate through your firewall. Also, if your workflow uses any managed connectors or custom connectors, your firewall has to allow traffic in your logic app's Azure region for all the managed connectors' outbound IP addresses. If you have custom connectors that access on-premises resources through the on-premises data gateway resource in Azure, set up your gateway installation to allow access for the corresponding managed connector outbound IP addresses.

Region	Azure Logic Apps 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, 20.53.93.188, 20.53.72.170, 20.53.107.208, 20.53.106.182, 20.11.76.122, 20.11.77.49, 4.200.57.71, 20.11.77.107, 4.198.187.22, 4.198.185.90, 4.198.185.246, 4.200.58.227
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, 52.255.36.185, 52.158.133.57, 20.70.114.125, 20.70.114.10, 20.70.117.240, 20.70.116.106, 20.70.114.97, 20.211.194.242, 20.70.109.46, 20.11.136.137, 20.70.116.240, 20.211.194.233, 20.11.154.170, 4.198.89.96, 20.92.61.254, 20.70.95.150, 20.70.117.21, 20.211.194.127, 20.92.61.242, 20.70.93.143
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, 20.201.66.44, 20.201.64.135, 20.201.24.212, 191.237.207.21, 20.201.111.36, 20.201.110.208, 20.201.91.95, 20.201.110.244, 20.201.110.234, 20.201.111.212, 20.201.111.203, 4.228.72.24
Brazil Southeast	20.40.32.81, 20.40.32.19, 20.40.32.85, 20.40.32.60, 20.40.32.116, 20.40.32.87, 20.40.32.61, 20.40.32.113, 20.206.41.94, 20.206.41.20, 20.206.42.67, 20.206.40.250, 108.140.19.0, 108.140.16.168, 108.140.17.240, 108.140.17.223, 108.140.19.181, 108.140.20.3, 108.140.19.68, 108.140.16.195
Canada Central	52.233.29.92, 52.228.39.244, 40.85.250.135, 40.85.250.212, 13.71.186.1, 40.85.252.47, 13.71.184.150, 20.104.13.249, 20.104.9.221, 20.48.133.133, 20.48.132.222, 20.175.241.76, 20.116.229.92, 4.172.57.144, 52.237.56.228, 20.116.231.222, 20.116.229.57, 4.172.57.52, 20.116.230.54
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, 20.200.60.151, 20.200.59.228, 52.229.126.67, 52.229.105.109, 40.86.226.221, 40.86.228.72, 40.69.98.14, 40.86.208.137, 40.86.229.179, 40.86.227.188, 40.86.202.35, 40.86.206.74, 52.229.100.167, 40.86.240.237, 40.69.120.161, 40.69.102.71, 20.220.75.33, 20.220.74.16, 40.69.101.66, 52.229.114.105
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, 20.204.204.74, 20.204.202.72, 20.204.212.60, 20.204.212.8, 4.186.8.62, 4.186.8.18, 20.235.200.242, 20.235.200.237, 20.235.200.79, 20.235.200.44, 20.235.200.70, 20.235.200.32, 4.188.187.109, 4.188.187.86, 4.188.187.140, 4.188.185.15, 4.188.187.145, 4.188.187.107, 4.188.187.184, 4.188.187.64
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, 52.141.221.6, 52.141.218.55, 20.109.202.36, 20.109.202.29
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, 20.187.254.110, 20.187.250.221, 20.187.189.47, 20.187.188.136, 20.239.240.181, 20.6.152.201, 20.2.52.61, 20.255.43.37, 20.255.41.243, 4.192.72.182, 20.6.177.234, 20.255.113.33
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, 52.226.216.197, 52.226.216.187, 40.76.151.25, 40.76.148.50, 20.84.29.29, 20.84.29.18, 40.76.174.83, 40.76.174.39, 4.156.27.7, 4.156.28.117, 4.156.25.188, 20.242.168.24, 4.156.241.165, 4.156.243.170, 4.156.242.49, 4.156.243.164, 52.224.145.30, 4.156.242.92, 4.156.243.172, 4.156.241.191, 4.156.241.47, 4.156.241.229, 4.156.242.12, 172.212.32.196
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, 20.96.58.140, 20.96.58.139, 20.96.89.54, 20.96.89.48, 20.96.89.254, 20.96.89.234, 20.122.237.189, 52.253.79.47, 20.122.237.225, 20.122.237.205, 4.152.128.227, 4.152.128.205, 4.153.159.226, 4.152.129.221, 4.152.127.229, 4.152.125.62, 4.153.194.246, 4.153.201.239
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, 20.40.138.112, 20.40.140.149, 51.11.237.219, 51.11.237.216, 20.74.18.58, 20.74.18.36, 20.74.22.121, 20.74.20.147, 20.74.94.62, 20.74.88.179, 20.74.23.87, 20.74.22.119, 20.74.106.61, 20.74.105.214, 20.74.34.113, 20.74.33.177, 20.19.61.105, 20.74.109.28, 20.19.113.120, 20.74.106.31
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, 52.136.139.71, 52.136.135.74, 52.136.133.225, 52.136.139.96, 51.138.154.137, 51.138.153.121, 51.138.152.26, 51.138.155.43, 51.138.154.125, 51.138.153.24, 51.138.152.141, 51.138.152.170
Germany North	51.116.211.168, 51.116.208.165, 51.116.208.175, 51.116.208.192, 51.116.208.200, 51.116.208.222, 51.116.208.217, 51.116.208.51, 20.113.195.253, 20.113.196.183, 20.113.206.134, 20.113.206.170, 20.218.25.86, 20.218.25.112, 20.218.26.84, 20.218.26.28, 20.218.40.124, 20.218.41.137, 20.218.41.177, 20.218.41.117
Germany West Central	51.116.233.35, 51.116.171.49, 51.116.233.33, 51.116.233.22, 51.116.168.104, 51.116.175.17, 51.116.233.87, 51.116.175.51, 20.113.11.136, 20.113.11.85, 20.113.10.168, 20.113.8.64, 98.67.210.79, 98.67.210.78, 98.67.210.85, 98.67.210.84, 98.67.210.14, 98.67.210.24, 98.67.144.136, 98.67.144.122, 98.67.145.221, 98.67.144.207, 98.67.146.88, 98.67.146.81, 98.67.146.51, 98.67.145.122, 98.67.146.229, 98.67.146.218
Israel Central	20.217.134.127, 20.217.134.126, 20.217.134.132, 20.217.129.229, 51.4.1.246, 51.4.2.73, 51.4.2.116, 51.4.2.139, 51.4.2.89, 51.4.0.146, 51.4.2.105, 51.4.2.123
Italy North	4.232.12.164, 4.232.12.173, 4.232.12.190, 4.232.12.169, 172.213.176.243, 172.213.177.89, 172.213.176.130, 172.213.195.126, 172.213.199.94, 172.213.196.10, 172.213.199.179, 172.213.199.115
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, 20.191.172.255, 20.46.187.174, 20.194.206.98, 20.194.205.189, 20.18.198.224, 20.18.197.177, 20.18.198.141, 20.18.238.83, 4.189.14.67, 4.189.8.211, 4.189.9.135, 4.189.8.208
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, 20.89.227.63, 20.89.226.188, 20.89.227.14, 20.89.226.101, 40.74.128.79, 40.74.75.184, 138.91.16.164, 138.91.21.233, 40.74.119.237, 40.74.119.158, 138.91.22.248, 138.91.26.236, 138.91.17.197, 138.91.17.144, 138.91.17.137, 104.46.237.16, 23.100.109.62, 138.91.17.15, 138.91.26.67, 104.46.234.170
Jio India West	20.193.206.128, 20.193.206.129, 20.193.206.130, 20.193.206.131, 20.193.206.132, 20.193.206.133, 20.193.206.134, 20.193.206.135, 20.193.173.7, 20.193.172.11, 20.193.170.88, 20.193.171.252, 20.207.246.213, 20.207.247.91, 20.207.241.77, 20.207.246.218, 20.244.243.50, 20.244.243.105, 20.244.242.55, 20.244.241.138
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, 20.200.206.170, 20.200.202.75, 20.200.231.222, 20.200.231.139, 20.249.169.25, 20.249.169.18, 20.249.169.147, 20.249.171.130, 4.230.149.189, 20.249.169.207, 20.249.171.17, 20.249.169.238
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, 20.200.177.148, 20.200.177.135, 20.200.177.146, 20.200.180.213, 52.231.139.2, 52.231.220.66, 52.231.137.133, 52.231.228.71, 52.231.230.253, 52.231.176.192, 52.231.182.160, 52.231.218.243
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.177.90, 52.162.177.30, 23.101.160.111, 23.101.167.207, 20.80.33.190, 20.88.47.77, 172.183.51.180, 40.116.65.125, 20.88.51.31, 40.116.66.226, 40.116.64.218, 20.88.55.77, 172.183.49.208, 20.102.251.70, 20.102.255.252, 20.88.49.23, 172.183.50.30, 20.88.49.21, 20.102.255.209, 172.183.48.255
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, 40.127.242.159, 40.127.240.183, 51.138.226.19, 51.138.227.160, 40.127.144.251, 40.127.144.121, 40.67.251.175, 40.67.250.247, 4.207.0.229, 4.207.0.197, 4.207.204.8, 4.207.203.217, 4.207.203.190, 4.207.203.59, 20.67.141.244, 20.67.139.133, 20.67.137.144, 20.67.136.162, 68.219.40.225, 68.219.40.39, 20.105.12.63, 20.105.11.53, 4.207.202.106, 4.207.202.95, 4.207.204.91, 4.207.204.89, 4.207.201.234, 20.105.15.225, 20.67.191.232, 20.67.190.37
Norway East	51.120.88.52, 51.120.88.51, 51.13.65.206, 51.13.66.248, 51.13.65.90, 51.13.65.63, 51.13.68.140, 51.120.91.248, 20.100.26.148, 20.100.26.52, 20.100.36.49, 20.100.36.10 , 4.235.15.181, 4.235.33.240, 4.235.38.121, 4.235.9.253, 4.235.39.107, 4.235.36.134, 4.235.39.215, 4.235.39.238
Norway West	51.120.220.128, 51.120.220.129, 51.120.220.130, 51.120.220.131, 51.120.220.132, 51.120.220.133, 51.120.220.134, 51.120.220.135, 51.13.153.172, 51.13.148.178, 51.13.148.11, 51.13.149.162, 20.100.72.232, 20.100.75.45, 20.100.75.97, 20.100.74.217, 20.100.73.211, 20.100.72.17, 20.100.75.141, 20.100.76.234
Poland Central	20.215.144.229, 20.215.128.160, 20.215.144.235, 20.215.144.246, 74.248.82.189, 74.248.82.58, 74.248.82.253, 74.248.82.216, 74.248.81.148, 74.248.81.46, 74.248.81.211, 74.248.81.234
Qatar Central	20.21.211.240, 20.21.209.216, 20.21.211.245, 20.21.210.251
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, 20.87.92.40, 20.87.91.122, 20.87.91.169, 20.87.88.47, 20.164.165.13, 20.164.165.213, 20.164.167.181, 20.164.56.150, 20.164.151.35, 20.164.48.78, 20.164.48.26, 20.164.48.152
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, 102.133.101.220, 40.117.9.125, 40.117.10.230, 40.117.9.229, 20.87.177.51, 102.133.70.122, 20.87.178.214, 20.87.177.83, 20.87.176.146, 20.87.178.80, 20.87.177.204, 20.87.177.252
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, 20.94.150.220, 20.94.149.199, 20.88.209.97, 20.88.209.88, 172.206.187.57, 172.206.187.90, 172.206.187.98, 172.206.187.132, 52.255.124.118, 52.255.127.125, 52.255.126.229, 52.255.127.233
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, 104.211.211.221, 104.211.210.192, 104.211.213.78, 104.211.218.202, 52.172.101.114, 52.172.101.181, 52.140.5.116, 52.172.98.23, 52.140.2.252, 52.140.0.225, 52.140.7.114, 52.172.101.204
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, 20.195.49.240, 20.195.49.29, 20.198.130.152, 20.198.128.124, 23.98.121.179, 23.98.121.115, 4.144.203.116, 4.144.203.254, 4.144.203.72, 4.144.204.223, 20.247.192.203, 20.247.192.18, 20.247.197.137, 20.247.197.3, 20.247.196.123, 20.247.197.249, 20.247.195.111, 20.247.195.8, 20.247.197.146, 20.247.197.100, 20.247.197.40, 20.247.198.128, 20.247.198.96
Spain Central	68.221.3.7, 68.221.1.175, 68.221.2.156, 68.221.2.37, 68.221.249.177, 68.221.249.251, 68.221.249.213, 68.221.249.186, 68.221.249.215, 68.221.249.210, 68.221.249.185, 68.221.249.203, 68.221.249.175, 68.221.249.229, 68.221.249.205, 68.221.249.184, 68.221.249.202, 68.221.249.209, 68.221.249.252, 68.221.250.2
Sweden Central	20.91.178.11, 20.91.177.115, 20.240.10.91, 20.240.10.89, 74.241.204.65, 74.241.204.35, 74.241.204.193, 74.241.205.139, 4.225.198.80, 4.225.198.41, 74.241.203.136, 4.225.198.14
Switzerland North	51.103.137.79, 51.103.135.51, 51.103.139.122, 51.103.134.69, 51.103.138.96, 51.103.138.28, 51.103.136.37, 51.103.136.210, 20.203.230.58, 20.203.229.127, 20.203.224.37, 20.203.225.242, 4.226.35.166, 20.250.239.202, 20.250.239.33, 20.250.239.55, 20.250.233.27, 20.250.235.76, 20.250.235.169, 20.250.235.96
Switzerland West	51.107.239.66, 51.107.231.86, 51.107.239.112, 51.107.239.123, 51.107.225.190, 51.107.225.179, 51.107.225.186, 51.107.225.151, 51.107.239.83, 51.107.232.61, 51.107.234.254, 51.107.226.253, 20.199.193.249, 20.199.217.37, 20.199.219.154, 20.199.216.246, 20.199.219.21, 20.208.230.30, 20.199.216.63, 20.199.218.36, 20.199.216.44
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, 40.126.210.93, 40.126.209.151, 40.126.208.156, 40.126.214.92, 40.125.28.217, 40.125.28.159, 40.125.25.44, 40.125.29.66, 40.125.3.49, 40.125.3.66, 40.125.3.111, 40.125.3.63
UAE North	40.123.230.45, 40.123.231.179, 40.123.231.186, 40.119.166.152, 40.123.228.182, 40.123.217.165, 40.123.216.73, 40.123.212.104, 20.74.255.28, 20.74.250.247, 20.216.16.75, 20.74.251.30, 20.233.241.106, 20.233.241.102, 20.233.241.85, 20.233.241.25, 20.174.64.128, 20.174.64.55, 20.233.240.41, 20.233.241.206, 20.174.48.149, 20.174.48.147, 20.233.241.187, 20.233.241.165, 20.174.56.83, 20.174.56.74, 20.174.40.222, 20.174.40.91
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, 20.108.102.142, 20.108.102.123, 20.90.204.228, 20.90.204.188, 20.108.146.132, 20.90.223.4, 20.26.15.70, 20.26.13.151, 4.159.24.241, 4.250.55.134, 4.159.24.255, 4.250.55.217, 172.165.88.82, 4.250.82.111, 4.158.106.101, 4.158.105.106, 4.250.51.127, 4.250.49.230, 4.159.26.128, 172.166.86.30, 4.159.26.151, 4.159.26.77, 4.159.59.140, 4.159.59.13, 85.210.65.206, 85.210.120.102, 4.159.57.40, 85.210.66.97, 20.117.192.192
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.104.58.40, 51.104.57.160, 51.141.121.72, 51.141.121.220, 20.162.84.125, 20.162.86.120, 51.141.86.225, 20.162.80.198, 20.254.242.187, 20.254.242.213, 20.254.244.189, 20.254.245.102
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.199.128 - 13.71.199.159, 13.78.212.163, 13.77.220.134, 13.78.200.233, 13.77.219.128, 52.150.226.148, 4.255.161.16, 4.255.195.186, 4.255.168.251, 4.255.219.152, 20.165.235.148, 20.165.249.200, 20.165.232.68
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.71.160, 13.69.71.161, 13.69.71.162, 13.69.71.163, 13.69.71.164, 13.69.71.165, 13.69.71.166, 13.69.71.167, 20.103.21.81, 20.103.17.247, 20.103.17.223, 20.103.16.47, 20.103.58.116, 20.103.57.29, 20.101.174.49, 20.101.174.23, 20.93.236.26, 20.93.235.107, 20.103.94.250, 20.76.174.72, 20.82.87.192, 20.82.87.16, 20.76.170.145, 20.103.91.39, 20.103.84.41, 20.76.161.156, 98.64.193.64, 98.64.194.135, 98.64.198.219, 98.64.198.194, 98.64.208.46, 98.64.209.43, 172.211.196.188, 172.211.195.181, 98.64.157.37, 98.64.156.69, 98.64.156.152, 98.64.156.62, 20.238.229.108, 108.141.139.225, 20.238.230.87, 108.141.139.80, 108.142.111.161, 108.142.111.173, 108.142.111.175, 108.142.111.182, 108.142.111.151, 108.142.111.155, 108.142.111.157, 108.142.111.167, 98.64.203.5, 98.64.156.150, 20.56.202.134, 20.56.202.244, 57.153.19.27, 57.153.59.193, 108.141.95.129, 20.61.147.200, 57.153.83.40, 57.153.38.60, 57.153.2.162, 57.153.1.215, 108.142.24.182, 108.142.31.170, 108.142.31.143, 20.61.152.226, 57.153.7.245, 108.141.83.46
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.155.179, 104.211.142.119, 104.211.153.240, 104.211.156.193
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, 13.86.223.0, 13.86.223.1, 13.86.223.2, 13.86.223.3, 13.86.223.4, 13.86.223.5, 104.40.34.169, 104.40.32.148, 52.160.70.221, 52.160.70.105, 13.91.81.221, 13.64.231.196, 13.87.204.182, 40.78.65.193, 13.87.207.39, 104.42.44.28, 40.83.134.97, 40.78.65.112, 168.62.9.74, 168.62.28.191, 13.91.81.188, 13.88.169.213, 13.64.224.17, 13.91.70.215, 13.83.14.75, 13.91.231.159, 13.91.102.122, 52.160.94.54, 13.91.17.147, 13.93.163.29, 13.93.223.133, 13.88.19.4, 13.91.33.16, 13.91.247.124, 52.160.39.166, 13.91.20.94, 13.93.180.161, 13.93.161.57, 13.93.183.170, 13.93.180.221, 13.64.236.222, 13.64.237.74, 13.93.203.72, 13.88.56.138, 13.93.239.25, 13.83.10.112, 13.64.241.219, 13.64.243.209, 104.42.134.185, 40.112.138.23, 104.42.226.197, 104.42.129.159, 13.91.87.195, 13.93.167.155, 13.91.46.132, 13.91.247.104
West US 2	13.66.210.167, 52.183.30.169, 52.183.29.132, 13.66.201.169, 13.77.149.159, 52.175.198.132, 13.66.246.219, 20.99.189.158, 20.99.189.70, 20.72.244.58, 20.72.243.225, 4.155.162.242, 172.179.145.85, 4.155.163.91, 4.155.160.115, 4.149.67.227, 172.179.155.210, 4.149.68.65, 4.149.68.107
West US 3	20.150.181.32, 20.150.181.33, 20.150.181.34, 20.150.181.35, 20.150.181.36, 20.150.181.37, 20.150.181.38, 20.150.173.192, 20.106.85.228, 20.150.159.163, 20.106.116.207, 20.106.116.186, 4.227.74.141, 4.227.76.10, 4.236.45.223, 4.236.55.86, 4.227.76.180, 4.227.77.218, 4.227.77.116, 4.227.78.222

Azure Government - Outbound IP addresses

Region	Azure Logic Apps IP
US DoD Central	52.182.48.215, 52.182.92.143, 52.182.53.147, 52.182.52.212, 52.182.49.162, 52.182.49.151, 52.180.225.0, 52.180.251.16, 52.180.250.135, 52.180.251.20, 52.180.231.89, 52.180.224.251, 52.180.252.222, 52.180.225.21
US Gov Arizona	52.244.67.143, 52.244.65.66, 52.244.65.190, 52.126.50.197, 52.126.49.223, 52.126.53.144, 52.126.36.100, 52.244.187.5, 52.244.19.121, 52.244.18.105, 52.244.51.113, 52.244.17.113, 52.244.26.122, 52.244.22.195, 52.244.19.137
US Gov Texas	52.238.114.217, 52.238.115.245, 52.238.117.119, 20.141.120.209, 52.245.171.152, 20.141.123.226, 52.245.163.1, 52.238.164.53, 52.238.72.216, 52.238.164.123, 52.238.160.255, 52.243.237.44, 52.249.101.31, 52.243.251.37, 52.243.252.22
US Gov Virginia	13.72.54.205, 52.227.138.30, 52.227.152.44, 13.77.239.177, 13.77.239.140, 13.77.239.187, 13.77.239.184, 20.159.219.180, 62.10.96.177, 62.10.102.138, 62.10.102.94, 62.10.111.134, 62.10.111.151, 62.10.110.102, 62.10.109.190

แชร์ผ่าน

Limits and configuration reference for Azure Logic Apps

Workflow definition limits

Run duration and history retention limits

Change run duration and history retention in storage

Portal

ARM template

Looping, concurrency, and debatching limits

Loop actions

For each loop

Until loop

Concurrency and debatching

Throughput limits

Scale for high throughput

Enable high throughput in the portal

Enable high throughput in a Resource Manager template

Data gateway limits

Retry policy limits

Variables action limits

HTTP request limits

Timeout duration

Request trigger and webhook trigger size limits

Messages

Character limits

Authentication limits

Switch action limits

Inline Code action limits

Custom connector limits

Managed identity limits

Integration account limits

Artifact limits per integration account

Artifact capacity limits

Throughput limits

B2B protocol (AS2, X12, EDIFACT) message size

Firewall configuration: IP addresses and service tags

Firewall IP configuration considerations

Inbound IP addresses

Multitenant - Inbound IP addresses

Azure Government - Inbound IP addresses

Outbound IP addresses

Multitenant - Outbound IP addresses

Azure Government - Outbound IP addresses

Next steps

คำติชม

แหล่งทรัพยากรเพิ่มเติม