Skip to content

Commit 857acac

Browse files
author
gitName
committed
backed out reliability article
1 parent e9eae4c commit 857acac

File tree

1 file changed

+27
-5
lines changed

1 file changed

+27
-5
lines changed

articles/reliability/migrate-api-mgt.md

Lines changed: 27 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,10 @@
11
---
2-
title: Migrate Azure API Management to Availability Zones
2+
title: Migrate Azure API Management to availability zones
33
description: Learn how to migrate your Azure API Management instances to availability zones for zone redundancy.
44
author: shaunjacob
55
ms.service: azure-api-management
66
ms.topic: how-to
7-
ms.date: 04/17/2025
7+
ms.date: 10/16/2024
88
ms.author: anaharris
99
ms.custom: subject-reliability
1010

@@ -18,7 +18,7 @@ The Azure API Management service supports [availability zones](../reliability/av
1818

1919
* **Zone-redundant** - the gateway and the control plane of your API Management instance (management API, developer portal, Git configuration) are replicated across two or more physically separated zones within an Azure region. Zone redundancy provides resiliency and high availability to a service instance.
2020

21-
This article describes three scenarios for migrating an API Management instance to availability zones. For more information about configuring API Management for high availability, see [Ensure API Management availability and reliability](../api-management/high-availability.md).
21+
This article describes four scenarios for migrating an API Management instance to availability zones. For more information about configuring API Management for high availability, see [Ensure API Management availability and reliability](../api-management/high-availability.md).
2222

2323
[!INCLUDE [api-management-service-update-behavior](../../includes/api-management-service-update-behavior.md)]
2424

@@ -30,6 +30,7 @@ This article describes three scenarios for migrating an API Management instance
3030

3131
* If you have an existing API Management instance, make sure that it's in the Premium tier. If it isn't, [upgrade to the Premium tier](../api-management/upgrade-and-scale.md#change-your-api-management-service-tier).
3232

33+
3334
## Downtime requirements
3435

3536
There are no downtime requirements for any of the migration options.
@@ -66,10 +67,31 @@ To migrate an existing location of your API Management instance to availability
6667

6768
:::image type="content" alt-text="Screenshot that shows selections for migrating an existing location of API Management instance that's not injected in a virtual network." source ="media/migrate-api-mgt/option-one-not-injected-in-vnet.png":::
6869

70+
## Existing gateway location (stv1 platform) injected in a virtual network
71+
72+
To migrate an existing location of your API Management instance to availability zones when the instance is currently injected in a virtual network and is currently hosted on the `stv1` platform, use the following steps. Migrating to availability zones also migrates the instance to the `stv2` platform.
73+
74+
1. Create a new subnet and optional public IP address in the location to migrate to availability zones. Detailed requirements are in the [virtual networking guidance](../api-management/api-management-using-with-vnet.md?tabs=stv2#prerequisites).
75+
76+
1. In the Azure portal, go to your API Management instance.
77+
78+
1. On the **Deployment + infrastructure** menu, select **Locations**.
79+
80+
1. In the **Location** box, select the location to be migrated. The location must support availability zones, as mentioned earlier in the [prerequisites](#prerequisites).
81+
82+
1. In the **Units** box, select the number of scale [units](../api-management/upgrade-and-scale.md) that you want in the location.
83+
84+
1. In the **Availability zones** box, select one or more zones. The number of units that you selected must be distributed evenly across the availability zones. For example, if you selected three units, select three zones so that each zone hosts one unit.
85+
86+
1. In the respective boxes under **Network**, select the new subnet and optional public IP address in the location.
87+
88+
1. Select **Apply**, and then select **Save**.
89+
90+
:::image type="content" alt-text="Screenshot that shows selections for migrating an existing location of an API Management instance that's injected in a virtual network." source ="media/migrate-api-mgt/option-two-injected-in-vnet.png":::
6991

70-
## Existing gateway location injected in a virtual network
92+
## Existing gateway location (stv2 platform) injected in a virtual network
7193

72-
To migrate an existing location of your API Management instance to availability zones when the instance is currently injected in a virtual network:
94+
To migrate an existing location of your API Management instance to availability zones when the instance is currently injected in a virtual network and is already hosted on the `stv2` platform:
7395

7496
1. In the Azure portal, go to your API Management instance.
7597

0 commit comments

Comments
 (0)