Skip to content

Commit 4e2c400

Browse files
committed
Learn Editor: Update migrate-api-mgt.md
1 parent 1fbba4a commit 4e2c400

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/reliability/migrate-api-mgt.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ There are no downtime requirements for any of the migration options.
3636

3737
* When you're migrating an API Management instance that's deployed in an external or internal virtual network to availability zones, you must specify a new public IP address resource. In an internal virtual network, the public IP address is used only for management operations, not for API requests. [Learn more about IP addresses of API Management](../api-management/api-management-howto-ip-addresses.md).
3838

39-
* Migrating to availability zones or changing the configuration of availability zones triggers a public [IP address change](../api-management/api-management-howto-ip-addresses.md#changes-to-the-ip-addresses).
39+
* Migrating to availability zones or changing the configuration of availability zones triggers a public and private [IP address change](../api-management/api-management-howto-ip-addresses.md#changes-to-the-ip-addresses).
4040

4141
* When you're enabling availability zones in a region, you configure API Management scale [units](../api-management/upgrade-and-scale.md) that you can distribute evenly across the zones. For example, if you configure two zones, you can configure two units, four units, or another multiple of two units.
4242

0 commit comments

Comments
 (0)