Merge pull request #281135 from ecfan/zone

Clarify availability zone support

Author: Jill Grant

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

@@ -103,18 +103,17 @@ To create and manage a Consumption logic app workflow using other tools, see the
    | **Region** | Yes | <*Azure-region*> | The Azure datacenter region for storing your app's information. This example deploys the sample logic app to the **West US** region in Azure. |
    | **Enable log analytics** | Yes | **No** | This option appears and applies only when you select the **Consumption** logic app type. <br><br>Change this option only when you want to enable diagnostic logging. For this quickstart, keep the default selection. |
 
-   When you're done, your settings look similar to the following example:
-
-   :::image type="content" source="media/quickstart-create-example-consumption-workflow/create-logic-app-settings.png" alt-text="Screenshot shows Azure portal and logic app resource creation page with details for new logic app." lightbox="media/quickstart-create-example-consumption-workflow/create-logic-app-settings.png":::
-
    > [!NOTE]
    >
-   > If you selected an Azure region that supports availability zone redundancy, the **Zone redundancy** 
-   > section is automatically enabled. This preview section offers the choice to enable availability zone 
-   > redundancy for your logic app. However, currently supported Azure regions don't include **West US**, 
-   > so you can ignore this section for this example. For more information, see 
+   > Availability zones are automatically enabled for new and existing Consumption logic app workflows in 
+   > [Azure regions that support availability zones](../reliability/availability-zones-service-support.md#azure-regions-with-availability-zone-support). 
+   > For more information, see [Reliability in Azure Functions](../reliability/reliability-functions.md#availability-zone-support) and 
    > [Protect logic apps from region failures with zone redundancy and availability zones](set-up-zone-redundancy-availability-zones.md).
 
+   After you finish, your settings look similar to the following example:
+
+   :::image type="content" source="media/quickstart-create-example-consumption-workflow/create-logic-app-settings.png" alt-text="Screenshot shows Azure portal and logic app resource creation page with details for new logic app." lightbox="media/quickstart-create-example-consumption-workflow/create-logic-app-settings.png":::
+
 1. When you're ready, select **Review + Create**.
 
 1. On the validation page that appears, confirm all the provided information, and select **Create**.
@@ -202,7 +201,7 @@ This example uses an Office 365 Outlook action that sends an email each time tha
 
          :::image type="content" source="media/quickstart-create-example-consumption-workflow/dynamic-content-see-more.png" alt-text="Screenshot shows open dynamic content list and selected option, See more." lightbox="media/quickstart-create-example-consumption-workflow/dynamic-content-see-more.png":::
 
-         When you're done, the email subject looks like the following example:
+         After you finish, the email subject looks like the following example:
 
          :::image type="content" source="media/quickstart-create-example-consumption-workflow/send-email-feed-title.png" alt-text="Screenshot shows action named Send an email, with example email subject and included property named Feed title." lightbox="media/quickstart-create-example-consumption-workflow/send-email-feed-title.png":::
 
@@ -232,7 +231,7 @@ This example uses an Office 365 Outlook action that sends an email each time tha
 
 ## Test your workflow
 
-To check that the workflow runs correctly, you can either wait for the trigger to fire based on your specifed schedule, or you can manually run the workflow.
+To check that the workflow runs correctly, you can either wait for the trigger to fire based on your specified schedule, or you can manually run the workflow.
 
 * On the designer toolbar, from the **Run** menu, select **Run**.
 
@@ -252,7 +251,7 @@ If you don't receive emails from the workflow as expected:
 
 ## Clean up resources
 
-When you're done with this quickstart, delete the sample logic app resource and any related resources by deleting the resource group that you created for this example.
+When you complete this quickstart, delete the sample logic app resource and any related resources by deleting the resource group that you created for this example.
 
 1. In the Azure search box, enter **resource groups**, and select **Resource groups**.
 

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

@@ -1,66 +1,47 @@
 ---
-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.
+title: Protect logic apps from zonal failures
+description: Set up availability zone support 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: 01/04/2024
+ms.date: 07/17/2024
 ms.custom: references_regions
-#Customer intent: As a developer, I want to protect logic apps from regional failures by setting up availability zones.
+#Customer intent: As a developer, I want to protect logic apps from zonal failures by setting up availability zones and zone redundancy.
 ---
 
-# Protect logic apps from zonal failures with zone redundancy and availability zones
+# Protect logic apps from zonal failures with availability zones and zone redundancy
 
 [!INCLUDE [logic-apps-sku-consumption-standard](../../includes/logic-apps-sku-consumption-standard.md)]
 
 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 zone redundancy, review [Azure regions and availability zones](../availability-zones/az-overview.md).
+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.
 
-This article provides a brief overview, considerations, and information about how to enable availability zone redundancy in Azure Logic Apps.
+For more information, see the following documentation:
 
-## Considerations
-
-### [Standard](#tab/standard)
+* [What are availability zones](../reliability/availability-zones-overview.md)?
+* [Azure regions with availability zone support](../reliability/availability-zones-service-support.md)
 
-Availability zone support is available for Standard logic apps, which are powered by Azure Functions extensibility. For more information, see [What is reliability in Azure Functions?](../reliability/reliability-functions.md#availability-zone-support).
+This guide provides a brief overview, considerations, and information about how to enable availability zones in Azure Logic Apps.
 
-* You can enable availability zone redundancy *only when you create* Standard logic apps, either in a [supported Azure region](../azure-functions/azure-functions-az-redundancy.md#requirements) or in an [App Service Environment v3 (ASE v3) - Windows plans only](../app-service/environment/overview-zone-redundancy.md). Currently, this capability supports only built-in connector operations, not Azure (managed) connector operations.
-
-* 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.
+## Considerations
 
-* You can enable availability zone redundancy *only at creation time*. No programmatic tool support, such as Azure PowerShell or Azure CLI, currently exists to enable availability zone redundancy after creation.
+### [Standard](#tab/standard)
 
-### [Consumption (preview)](#tab/consumption)
+Availability zones are supported with Standard logic app workflows, which run in single-tenant Azure Logic Apps and are powered by Azure Functions extensibility. For more information, see [Reliability in Azure Functions](../reliability/reliability-functions.md#availability-zone-support).
 
-Availability zone redundancy is currently in *preview* for Consumption logic apps, which run in multi-tenant Azure Logic Apps. During preview, the following considerations apply:
+* You can enable this capability only when you create a Standard logic app in a [supported Azure region](../reliability/reliability-functions.md#regional-availability) or in an [App Service Environment v3 (ASE v3) - Windows plans only](../app-service/environment/overview-zone-redundancy.md).
 
-* 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:
+* You can enable this capability *only for new* Standard logic apps. You can't enable availability zone support for existing Standard logic app workflows.
 
-  * Australia East
-  * Brazil South
-  * Canada Central
-  * Central India
-  * Central US
-  * East Asia
-  * East US
-  * East US 2
-  * France Central
-  * Germany West Central
-  * Japan East
-  * Korea Central
-  * Norway East
-  * South Central US
-  * UK South
-  * West Europe
-  * West US 3
+* You can enable this capability *only at creation time*. No programmatic tool support, such as Azure PowerShell or Azure CLI, currently exists to enable availability zone support after creation.
 
-  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. 
+* This capability supports only built-in connector operations, which directly run with the Azure Logic Apps runtime, not connector operations that are hosted and run in Azure.
 
-* 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.
+### [Consumption](#tab/consumption)
 
-  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.
+Availability zones are supported with Consumption logic app workflows, which run in multitenant Azure Logic Apps. This capability is automatically enabled for new and existing Consumption logic app workflows in [Azure regions that support availability zones](../reliability/availability-zones-service-support.md#azure-regions-with-availability-zone-support).
 
 ---
 
@@ -84,48 +65,32 @@ With HTTP-based actions, certificates exported or created with AES256 encryption
 
 ## Enable availability zones
 
-### [Standard](#tab/standard)
+For Standard logic apps only, follow these steps:
 
 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.
 
-   ![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)
+   :::image type="content" source="media/set-up-zone-redundancy-availability-zones/select-standard-plan.png" alt-text="Screenshot shows Azure portal, Create Logic App page, logic app details, and selected Standard plan type." lightbox="media/set-up-zone-redundancy-availability-zones/select-standard-plan.png":::
 
-   For a tutorial, review [Create Standard logic app workflows with single-tenant Azure Logic Apps in the Azure portal](create-single-tenant-workflows-azure-portal.md).
+   For a tutorial, see [Create Standard logic app workflows with single-tenant Azure Logic Apps in the Azure portal](create-single-tenant-workflows-azure-portal.md).
 
    After you select **Standard**, 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, Standard logic app details, and the "Enabled" option under "Zone redundancy" selected.](./media/set-up-zone-redundancy-availability-zones/enable-zone-redundancy-standard.png)
-
-1. Finish creating your logic app workflow.
-
-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).
-
-### [Consumption (preview)](#tab/consumption)
-
-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, see [Quickstart: Create an example Consumption logic app workflow in multi-tenant Azure Logic Apps using the Azure portal](quickstart-create-example-consumption-workflow.md).
-
-   After you select **Consumption**, the **Zone redundancy** section and options become available.
+   > [!NOTE]
+   >
+   > The **Zone redundancy** options appear unavailable if you select an unsupported Azure region or an 
+   > existing Windows plan that created in an unsupported Azure region. Make sure to select a supported 
+   > Azure region and a Windows plan that was created in a supported Azure region, or create a new Windows plan.
 
 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, Consumption logic app details, and the "Enabled" option under "Zone redundancy" selected.](./media/set-up-zone-redundancy-availability-zones/enable-zone-redundancy-consumption.png)
+   :::image type="content" source="media/set-up-zone-redundancy-availability-zones/enable-zone-redundancy-standard.png" alt-text="Screenshot shows Azure portal, Create Logic App page, Standard logic app details, and the Enabled option selected under Zone redundancy." lightbox="media/set-up-zone-redundancy-availability-zones/enable-zone-redundancy-standard.png":::
 
 1. Finish creating your logic app workflow.
 
 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
+## Related content
 
 * [Business continuity and disaster recovery for Azure Logic Apps](business-continuity-disaster-recovery-guidance.md)