Skip to content

Commit 13381c1

Browse files
authored
Update migrate-api-mgt.md
1 parent de3f125 commit 13381c1

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

articles/reliability/migrate-api-mgt.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -44,7 +44,7 @@ There are no downtime requirements for any of the migration options.
4444

4545
* 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.
4646

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
4848

4949
To migrate an existing location of your API Management instance to availability zones when the instance is not injected in a virtual network:
5050

@@ -62,7 +62,7 @@ To migrate an existing location of your API Management instance to availability
6262

6363
:::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":::
6464

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
6666

6767
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.
6868

@@ -84,7 +84,7 @@ To migrate an existing location of your API Management instance to availability
8484

8585
:::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":::
8686

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
8888

8989
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:
9090

@@ -106,7 +106,7 @@ To migrate an existing location of your API Management instance to availability
106106

107107
:::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":::
108108

109-
## Add a new location for an API Management instance (with or without a virtual network) with availability zones
109+
## New gateway location
110110

111111
To add a new location to your API Management instance and enable availability zones in that location:
112112

0 commit comments

Comments
 (0)