You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/reliability/migrate-api-mgt.md
+27-5Lines changed: 27 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,10 +1,10 @@
1
1
---
2
-
title: Migrate Azure API Management to Availability Zones
2
+
title: Migrate Azure API Management to availability zones
3
3
description: Learn how to migrate your Azure API Management instances to availability zones for zone redundancy.
4
4
author: shaunjacob
5
5
ms.service: azure-api-management
6
6
ms.topic: how-to
7
-
ms.date: 04/17/2025
7
+
ms.date: 10/16/2024
8
8
ms.author: anaharris
9
9
ms.custom: subject-reliability
10
10
@@ -18,7 +18,7 @@ The Azure API Management service supports [availability zones](../reliability/av
18
18
19
19
***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.
20
20
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).
@@ -30,6 +30,7 @@ This article describes three scenarios for migrating an API Management instance
30
30
31
31
* 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).
32
32
33
+
33
34
## Downtime requirements
34
35
35
36
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
66
67
67
68
:::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":::
68
69
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":::
69
91
70
-
## Existing gateway location injected in a virtual network
92
+
## Existing gateway location (stv2 platform) injected in a virtual network
71
93
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:
73
95
74
96
1. In the Azure portal, go to your API Management instance.
0 commit comments