Merge pull request #290002 from anaharris-ms/reliability-logic-apps

Reliability document: Logic Apps

Author: Jill Grant

.openpublishing.redirection.json

@@ -4492,6 +4492,11 @@
       "redirect_url": "/azure/virtual-network/tutorial-create-route-table",
       "redirect_document_id": false
     },
+    {
+      "source_path_from_root": "/articles/logic-apps/business-continuity-disaster-recovery-guidance.md",
+      "redirect_url": "/azure/logic-apps/multi-region-disaster-recovery",
+      "redirect_document_id": true
+    },
     {
       "source_path_from_root": "/articles/virtual-network/tutorial-connect-virtual-networks-portal.md",
       "redirect_url": "/azure/virtual-network/tutorial-connect-virtual-networks",

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

@@ -5,92 +5,71 @@ services: logic-apps
 ms.suite: integration
 ms.reviewer: estfan, shahparth, laveeshb, azla
 ms.topic: how-to
-ms.date: 07/17/2024
+ms.date: 12/18/2024
 ms.custom: references_regions
 #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 availability zones and zone redundancy
+# Enable zone-redundancy for your logic app
 
 [!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.
+[!INCLUDE [reliability-az-description](../reliability/includes/reliability-availability-zone-description-include.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.
+For scenarios where you need high reliability for your logic app workflows, you can set up *zone redundancy* with *availability zones* within an Azure region. Azure Logic Apps can then distribute logic app workloads across all the availability zones within a region. This capability protects your apps and their information from datacenter failures within a region.
 
-For more information, see the following documentation:
+This guide shows how to enable zone redundancy for your logic apps.
 
-* [What are availability zones](../reliability/availability-zones-overview.md)?
-* [Azure regions with availability zone support](../reliability/availability-zones-region-support.md)
-
-This guide provides a brief overview, considerations, and information about how to enable availability zones in Azure Logic Apps.
-
-## Considerations
-
-### [Standard](#tab/standard)
-
-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).
+## Prerequisites
 
-* 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).
+- Make sure that you understand zone redundancy support. Also, ensure you meet the requirements to use availability zones, including being in a supported region, when you create your logic app resource. For more information, see [Reliability in Azure Logic Apps](../reliability/reliability-logic-apps.md#availability-zone-support).
 
-* You can enable this capability *only for new* Standard logic apps. You can't enable availability zone support for existing Standard logic app workflows.
+- You need to have an Azure account and subscription. If you don't have a subscription, [sign up for a free Azure account](https://azure.microsoft.com/pricing/purchase-options/azure-account?WT.mc_id=A261C142F).
 
-* 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.
+- If you have a firewall or restricted environment, you have to allow traffic through all the IP addresses required by Azure Logic Apps, Azure-hosted 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, see the following documentation:
 
-* 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.
+  - [Firewall configuration: IP addresses and service tags](logic-apps-limits-and-config.md#firewall-ip-configuration)
 
-### [Consumption](#tab/consumption)
+  - [Inbound IP addresses for Azure Logic Apps](logic-apps-limits-and-config.md#inbound)
 
-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-region-support.md).
+  - [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)
 
 ## 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. 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:
+## Set up zone redundancy for your logic app
 
-  * [Firewall configuration: IP addresses and service tags](logic-apps-limits-and-config.md#firewall-ip-configuration)
+For Consumption logic apps, zone redundancy is automatically enabled. You don't need to take any additional steps to enable zone redundancy for Consumption logic apps.
 
-  * [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)
+For Standard logic apps only, follow these steps:
 
-  * [Outbound IP addresses for managed connectors and custom connectors](/connectors/common/outbound-ip-addresses)
+1. In the [Azure portal](https://portal.azure.com), start creating a logic app.
 
-## Enable availability zones
+1. On the **Create Logic App** page, select **Workflow Service Plan** or **App Service Environment V3**, based on the hosting option you want to use.
 
-For Standard logic apps only, follow these steps:
+   :::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, Standard plan types." lightbox="media/set-up-zone-redundancy-availability-zones/select-standard-plan.png":::
 
-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.
+   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).
 
-   :::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":::
+1. Under **Zone redundancy**, select **Enabled**.
 
-   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).
+   At this point, your logic app creation experience appears similar to this example:
 
-   After you select **Standard**, the **Zone redundancy** section and options become available.
+   :::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":::
 
    > [!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 
+   > existing Windows plan that was 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:
-
-   :::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).
 
 ## Related content
 
-* [Business continuity and disaster recovery for Azure Logic Apps](business-continuity-disaster-recovery-guidance.md)
+- [Reliability in Azure Logic Apps](../reliability/reliability-logic-apps.md)

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

@@ -74,8 +74,12 @@ items:
     href: logic-apps-enterprise-integration-overview.md
   - name: Mainframe modernization
     href: mainframe-modernization-overview.md
-  - name: Business continuity and disaster recovery
-    href: business-continuity-disaster-recovery-guidance.md
+  - name: Reliability
+    items:
+    - name: Reliability in Azure Logic Apps
+      href: ../reliability/reliability-logic-apps.md?toc=/azure/logic-apps/toc.json
+    - name: Multi-region deployments for disaster recovery
+      href: multi-region-disaster-recovery.md
   - name: Security
     items:
     - name: Security controls by Azure Policy
@@ -483,13 +487,13 @@ items:
         href: tracking-schemas-as2-x12-custom.md
       - name: Create monitoring and tracking queries
         href: create-monitoring-tracking-queries.md
-  - name: Business continuity and disaster recovery
+  - name: Reliability
     items:
-    - name: Set up zone redundant logic apps
+    - name: Enable zone redundancy
       href: set-up-zone-redundancy-availability-zones.md
-    - name: Replicate Azure resources for business continuity and disaster recovery
+    - name: Create replication tasks for Azure resources
       href: create-replication-tasks-azure-resources.md
-    - name: Build a B2B business continuity and disaster recovery plan
+    - name: Set up cross-region disaster recovery for integration accounts
       href: logic-apps-enterprise-integration-b2b-business-continuity.md
   - name: Examples, scenarios, and walkthroughs
     href: logic-apps-examples-and-scenarios.md

articles/logic-apps/business-continuity-disaster-recovery-guidance.md renamed to articles/logic-apps/multi-region-disaster-recovery.md

@@ -64,8 +64,6 @@
         href: migrate-load-balancer.md
       - name: Log Analytics Dedicated Cluster workspaces
         href: migrate-monitor-log-analytics.md
-      - name: Azure Logic Apps
-        href: /azure/logic-apps/set-up-zone-redundancy-availability-zones?tabs=standard&toc=/azure/reliability
       - name: Azure Recovery Services vault
         href: migrate-recovery-services-vault.md
       - name: Azure Service Fabric
@@ -267,11 +265,7 @@
       - name: De-identification service
         href: reliability-health-data-services-deidentification.md
     - name: Azure Logic Apps
-      items:
-      - name: Availability zones
-        href: ../logic-apps/set-up-zone-redundancy-availability-zones.md?toc=/azure/reliability/toc.json&bc=/azure/reliability/breadcrumb/toc.json
-      - name: Disaster recovery
-        href: ../logic-apps/business-continuity-disaster-recovery-guidance.md?toc=/azure/reliability/toc.json&bc=/azure/reliability/breadcrumb/toc.json
+      href: reliability-logic-apps.md
   - name: Internet of Things
     items:
     - name: Azure Device Registry

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

@@ -4,11 +4,11 @@
  author: anaharris-ms
  ms.service: azure
  ms.topic: include
- ms.date: 11/12/2024
+ ms.date: 11/19/2024
  ms.author: anaharris
  ms.custom: include file
 ---
 
 Availability zones are physically separate groups of datacenters within each Azure region. When one zone fails, services can fail over to one of the remaining zones.
 
-For more information on availability zones in Azure, see [What are availability zones?](/azure/reliability/availability-zones-overview).
+For more information on availability zones in Azure, see [What are availability zones?](/azure/reliability/availability-zones-overview).

articles/logic-apps/toc.yml

@@ -0,0 +1,27 @@
+---
+ title: include file
+ description: include file
+ author: anaharris-ms
+ ms.service: azure
+ ms.topic: include
+ ms.date: 1/7/2025
+ ms.author: anaharris
+ ms.custom: include file
+---
+
+To prepare for availability zone failure, consider *over-provisioning* the capacity of your service. Over-provisioning allows the solution to tolerate some degree of capacity loss and still continue to function without degraded performance. 
+
+To find out how many instances to over-provision, it's important to know that the platform spreads instances across multiple zones. You need to account for at least the failure of one zone.
+
+Follow these steps to find out the total number of instances you should provision:
+
+1. Determine the number of instances your peak workload requires. In this example, we use two scenarios. One is with 3 instances and one is with 4.
+2. Retrieve the over-provision instance count by multiplying the peak workload instance count by a factor of [(zones/(zones-1)]:
+
+>[!NOTE]
+>The following table assumes that you're using three availability zones. If you use a different number of availability zones, adjust the formula accordingly.
+
+| Peak workload instance count | Factor of  [(zones/(zones-1)]|Formula| Instances to provision (Rounded) |
+|-------|---------|---------|--------|
+|3|3/2 or 1.5|(3 x 1.5 = 4.5)|5 instances|
+|4|3/2 or 1.5|(4 x 1.5 = 4.5)|6 instances|

articles/reliability/TOC.yml

@@ -124,7 +124,7 @@ Below is a list of Azure service reliability guides, organized by service catego
 |Azure Functions|  [Reliability in Azure Functions ](reliability-functions.md)|
 |Azure Health Data Services: De-identification service (preview)|[Reliability in Azure Health Data Services: De-Identification service](reliability-health-data-services-deidentification.md)|
 | Azure Health Data Services: Workspace services (FHIR®, DICOM®, MedTech) | [Business continuity and disaster recovery considerations](/azure/healthcare-apis/business-continuity-disaster-recovery?toc=/azure/reliability/toc.json&bc=/azure/reliability/breadcrumb/toc.json) |
-|Azure Logic Apps|[Protect logic apps from region failures with zone redundancy and availability zones](../logic-apps/set-up-zone-redundancy-availability-zones.md?toc=/azure/reliability/toc.json&bc=/azure/reliability/breadcrumb/toc.json)</p> [Business continuity and disaster recovery for Azure Logic Apps](../logic-apps/business-continuity-disaster-recovery-guidance.md?toc=/azure/reliability/toc.json&bc=/azure/reliability/breadcrumb/toc.json) |
+|Azure Logic Apps|[Reliability in Azure Logic Apps](reliability-logic-apps.md) |
 |Azure Service Bus| [Best practices for insulating applications against Service Bus outages and disasters](../service-bus-messaging/service-bus-outages-disasters.md?toc=/azure/reliability/toc.json&bc=/azure/reliability/breadcrumb/toc.json)|