Merge pull request #200119 from anaharris-ms/az-api-mgt

API Management AZ Migration doc

Author: liljack17

articles/availability-zones/TOC.yml

@@ -16,6 +16,8 @@
     href: az-region.md
   - name: Migration Guidance
     items:
+    - name: API Management
+      href: migrate-api-mgt.md
     - name: App Service Environment
       href: migrate-app-service-environment.md
     - name: App Service
@@ -26,6 +28,8 @@
       href: migrate-vm.md
     - name: Storage accounts
       href: migrate-storage.md
+    - name: Virtual Machines and Virtual Machine Scale Sets
+      href: migrate-vm.md
   - name: Terminology
     href: glossary.md
 - name: High Availability

articles/availability-zones/az-region.md

@@ -93,7 +93,7 @@ In the Product Catalog, always-available services are listed as "non-regional" s
 | **Products**   | **Resiliency**   |
 | --- | --- |
 | [Azure Active Directory Domain Services](../active-directory-domain-services/overview.md) | ![An icon that signifies this service is zone redundant.](media/icon-zone-redundant.svg) |
-| [Azure API Management](../api-management/zone-redundancy.md) | ![An icon that signifies this service is zone redundant.](media/icon-zone-redundant.svg) |
+| [Azure API Management](migrate-api-mgt.md) | ![An icon that signifies this service is zone redundant.](media/icon-zone-redundant.svg) |
 | [Azure App Configuration](../azure-app-configuration/faq.yml#how-does-app-configuration-ensure-high-data-availability) | ![An icon that signifies this service is zone redundant.](media/icon-zone-redundant.svg) |
 | [Azure App Service](migrate-app-service.md) | ![An icon that signifies this service is zone redundant.](media/icon-zone-redundant.svg) |
 | [Azure App Service: App Service Environment](migrate-app-service-environment.md) | ![An icon that signifies this service is zone redundant.](media/icon-zone-redundant.svg) ![An icon that signifies this service is zonal](media/icon-zonal.svg) |

articles/availability-zones/media/migrate-api-mgt/option-four-add-new-location.png

@@ -0,0 +1,163 @@
+---
+title: Migrate Azure API Management to availability zone support
+description: Learn how to migrate your Azure API Management instances to availability zone support.
+author: anaharris-ms
+ms.service: api-management
+ms.topic: how-to
+ms.date: 07/07/2022
+ms.author: anaharris
+ms.custom: references_regions
+
+---
+
+# Migrate Azure API Management to availability zone support
+
+This guide describes how to enable availability zone support for your API Management instance. The API Management service supports [Zone redundancy](../availability-zones/az-overview.md#availability-zones), which provides resiliency and high availability to a service instance in a specific Azure region. With zone redundancy, the gateway and the control plane of your API Management instance (Management API, developer portal, Git configuration) are replicated across datacenters in physically separated zones, making it resilient to a zone failure.
+
+In this article, we'll take you through the different options for availability zone migration.
+
+## Prerequisites
+
+* To configure API Management for zone redundancy, your instance must be in one of the following regions:
+    
+    * 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 (*)
+    * North Europe
+    * Norway East (*)
+    * South Africa North (*)
+    * South Central US
+    * Southeast Asia
+    * Switzerland North
+    * UK South
+    * West Europe
+    * West US 2
+    * West US 3
+
+    > [!IMPORTANT]
+    > The regions with * against them have restrictive access in an Azure subscription to enable availability zone support. Please work with your Microsoft sales or customer representative.
+
+* If you haven't yet created an API Management service instance, see [Create an API Management service instance](../api-management/get-started-create-service-instance.md). Select the Premium service tier.
+
+* API Management service must be in the Premium tier. If it isn't, you can [upgrade](../api-management/upgrade-and-scale.md#change-your-api-management-service-tier) to the Premium tier.
+
+* If your API Management instance is deployed (injected) in a [Azure virtual network (VNet)](../api-management/api-management-using-with-vnet.md), check the version of the [compute platform](../api-management/compute-infrastructure.md) (stv1 or stv2) that hosts the service.
+
+## Downtime requirements
+
+There are no downtime requirements for any of the migration options.
+
+## Considerations
+
+* Changes can take from 15 to 45 minutes to apply. The API Management gateway can continue to handle API requests during this time.
+
+* Migrating to availability zones or changing the availability zone configuration will trigger a public IP address change.
+
+* If you've configured autoscaling for your API Management instance in the primary location, you might need to adjust your autoscale settings after enabling zone redundancy. The number of API Management units in autoscale rules and limits must be a multiple of the number of zones.
+
+
+## Option 1: Migrate existing location of API Management instance, not injected in VNet
+
+Use this option to migrate an existing location of your API Management instance to availability zones when it’s not injected (deployed) in a virtual network.
+
+### How to migrate API Management in a VNet
+
+1.	In the Azure portal, navigate to your API Management service.
+
+1.	Select **Locations** in the menu, and then select the location to be migrated. The location must [support availability zones](#prerequisites).
+
+1.	Select the number of scale [Units](../api-management/upgrade-and-scale.md) desired in the location.
+
+1.	In **Availability zones**, select one or more zones. The number of units selected must be distributed evenly across the availability zones. For example, if you selected 3 units, select 3 zones so that each zone hosts one unit.
+
+1.	Select **Apply**, and then select **Save**.
+
+     :::image type="content" alt-text="Screenshot of how to migrate existing location of API Management instance not injected in VNet." source ="media/migrate-api-mgt/option-one-not-injected-in-vnet.png":::
+    
+
+
+## Option 2: Migrate existing location of API Management instance (stv1 platform), injected in  VNet
+
+Use this option to migrate an existing location of your API Management instance to availability zones when it is currently injected (deployed) in a virtual network. The following steps are needed when the API Management instance is currently hosted on the stv1 platform. Migrating to availability zones will also migrate the instance to the stv2 platform.
+
+1.	Create a new subnet and public IP address in location to migrate to availability zones. Detailed requirements are in [virtual networking guidance](../api-management/api-management-using-with-vnet.md?tabs=stv2#prerequisites).
+
+1.	In the Azure portal, navigate to your API Management service.
+
+1.	Select **Locations** in the menu, and then select the location to be migrated. The location must [support availability zones](#prerequisites).
+
+1.	Select the number of scale [Units](../api-management/upgrade-and-scale.md) desired in the location.
+
+1.	In **Availability zones**, select one or more zones. The number of units selected must be distributed evenly across the availability zones. For example, if you selected 3 units, select 3 zones so that each zone hosts one unit.
+
+1.	Select the new subnet and new public IP address in the location. 
+
+1.	Select **Apply**, and then select **Save**.
+
+
+     :::image type="content" alt-text="Screenshot of how to migrate existing location of API Management instance injected in VNet." source ="media/migrate-api-mgt/option-two-injected-in-vnet.png":::
+
+## Option 3: Migrate existing location of API Management instance (stv2 platform), injected in VNet
+
+Use this option to migrate an existing location of your API Management instance to availability zones when it is currently injected (deployed) in a virtual network. The following steps are used when the API Management instance is already hosted on the stv2 platform.
+
+1.	Create a new subnet and public IP address in location to migrate to availability zones. Detailed requirements are in [virtual networking guidance](../api-management/api-management-using-with-vnet.md?tabs=stv2#prerequisites).
+
+1.	In the Azure portal, navigate to your API Management service.
+
+1.	Select **Locations** in the menu, and then select the location to be migrated. The location must [support availability zones](#prerequisites).
+
+1.	Select the number of scale [Units](../api-management/upgrade-and-scale.md) desired in the location.
+
+1.	In **Availability zones**, select one or more zones. The number of units selected must be distributed evenly across the availability zones. For example, if you selected 3 units, select 3 zones so that each zone hosts one unit.
+
+1.	Select the new public IP address in the location. 
+
+1.	Select **Apply**, and then select **Save**.
+
+     :::image type="content" alt-text="Screenshot of how to migrate existing location of API Management instance (stv2 platform) injected in VNet." source ="media/migrate-api-mgt/option-three-stv2-injected-in-vnet.png":::
+
+## Option 4. Add new location for API Management instance (with or without VNet) with availability zones
+
+Use this option to add a new location to your API Management instance and enable availability zones in that location. 
+
+If your API Management instance is deployed in a virtual network in the primary location, ensure that you set up a [virtual network](../api-management/api-management-using-with-vnet.md?tabs=stv2), subnet, and public IP address in any new location where you plan to enable zone redundancy.
+
+1.	In the Azure portal, navigate to your API Management service.
+
+1.	Select **+ Add** in the top bar to add a new location. The location must [support availability zones](#prerequisites).
+
+1.	Select the number of scale [Units](../api-management/upgrade-and-scale.md) desired in the location.
+
+1.	In **Availability zones**, select one or more zones. The number of units selected must be distributed evenly across the availability zones. For example, if you selected 3 units, select 3 zones so that each zone hosts one unit.
+
+1. If your API Management instance is deployed in a [virtual network](../api-management/api-management-using-with-vnet.md?tabs=stv2), 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 of how to add new location for API Management instance with or without VNet." source ="media/migrate-api-mgt/option-four-add-new-location.png":::
+
+## Next steps
+
+Learn more about:
+
+> [!div class="nextstepaction"]
+> [deploying an Azure API Management service instance to multiple Azure regions](../api-management/api-management-howto-deploy-multi-region.md).
+
+> [!div class="nextstepaction"]
+> [building for reliability](/azure/architecture/framework/resiliency/app-design) in Azure.
+
+> [!div class="nextstepaction"]
+> [Regions and Availability Zones in Azure](az-overview.md)
+
+> [!div class="nextstepaction"]
+> [Azure Services that support Availability Zones](az-region.md)