Merge pull request #196035 from ecfan/availability-zones

Azure Logic Apps: Availability zones preview

Author: AnnaMHuff

articles/logic-apps/business-continuity-disaster-recovery-guidance.md

@@ -5,7 +5,7 @@ services: logic-apps
 ms.suite: integration
 ms.reviewer: estfan, azla
 ms.topic: conceptual
-ms.date: 03/24/2021
+ms.date: 05/02/2022
 ---
 
 # Business continuity and disaster recovery for Azure Logic Apps
@@ -34,7 +34,7 @@ Each logic app needs to specify the location that you want to use for deployment
 
 This disaster recovery strategy focuses on setting up your primary logic app to [*failover*](https://en.wikipedia.org/wiki/Failover) onto a standby or backup logic app in an alternate location where Azure Logic Apps is also available. That way, if the primary suffers losses, disruptions, or failures, the secondary can take on the work. This strategy requires that your secondary logic app and dependent resources are already deployed and ready in the alternate location.
 
-If you follow good DevOps practices, you already use [Azure Resource Manager templates](../azure-resource-manager/management/overview.md) to define and deploy your logic apps and their dependent resources. Resource Manager templates give you the capability to use a single deployment definition and then use parameter files to provide the configuration values to use for each deployment destination. This capability means that you can deploy the same logic app to different environments, for example, development, test, and production. You can also deploy the same logic app to different Azure regions or ISEs, which supports disaster recovery strategies that use [paired-regions](../availability-zones/cross-region-replication-azure.md).
+If you follow good DevOps practices, you already use [Azure Resource Manager templates](../azure-resource-manager/management/overview.md) to define and deploy your logic apps and their dependent resources. Resource Manager templates give you the capability to use a single deployment definition and then use parameter files to provide the configuration values to use for each deployment destination. This capability means that you can deploy the same logic app to different environments, for example, development, test, and production. You can also deploy the same logic app to different Azure regions or ISEs, which support disaster recovery strategies that use [paired-regions](../availability-zones/cross-region-replication-azure.md).
 
 For the failover strategy, your logic apps and locations must meet these requirements:
 
@@ -142,7 +142,7 @@ This example shows the active-passive setup where the primary logic app instance
 
 This example shows a combined setup where the primary location has both active logic app instances, while the secondary location has active-passive logic app instances. If the primary location experiences a disruption or failure, the active logic app in the secondary location, which is already handling a partial workload, can take over the entire workload.
 
-* In the primary location, an active logic app listens to an Azure Service Bus queue for messages, while another active logic app checks for emails by using a Office 365 Outlook polling trigger.
+* In the primary location, an active logic app listens to an Azure Service Bus queue for messages, while another active logic app checks for emails by using an Office 365 Outlook polling trigger.
 
 * In the secondary location, an active logic app works with the logic app in the primary location by listening and competing for messages from the same Service Bus queue. Meanwhile, a passive inactive logic app waits on standby to check for emails when the primary location becomes unavailable but is *disabled* to avoid rereading emails.
 
@@ -340,6 +340,19 @@ For this task, in the secondary location, create a watchdog logic app that perfo
 
 To automatically activate the secondary instance, you can create a logic app that calls the management API such as the [Azure Resource Manager connector](/connectors/arm/) to activate the appropriate logic apps in the secondary location. You can expand your watchdog app to call this activation logic app after a specific number of failures happen.
 
+<a name="availability-zones"></a>
+
+## Zone redundancy with availability zones
+
+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.
+
+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.
+
+Currently, this capability is preview and available for new Consumption logic apps in specific regions. For more information, see the following documentation:
+
+* [Protect Consumption logic apps from region failures with zone redundancy and availability zones](set-up-zone-redundancy-availability-zones.md)
+* [Azure regions and availability zones](../availability-zones/az-overview.md)
+
 <a name="collect-diagnostic-data"></a>
 
 ## Collect diagnostic data

articles/logic-apps/media/quickstart-create-first-logic-app-workflow/create-logic-app-settings.png

@@ -6,7 +6,7 @@ ms.suite: integration
 ms.reviewer: estfan, azla
 ms.topic: quickstart
 ms.custom: contperf-fy21q4, mode-ui
-ms.date: 03/02/2022
+ms.date: 05/02/2022
 
 #Customer intent: As a developer, I want to create my first automated integration workflow that runs in Azure Logic Apps using the Azure portal.
 ---
@@ -86,7 +86,7 @@ To create and manage a logic app resource using other tools, review these other
 
    | Plan type | Description |
    |-----------|-------------|
-   | **Consumption** | This logic app type runs in global, multi-tenant Azure Logic Apps and uses the [Consumption billing model](logic-apps-pricing.md#consumption-pricing). |
+   | **Consumption** | This logic app type runs in global, multi-tenant Azure Logic Apps and uses the [Consumption billing model](logic-apps-pricing.md#consumption-pricing). After you select **Consumption**, the **Zone redundancy** section appears. This section offers the choice to enable availability zones for your Consumption logic app. In this example, keep **Enabled** as the setting value. For more information, see [Protect Consumption logic apps from region failures with zone redundancy and availability zones](set-up-zone-redundancy-availability-zones.md). |
    | **Standard** | This logic app type is the default selection and runs in single-tenant Azure Logic Apps and uses the [Standard billing model](logic-apps-pricing.md#standard-pricing). |
    |||
 

articles/logic-apps/media/set-up-zone-redundancy-availability-zones/enable-zone-redundancy.png

@@ -0,0 +1,82 @@
+---
+title: Protect logic apps from region failures with zone redundancy
+description: Set up availability zones for logic apps with zone redundancy for business continuity and disaster recovery.
+services: logic-apps
+ms.suite: integration
+ms.reviewer: estfan, shahparth, laveeshb, azla
+ms.topic: how-to
+ms.date: 05/02/2022
+ms.custom: references_regions
+#Customer intent: As a developer, I want to protect logic apps from regional failures by setting up availability zones.
+---
+
+# Protect Consumption logic apps from region failures with zone redundancy and availability zones (preview)
+
+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.
+
+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).
+
+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.
+
+## Considerations
+
+During preview, the following considerations apply:
+
+* The following list includes the Azure regions where you can currently enable availability zones with the list expanding as available:  
+
+  - Brazil South
+  - Canada Central
+  - France Central
+
+* 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.
+
+  * 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.
+
+  * This option is unavailable for existing Consumption logic app workflows and for any Standard logic app workflows.
+
+* 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.
+
+* 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).
+
+## Limitations
+
+With HTTP-based actions, certificates exported or created with AES256 encryption won't work when used for client certificate authentication. The same certificates also won't work when used for OAuth authentication.
+
+## Prerequisites
+
+* 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).
+
+* 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:
+
+  * [Firewall configuration: IP addresses and service tags](logic-apps-limits-and-config.md#firewall-ip-configuration)
+
+  * [Inbound IP addresses for Azure Logic Apps](logic-apps-limits-and-config.md#inbound)
+
+  * [Outbound IP addresses for Azure Logic Apps](logic-apps-limits-and-config.md#outbound)
+
+  * [Outbound IP addresses for managed connectors and custom connectors](/connectors/common/outbound-ip-addresses)
+
+## Set up availability zones for Consumption logic app workflows
+
+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.
+
+   ![Screenshot showing Azure portal, "Create Logic App" page, logic app details, and the "Consumption" plan type selected.](./media/set-up-zone-redundancy-availability-zones/select-consumption-plan.png)
+
+   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).
+
+   After you select **Consumption**, the **Zone redundancy** section and options become available.
+
+1. Under **Zone redundancy**, select **Enabled**.
+
+   At this point, your logic app creation experience appears similar to this example:
+
+   ![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)
+
+1. Finish creating your logic app.
+
+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).
+
+## Next steps
+
+* [Business continuity and disaster recovery for Azure Logic Apps](business-continuity-disaster-recovery-guidance.md)
+* [Connectors in Azure Logic Apps](../connectors/apis-list.md)

articles/logic-apps/media/set-up-zone-redundancy-availability-zones/select-consumption-plan.png

@@ -412,6 +412,8 @@
         href: create-monitoring-tracking-queries.md
   - name: Business continuity and disaster recovery
     items:
+    - name: Set up zone redundant logic apps
+      href: set-up-zone-redundancy-availability-zones.md
     - name: Replicate Azure resources for business continuity and disaster recovery
       href: create-replication-tasks-azure-resources.md
     - name: Build a B2B business continuity and disaster recovery plan