Skip to content

Commit 3bf973f

Browse files
authored
Merge pull request #190850 from ecfan/name-limit
Azure Logic Apps: Clarify naming limits for Consumption vs Standard
2 parents 0929988 + 0d817a3 commit 3bf973f

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/logic-apps/logic-apps-limits-and-config.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ services: logic-apps
55
ms.suite: integration
66
ms.reviewer: rohithah, laveeshb, rarayudu, azla
77
ms.topic: reference
8-
ms.date: 03/01/2022
8+
ms.date: 03/07/2022
99
---
1010

1111
# Limits and configuration reference for Azure Logic Apps
@@ -30,7 +30,7 @@ The following tables list the values for a single workflow definition:
3030
| Name | Limit | Notes |
3131
| ---- | ----- | ----- |
3232
| Workflows per region per subscription | 1,000 workflows ||
33-
| Workflow - Maximum name length | 43 characters | Previously 80 characters |
33+
| Workflow - Maximum name length | - Consumption: 80 characters <br><br>- Standard: 43 characters ||
3434
| Triggers per workflow | 10 triggers | This limit applies only when you work on the JSON workflow definition, whether in code view or an Azure Resource Manager (ARM) template, not the designer. |
3535
| Actions per workflow | 500 actions | To extend this limit, you can use nested workflows as necessary. |
3636
| Actions nesting depth | 8 actions | To extend this limit, you can use nested workflows as necessary. |

0 commit comments

Comments
 (0)