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
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -44,7 +44,7 @@ There are no downtime requirements for any of the migration options.
44
44
45
45
* If you 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.
46
46
47
-
## Migrate an existing location of an API Management instance that's not injected in a virtual network
47
+
## Existing gateway location not injected in a virtual network
48
48
49
49
To migrate an existing location of your API Management instance to availability zones when the instance is not injected in a virtual network:
50
50
@@ -62,7 +62,7 @@ To migrate an existing location of your API Management instance to availability
62
62
63
63
:::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":::
64
64
65
-
## Migrate an existing location of an API Management instance (stv1 platform) that's injected in a virtual network
65
+
## Existing gateway location (stv1 platform) injected in a virtual network
66
66
67
67
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.
68
68
@@ -84,7 +84,7 @@ To migrate an existing location of your API Management instance to availability
84
84
85
85
:::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":::
86
86
87
-
## Migrate an existing location of an API Management instance (stv2 platform) that's injected in a virtual network
87
+
## Existing gateway location (stv2 platform) injected in a virtual network
88
88
89
89
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:
90
90
@@ -106,7 +106,7 @@ To migrate an existing location of your API Management instance to availability
106
106
107
107
:::image type="content" alt-text="Screenshot that shows selections for migrating an existing location of an API Management instance (stv2 platform) that's injected in a virtual network." source ="media/migrate-api-mgt/option-three-stv2-injected-in-vnet.png":::
108
108
109
-
## Add a new location for an API Management instance (with or without a virtual network) with availability zones
109
+
## New gateway location
110
110
111
111
To add a new location to your API Management instance and enable availability zones in that location:
0 commit comments