Skip to content

Commit fc5962f

Browse files
committed
Add Standard info and update UX
1 parent e5e1b48 commit fc5962f

File tree

5 files changed

+52
-20
lines changed

5 files changed

+52
-20
lines changed
40.4 KB
Loading
12.8 KB
Loading
69.9 KB
Loading

articles/logic-apps/set-up-zone-redundancy-availability-zones.md

Lines changed: 52 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -10,25 +10,31 @@ ms.custom: references_regions
1010
#Customer intent: As a developer, I want to protect logic apps from regional failures by setting up availability zones.
1111
---
1212

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
1414

1515
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.
1616

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).
1818

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.
2620

2721
## Considerations
2822

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.
3030

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:
3238

3339
* Australia East
3440
* Brazil South
@@ -48,15 +54,13 @@ During preview, the following considerations apply:
4854
* West Europe
4955
* West US 3
5056

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.
5458

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.
5660

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.
5862

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+
---
6064

6165
## Limitations
6266

@@ -66,7 +70,7 @@ With HTTP-based actions, certificates exported or created with AES256 encryption
6670

6771
* 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).
6872

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:
7074

7175
* [Firewall configuration: IP addresses and service tags](logic-apps-limits-and-config.md#firewall-ip-configuration)
7276

@@ -76,7 +80,33 @@ With HTTP-based actions, certificates exported or created with AES256 encryption
7680

7781
* [Outbound IP addresses for managed connectors and custom connectors](/connectors/common/outbound-ip-addresses)
7882

79-
## Set up availability zones for Consumption logic app workflows
83+
## Enable availability zones
84+
85+
<a name="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+
![Screenshot showing Azure portal, "Create Logic App" page, logic app details, and the "Standard" plan type selected.](./media/set-up-zone-redundancy-availability-zones/select-standard-plan.png)
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+
![Screenshot showing Azure portal, "Create Logic App" page, Standard logic app details, and the "Enabled" option under "Zone redundancy" selected.](./media/set-up-zone-redundancy-availability-zones/enable-zone-redundancy-standard.png)
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+
<a name="consumption"></a>
108+
109+
### [Consumption (preview)](#tab/consumption)
80110

81111
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.
82112

@@ -90,12 +120,14 @@ With HTTP-based actions, certificates exported or created with AES256 encryption
90120

91121
At this point, your logic app creation experience appears similar to this example:
92122

93-
![Screenshot showing Azure portal, "Create Logic App" page, logic app details, and the "Enabled" option under "Zone redundancy" selected.](./media/set-up-zone-redundancy-availability-zones/enable-zone-redundancy.png)
123+
![Screenshot showing Azure portal, "Create Logic App" page, Consumption logic app details, and the "Enabled" option under "Zone redundancy" selected.](./media/set-up-zone-redundancy-availability-zones/enable-zone-redundancy-consumption.png)
94124

95125
1. Finish creating your logic app.
96126

97127
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).
98128

129+
---
130+
99131
## Next steps
100132

101133
* [Business continuity and disaster recovery for Azure Logic Apps](business-continuity-disaster-recovery-guidance.md)

0 commit comments

Comments
 (0)