Limits and configuration information for Azure Logic Apps

• 11/19/2019
• 15 minutes to read
• • 
  • 
  • 
  • 
  • 
  • +17

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:

Run duration and retention limits

Here are the limits for a single logic app run:

Change run duration and storage retention

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

1. In the Azure portal, on your logic app's menu, select Workflow settings.

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

3. Enter or drag the slider for the number of days that you want.

   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.

Concurrency, looping, and debatching limits

Here are the limits for a single logic app run:

Throughput limits

Here are the limits for a single logic app definition:

Multi-tenant Logic Apps service

Integration service environment (ISE)

Here are the throughput limits for the Premium SKU:

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.

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.

Message size

Retry policy

Custom connector limits

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

Managed identities

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.

Artifact capacity limits

B2B protocol (AS2, X12, EDIFACT) message size

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

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

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 that are in the same region use the same IP address ranges.

• 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 Microsoft-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.

• For custom connectors, Azure Government, and Azure China 21Vianet, fixed or reserved IP addresses aren't available.

Inbound IP addresses - Logic Apps service only

Outbound IP addresses - Logic Apps service & managed connectors

Next steps

• Learn how to create your first logic app
• Learn about common examples and scenarios