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/set-up-zone-redundancy-availability-zones.md
+52-20Lines changed: 52 additions & 20 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,25 +10,31 @@ ms.custom: references_regions
10
10
#Customer intent: As a developer, I want to protect logic apps from regional failures by setting up availability zones.
11
11
---
12
12
13
-
# Protect Consumption logic apps from region failures with zone redundancy and availability zones (preview)
13
+
# Protect logic apps from region failures with zone redundancy and availability zones
14
14
15
15
In each Azure region, *availability zones* are physically separate locations that are tolerant to local failures. Such failures can range from software and hardware failures to events such as earthquakes, floods, and fires. These zones achieve tolerance through the redundancy and logical isolation of Azure services.
16
16
17
-
To provide resiliency and distributed availability, at least three separate availability zones exist in any Azure region that supports and enables zone redundancy. The Azure Logic Apps platform distributes these zones and logic app workloads across these zones. This capability is a key requirement for enabling resilient architectures and providing high availability if datacenter failures happen in a region. For more information about availability zones and zone redundancy, review [Azure regions and availability zones](../availability-zones/az-overview.md).
17
+
To provide resiliency and distributed availability, at least three separate availability zones exist in any Azure region that supports and enables zone redundancy. The Azure Logic Apps platform distributes these zones and logic app workloads across these zones. This capability is a key requirement for enabling resilient architectures and providing high availability if datacenter failures happen in a region. For more information about availability zone redundancy, review [Azure regions and availability zones](../availability-zones/az-overview.md).
18
18
19
-
This article provides a brief overview about considerations for using availability zones in Azure Logic Apps and how to enable this capability for your Consumption logic app.
20
-
21
-
> [!NOTE]
22
-
>
23
-
> Standard logic apps that use [App Service Environment v3 (ASE v3)](../app-service/environment/overview-zone-redundancy.md)
24
-
> support zone redundancy with availability zones, but only for built-in operations. Currently, support is unavailable
25
-
> for Azure (managed) connectors.
19
+
This article provides a brief overview, considerations, and information about how to enable availability zone redundancy in Azure Logic Apps.
26
20
27
21
## Considerations
28
22
29
-
During preview, the following considerations apply:
23
+
### [Standard](#tab/standard)
24
+
25
+
Availability zone redundancy is available for Standard logic apps, which are powered by Azure Functions extensibility. For more information, review [Azure Functions support for availability zone redundancy](../azure-functions/azure-functions-az-redundancy.md#overview).
26
+
27
+
* You can enable availability zone redundancy *only when you create* Standard logic apps in [Azure regions that support availability zone redundancy](../azure-functions/azure-functions-az-redundancy.md#requirements) or in an [App Service Environment v3 (ASE v3) for Windows plans only](../app-service/environment/overview-zone-redundancy.md). However, this capability is supports only built-in connector operations, not Azure (managed) connector operations.
28
+
29
+
* You can enable availability zone redundancy *only for new* Standard logic apps with workflows that run in single-tenant Azure Logic Apps. You can't enable availability zone redundancy for existing Standard logic app workflows.
30
30
31
-
* The following list includes the Azure regions where you can currently enable availability zones with the list expanding as available:
31
+
* You can enable availability zone redundancy *only at creation time using Azure portal*. No programmatic tool support, such as Azure PowerShell or Azure CLI, currently exists to enable availability zone redundancy.
32
+
33
+
### [Consumption (preview)](#tab/consumption)
34
+
35
+
Availability zone redundancy is currently in *preview* for Consumption logic apps. During preview, the following considerations apply:
36
+
37
+
* You can enable availability zone redundancy *only for new* Consumption logic app workflows that you create in the following Azure regions, which will expand as available:
32
38
33
39
* Australia East
34
40
* Brazil South
@@ -48,15 +54,13 @@ During preview, the following considerations apply:
48
54
* West Europe
49
55
* West US 3
50
56
51
-
* Azure Logic Apps currently supports the option to enable availability zones *only for new Consumption logic app workflows* that run in multi-tenant Azure Logic Apps.
52
-
53
-
* This option is available *only when you create a Consumption logic app using the Azure portal*. No programmatic tool support, such as Azure PowerShell or Azure CLI, currently exists to enable availability zones.
57
+
You have to create these Consumption logic apps *using the Azure portal*. No programmatic tool support, such as Azure PowerShell or Azure CLI, currently exists to enable availability zone redundancy.
54
58
55
-
* This option is unavailable for existing Consumption logic app workflows and for any Standard logic app workflows.
59
+
* You can't enable availability zone redundancy for existing Consumption logic app workflows. Any existing Consumption logic app workflows are unaffected until mid-May 2022.
56
60
57
-
* Existing Consumption logic app workflows are unaffected until mid-May 2022. After this time, the Azure Logic Apps team will gradually start to move existing Consumption logic app workflows towards using availability zones, several Azure regions at a time. The option to enable availability zones on new Consumption logic app workflows remains available during this time.
61
+
However, after this time, the Azure Logic Apps team will gradually start to move existing Consumption logic app workflows towards using availability zone redundancy, several Azure regions at a time. The option to enable availability zone redundancy on new Consumption logic app workflows remains available during this time.
58
62
59
-
* If you use a firewall or restricted environment, you have to allow traffic through all the IP addresses required by Azure Logic Apps, managed connectors, and custom connectors in the Azure region where you create your logic app workflows. New IP addresses that support availability zones are already published for Azure Logic Apps, managed connectors, and custom connectors. For more information, review [Prerequisites](#prerequisites).
63
+
---
60
64
61
65
## Limitations
62
66
@@ -66,7 +70,7 @@ With HTTP-based actions, certificates exported or created with AES256 encryption
66
70
67
71
* An Azure account and subscription. If you don't have a subscription, [sign up for a free Azure account](https://azure.microsoft.com/free/?WT.mc_id=A261C142F).
68
72
69
-
* If you have a firewall or restricted environment, you have to allow traffic through all the IP addresses required by Azure Logic Apps, managed connectors, and any custom connectors in the Azure region where you create your logic app workflows. For more information, review the following documentation:
73
+
* If you have a firewall or restricted environment, you have to allow traffic through all the IP addresses required by Azure Logic Apps, managed connectors, and any custom connectors in the Azure region where you create your logic app workflows. New IP addresses that support availability zone redundancy are already published for Azure Logic Apps, managed connectors, and custom connectors. For more information, review the following documentation:
70
74
71
75
*[Firewall configuration: IP addresses and service tags](logic-apps-limits-and-config.md#firewall-ip-configuration)
72
76
@@ -76,7 +80,33 @@ With HTTP-based actions, certificates exported or created with AES256 encryption
76
80
77
81
*[Outbound IP addresses for managed connectors and custom connectors](/connectors/common/outbound-ip-addresses)
78
82
79
-
## Set up availability zones for Consumption logic app workflows
83
+
## Enable availability zones
84
+
85
+
<aname="standard"></a>
86
+
87
+
### [Standard](#tab/standard)
88
+
89
+
1. In the [Azure portal](https://portal.azure.com), start creating a Standard logic app. On the **Create Logic App** page, stop after you select **Standard** as the plan type for your logic app.
90
+
91
+

92
+
93
+
For a quick tutorial, review [Quickstart: Create your first integration workflow with multi-tenant Azure Logic Apps and the Azure portal](quickstart-create-first-logic-app-workflow.md).
94
+
95
+
After you select **Standard**, the **Zone redundancy** section and options become available.
96
+
97
+
1. Under **Zone redundancy**, select **Enabled**.
98
+
99
+
At this point, your logic app creation experience appears similar to this example:
100
+
101
+

102
+
103
+
1. Finish creating your logic app.
104
+
105
+
1. If you use a firewall and haven't set up access for traffic through the required IP addresses, make sure to complete that [requirement](#prerequisites).
106
+
107
+
<aname="consumption"></a>
108
+
109
+
### [Consumption (preview)](#tab/consumption)
80
110
81
111
1. In the [Azure portal](https://portal.azure.com), start creating a Consumption logic app. On the **Create Logic App** page, stop after you select **Consumption** as the plan type for your logic app.
82
112
@@ -90,12 +120,14 @@ With HTTP-based actions, certificates exported or created with AES256 encryption
90
120
91
121
At this point, your logic app creation experience appears similar to this example:
92
122
93
-

123
+

94
124
95
125
1. Finish creating your logic app.
96
126
97
127
1. If you use a firewall and haven't set up access for traffic through the required IP addresses, make sure to complete that [requirement](#prerequisites).
98
128
129
+
---
130
+
99
131
## Next steps
100
132
101
133
*[Business continuity and disaster recovery for Azure Logic Apps](business-continuity-disaster-recovery-guidance.md)
0 commit comments