Merge branch 'main' of https://github.com/MicrosoftDocs/azure-docs-pr into advconn

Author: duongau

articles/api-management/TOC.yml

@@ -133,16 +133,16 @@
       href: api-management-configuration-repository-git.md
     - name: DevOps and CI/CD
       href: devops-api-development-templates.md
-  - name: Resiliency
+  - name: Resiliency and reliability
     items:
-    - name: High availability features
+    - name: Reliability in API Management
       displayName: reliability, resilience, resiliency
-      href: high-availability.md
+      href: /azure/reliability/reliability-api-management?toc=%2Fazure%2Fapi-management%2Ftoc.json&bc=/azure/api-management/breadcrumb/toc.json
     - name: Deploy to multiple Azure regions
       href: api-management-howto-deploy-multi-region.md
     - name: Enable availability zones
       displayName: zonal, zone-redundant
-      href: ../reliability/migrate-api-mgt.md?toc=%2Fazure%2Fapi-management%2Ftoc.json&bc=/azure/api-management/breadcrumb/toc.json
+      href: enable-availability-zone-support.md
     - name: Set up DR using backup/restore
       displayName: disaster, recovery
       href: api-management-howto-disaster-recovery-backup-restore.md

articles/api-management/api-management-howto-deploy-multi-region.md

@@ -5,7 +5,7 @@ description: Learn how to deploy a Premium tier Azure API Management instance to
 author: dlepow
 ms.service: azure-api-management
 ms.topic: how-to
-ms.date: 07/29/2024
+ms.date: 07/07/2025
 ms.author: danlep
 ---
 
@@ -19,7 +19,7 @@ When adding a region, you configure:
 
 * The number of scale [units](upgrade-and-scale.md) that region will host. 
 
-* Optional [availability zones](../reliability/migrate-api-mgt.md), if that region supports it.
+* [Availability zones](enable-availability-zone-support.md), if that region supports it. By default, API Management automatically configures availability zones for the added region, which is recommended. You can also manually configure availability zones for the added region.
 
 * [Virtual network](virtual-network-concepts.md) settings in the added region, if networking is configured in the existing region or regions.
 
@@ -35,37 +35,38 @@ When adding a region, you configure:
 
 ## Prerequisites
 
