You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/logic-apps/logic-apps-limits-and-config.md
+13-14Lines changed: 13 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -3,9 +3,9 @@ title: Limits and configuration
3
3
description: Service limits, such as duration, throughput, and capacity, plus configuration values, such as IP addresses to allow, for Azure Logic Apps
4
4
services: logic-apps
5
5
ms.suite: integration
6
-
ms.reviewer: klam, logicappspm
6
+
ms.reviewer: jonfan, logicappspm
7
7
ms.topic: article
8
-
ms.date: 03/12/2020
8
+
ms.date: 04/17/2020
9
9
---
10
10
11
11
# Limits and configuration information for Azure Logic Apps
@@ -107,7 +107,7 @@ Here are the limits for a single logic app definition:
107
107
108
108
### Integration service environment (ISE)
109
109
110
-
Here are the throughput limits for the Premium SKU:
110
+
Here are the throughput limits for the [Premium ISE SKU](../logic-apps/connect-virtual-network-vnet-isolated-environment-overview.md#ise-level):
111
111
112
112
| Name | Limit | Notes |
113
113
|------|-------|-------|
@@ -119,9 +119,9 @@ Here are the throughput limits for the Premium SKU:
119
119
To go above these limits in normal processing, or run load testing that might go above these limits, [contact the Logic Apps team](mailto://[email protected]) for help with your requirements.
120
120
121
121
> [!NOTE]
122
-
> The [Developer SKU](../logic-apps/connect-virtual-network-vnet-isolated-environment-overview.md#ise-level)has no published limits as this SKU
123
-
> doesn't have any service-level agreement (SLA) or capabilities for scaling up.
124
-
> Use this SKU only for experimenting, development, and testing, not production or performance testing.
122
+
> The [Developer ISE SKU](../logic-apps/connect-virtual-network-vnet-isolated-environment-overview.md#ise-level)
123
+
> has no published limits, no capabilities for scaling up, and no service-level agreement (SLA). Use this SKU
124
+
> only for experimenting, development, and testing, not production or performance testing.
125
125
126
126
<aname="gateway-limits"></a>
127
127
@@ -279,14 +279,9 @@ Here are the message size limits that apply to B2B protocols:
279
279
280
280
## Disabling or deleting logic apps
281
281
282
-
When you disable a logic app, no new runs are instantiated.
283
-
All in-progress and pending runs continue until they finish,
284
-
which might take time to complete.
282
+
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.
285
283
286
-
When you delete a logic app, no new runs are instantiated.
287
-
All in-progress and pending runs are canceled.
288
-
If you have thousands of runs, cancellation might
289
-
take significant time to complete.
284
+
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.
290
285
291
286
<aname="configuration"></a>
292
287
@@ -313,7 +308,11 @@ The IP addresses that Azure Logic Apps uses for incoming and outgoing calls depe
313
308
314
309
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](../logic-apps/logic-apps-limits-and-config.md#outbound), 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](../connectors/connectors-create-api-azureblobstorage.md#access-storage-accounts-behind-firewalls).
315
310
316
-
* For custom connectors, [Azure Government](../azure-government/documentation-government-overview.md), and [Azure China 21Vianet](https://docs.microsoft.com/azure/china/), fixed or reserved IP addresses aren't available.
311
+
* These connectors don't have fixed or reserved IP addresses:
312
+
313
+
* Custom connectors, whether they're used in multi-tenant Azure, [integration service environments (ISEs)](../logic-apps/connect-virtual-network-vnet-isolated-environment-overview.md), [Azure Government](../azure-government/documentation-government-overview.md), and [Azure China 21Vianet](https://docs.microsoft.com/azure/china/)
314
+
315
+
* Managed connectors in [Azure China 21Vianet](https://docs.microsoft.com/azure/china/), for example, Azure Storage, SQL Server, Office 365, and so on
0 commit comments