+* Thoroughly understand all requirements and considerations for enabling multi-region deployment in API Management by reading [Reliability in API Management](../reliability/reliability-api-management.md). 
 * If you haven't created an API Management service instance, see [Create an API Management service instance](get-started-create-service-instance.md). Select the Premium service tier.
 * If your API Management instance is deployed in a virtual network, ensure that you set up a virtual network and subnet in the location that you plan to add, and within the same subscription. See [virtual network prerequisites](api-management-using-with-vnet.md#prerequisites).
 
-## <a name="add-region"> </a>Deploy API Management service to an additional region
+## Deploy API Management service to an additional region
 
 1. In the Azure portal, navigate to your API Management service and select **Locations** from the left menu.
 1. Select **+ Add** in the top bar.
 1. Select the added location from the dropdown list.
 1. Select the number of scale **[Units](upgrade-and-scale.md)** in the location.
-1. Optionally select one or more [**Availability zones**](../reliability/migrate-api-mgt.md). 
-1. If the API Management instance is deployed in a [virtual network](api-management-using-with-vnet.md), configure virtual network settings in the location, including virtual network, subnet, and public IP address (if enabling availability zones).
+1. If the region supports [**Availability zones**](enable-availability-zone-support.md), leave the **Automatic** setting (recommended), or optionally select one or more zones. If you select specific zones, the number of units that you selected must distribute evenly across the availability zones. For example, if you selected three units, you would select three zones so that each zone hosts one unit. 
+1. If the API Management instance is deployed in a [virtual network](api-management-using-with-vnet.md), configure virtual network settings in the location, including virtual network, subnet, and public IP address.
 1. Select **Add** to confirm.
 1. Repeat this process until you configure all locations.
 1. Select **Save** in the top bar to start the deployment process.
 
-## <a name="remove-region"> </a>Remove an API Management service region
+## Remove an API Management service region
 
 1. In the Azure portal, navigate to your API Management service and select **Locations** from the left menu.
 1. For the location you would like to remove, select the context menu using the **...** button at the right end of the table. Select **Delete**.
 1. Confirm the deletion and select **Save** to apply the changes.
 
 
-## <a name="route-backend"> </a>Route API calls to regional backend services
+## Route API calls to regional backend services
 
 By default, each API routes requests to a single backend service URL. Even if you've configured Azure API Management gateways in various regions, the API gateway will still forward requests to the same backend service, which is deployed in only one region. In this case, the performance gain will come only from responses cached within Azure API Management in a region specific to the request; contacting the backend across the globe may still cause high latency.
 
 To take advantage of geographical distribution of your system, you should have backend services deployed in the same regions as Azure API Management instances. Then, using policies and `@(context.Deployment.Region)` property, you can route the traffic to local instances of your backend.
 
 1. Navigate to your Azure API Management instance and select **APIs** from the left menu.
 2. Select your desired API.
-3. Select **Code editor** from the arrow dropdown in the **Inbound processing**.
+3. On the **Design** tab, in the **Inbound processing** section, select **Code editor**.
 
     ![API code editor](./media/api-management-howto-deploy-multi-region/api-management-api-code-editor.png)
 
@@ -109,7 +110,7 @@ You may also front your backend services with [Azure Traffic Manager](https://az
 
 * For traffic control during maintenance operations, we recommend using the Priority routing method.
 
-## <a name="custom-routing"> </a>Use custom routing to API Management regional gateways
+## Use custom routing to API Management regional gateways
 
 API Management routes the requests to a regional gateway based on [the lowest latency](../traffic-manager/traffic-manager-routing-methods.md#performance). Although it isn't possible to override this setting in API Management, you can use your own Traffic Manager with custom routing rules.
 
@@ -167,7 +168,7 @@ This section provides considerations for multi-region deployments when the API M
 * Configure each regional network independently. The [connectivity requirements](virtual-network-reference.md) such as required network security group rules for a virtual network in an added region are generally the same as those for a network in the primary region.
 * Virtual networks in the different regions don't need to be peered.
 > [!IMPORTANT]
-> When configured in internal VNet mode, each regional gateway must also have outbound connectivity on port 1433 to the Azure SQL database configured for your API Management instance, which is only in the *primary* region. Ensure that you allow connectivity to the FQDN or IP address of this Azure SQL database in any routes or firewall rules you configure for networks in your secondary regions; the Azure SQL service tag can't be used in this scenario. To find the Azure SQL database name in the primary region, go to the **Network** > **Network status** page of your API Management instance in the portal. 
+> When configured in internal virtual network mode, each regional gateway must also have outbound connectivity on port 1433 to the Azure SQL database configured for your API Management instance, which is only in the *primary* region. Ensure that you allow connectivity to the FQDN or IP address of this Azure SQL database in any routes or firewall rules you configure for networks in your secondary regions; the Azure SQL service endpoint can't be used in this scenario. To find the Azure SQL database name in the primary region, go to the **Network** > **Network status** page of your API Management instance in the portal. 
 
 ### IP addresses
 
@@ -185,10 +186,10 @@ This section provides considerations for multi-region deployments when the API M
 
 ## Related content
 
-* Learn more about configuring API Management for [high availability](high-availability.md).
-
-* Learn more about configuring [availability zones](../reliability/migrate-api-mgt.md) to improve the availability of an API Management instance in a region.
+* Learn more about [reliability in API Management](../reliability/reliability-api-management.md)
 
+* Learn more about enabling [availability zone support](enable-availability-zone-support.md) for an API Management instance.
+    
 * For more information about virtual networks and API Management, see:
 
     * [Connect to a virtual network using Azure API Management](api-management-using-with-vnet.md)

articles/api-management/enable-availability-zone-support.md

@@ -0,0 +1,126 @@
+---
+title: Enable availability zones for Azure API Management instances
+description: Learn how to enable availability zone support on your Premium tier Azure API Management instances.
+author: dlepow 
+ms.service: azure-api-management
+ms.topic: how-to
+ms.date: 07/17/2025
+ms.author: danlep
+ms.custom: references_regions, subject-reliability
+#Customer intent: As an engineer responsible for business continuity, I want to learn how to enable zone redundancy for my Azure API Management instances. 
+---
+
+# Enable availability zone support on Azure API Management instances
+
+[!INCLUDE [premium.md](../../includes/api-management-availability-premium.md)]
+
+This how-to guide shows you how to enable and configure availability zones on an API Management instance. 
+
+For more detailed information about reliability features of API Management, such as availability zones and multi-region deployments, see [Reliability in Azure API Management](../reliability/reliability-api-management.md).
+
+[!INCLUDE [api-management-service-update-behavior](../../includes/api-management-service-update-behavior.md)]
+
+## Prerequisites
+
+* To configure availability zones for API Management, your instance must be in one of the [Azure regions that support availability zones](../reliability/regions-list.md).
+
+* If you don't have an API Management instance, create one by following the [Create a new Azure API Management instance by using the Azure portal](../api-management/get-started-create-service-instance.md) quickstart. Select the **Premium** service tier.
+
+* If you have an existing API Management instance, make sure that it's in the **Premium** (classic) tier. If it isn't, [upgrade to the Premium tier](../api-management/upgrade-and-scale.md#change-your-api-management-service-tier).
+
+## Default availability zone support
+
+When you create a new API Management instance in the **Premium** tier in a region that supports availability zones, or you [deploy API Management to an additional region](api-management-howto-deploy-multi-region.md), API Management offers two types of availability zone support:
+
+*Automatic*. Azure API Management offers automatic availability zone support when you don't specify which availability zones to use.
+
+*Manual*. Azure API Management offers manual availability zone support when you explicitly specify which availability zones to use.
+
+> [!IMPORTANT]
+> To ensure the reliability of your API Management instance, we recommend that you use the automatic availability zone support. To achieve maximum zone redundancy, we recommend that you deploy a minimum of three units in each region where you deploy your API Management instances. For details, see [Reliability in API Management](../reliability/reliability-api-management.md).
+
+## Manual availability zone support
+
+While automatic availability zone configuration is recommended, you can manually configure or update availability zones for an existing location of your API Management instance. The following sections provide steps for manually configuring zone redundancy on an existing location of your API Management instance, depending on whether the instance is injected in a virtual network.
+
+> [!NOTE]
+> You can optionally enable a *zonal* configuration, where the API Management instance or location is deployed in a single availability zone. Because it doesn't provide resiliency to an outage in that zone, this configuration generally isn't recommended except for specific scenarios. For more information, see [Reliability in API Management](../reliability/reliability-api-management.md).
+
+> [!CAUTION]
+> If you manually configure availability zones on an API Management instance that's configured with autoscaling, you might need to adjust your autoscale settings after configuration. In this case, the number of API Management units in autoscale rules and limits must be a multiple of the number of zones. If you simply default to the automatic availability zone support, you don't need to adjust your autoscale settings. 
+
+### Instance not injected in a virtual network
+
+To manually configure availability zone support on an existing location of an API Management instance:
+
+1. Thoroughly understand all requirements and considerations for availability zones in API Management by reading [Reliability in API Management](../reliability/reliability-api-management.md).
+
+1. In the Azure portal, go to your API Management instance.
+
+1. On the **Deployment + infrastructure** menu, select **Locations**.
+
+1. In the **Location** box, select the location to be enabled. The location must support availability zones, as mentioned earlier in the [prerequisites](#prerequisites).
+
+1. In the **Units** box, select the number of scale [units](../api-management/upgrade-and-scale.md) that you want in the location.
+
+1. In the **Availability zones** box, leave the **Automatic** setting (recommended), or optionally select one or more zones. If you select specific zones, the number of units that you selected must distribute evenly across the availability zones. For example, if you selected three units, you would select three zones so that each zone hosts one unit. 
+
+1. Select **Apply**, and then select **Save**.
+
+:::image type="content" alt-text="Screenshot that shows availability zone configuration for an existing location of API Management instance that's not injected in a virtual network." source ="media/enable-availability-zone-support/option-one-not-injected-in-vnet.png":::
+
+### Instance injected in a virtual network
+
+To manually configure availability zone support on an existing location of an API Management instance that's injected in a virtual network:
+
+1. Thoroughly understand all requirements and considerations for enabling zone redundancy in API Management by reading [Reliability in API Management](../reliability/reliability-api-management.md).
+
+1. Create a public IP address in the location to enable availability zones. Detailed requirements are in the [virtual networking guidance](../api-management/api-management-using-with-vnet.md?tabs=stv2#prerequisites).
+
+1. In the Azure portal, go to your API Management instance.
+
+1. On the **Deployment + infrastructure** menu, select **Locations**.
+
+1. In the **Location** box, select the location to be enabled. The location must support availability zones, as mentioned earlier in the [prerequisites](#prerequisites).
+
+1. In the **Units** box, select the number of scale [units](../api-management/upgrade-and-scale.md) that you want in the location.
+
+1. In the **Availability zones** box, leave the **Automatic** setting (recommended), or optionally select one or more zones. If you select specific zones, the number of units that you selected must distribute evenly across the availability zones. For example, if you selected three units, you would select three zones so that each zone hosts one unit.
+
+1. In the **Public IP Address** box, select a public IP address in the location.
+
+1. Select **Apply**, and then select **Save**.
+
+:::image type="content" alt-text="Screenshot that shows availability zone configuration for an existing location of API Management instance that's injected in a virtual network." source ="media/enable-availability-zone-support/option-three-stv2-injected-in-vnet.png":::
+
+## New gateway location
+
+To add a new location to your API Management instance and to configure availability zones in that location:
+
+1. Thoroughly understand all requirements and considerations for enabling availability zones in API Management by reading [Reliability in API Management](../reliability/reliability-api-management.md).
+
+1. If your API Management instance is deployed in a virtual network in the primary location, set up a [virtual network](../api-management/api-management-using-with-vnet.md), subnet, and optional public IP address in the new location where you plan to enable availability zones.
+
+1. In the Azure portal, go to your API Management instance.
+
+1. On the **Deployment + infrastructure** menu, select **Locations**.
+
+1. Select **+ Add** to add a new location. The location must support availability zones, as mentioned earlier in the [prerequisites](#prerequisites).
+
+1. In the **Units** box, select the number of scale [units](../api-management/upgrade-and-scale.md) that you want in the location.
+
+1. In the **Availability zones** box, leave the **Automatic** setting (recommended), or optionally select one or more zones. If you select specific zones, the number of units that you selected must distribute evenly across the availability zones. For example, if you selected three units, you would select three zones so that each zone hosts one unit.
+
+1. If your API Management instance is deployed in a virtual network, use the boxes under **Network** to select the virtual network, subnet, and public IP address that are available in the location.
+
+1. Select **Add**, and then select **Save**.
+
+:::image type="content" alt-text="Screenshot that shows selections for adding a new location for an API Management instance with or without a virtual network." source ="media/enable-availability-zone-support/option-four-add-new-location.png":::
+
+## Related content
+
+- [Reliability in API Management](../reliability/reliability-api-management.md)
+- [Architecture best practices for API Management](/azure/well-architected/service-guides/azure-api-management)
+- [Design review checklist for reliability](/azure/architecture/framework/resiliency/app-design)
+- [Azure services with availability zones](../reliability/availability-zones-service-support.md)
+- [Azure regions with availability zones](../reliability/regions-list.md)