Merge pull request #276077 from dlepow/patch-287

[APIM] Update api-management-howto-ip-addresses.md

Author: prmerger-automator[bot]

articles/api-management/api-management-howto-ip-addresses.md

@@ -133,7 +133,7 @@ In the Developer, Basic, Standard, and Premium tiers of API Management, the publ
 * The service subscription is disabled or warned (for example, for nonpayment) and then reinstated. [Learn more about subscription states](/azure/cost-management-billing/manage/subscription-states)
 * (Developer and Premium tiers) Azure Virtual Network is added to or removed from the service.
 * (Developer and Premium tiers) API Management service is switched between external and internal VNet deployment mode.
-* (Developer and Premium tiers) API Management service is moved to a different subnet, or [migrated](migrate-stv1-to-stv2.md) from the `stv1` to the `stv2` compute platform.
+* (Developer and Premium tiers) API Management service is moved to a different subnet, [migrated](migrate-stv1-to-stv2.md) from the `stv1` to the `stv2` compute platform, or configured with a different public IP address resource.
 * (Premium tier) [Availability zones](../reliability/migrate-api-mgt.md) are enabled, added, or removed.
 * (Premium tier) In [multi-regional deployments](api-management-howto-deploy-multi-region.md), the regional IP address changes if a region is vacated and then reinstated.
 
@@ -144,4 +144,4 @@ In the Developer, Basic, Standard, and Premium tiers of API Management, the publ
 
 - [Deploy API Management to a virtual network - external mode](api-management-using-with-vnet.md)
 - [Deploy API Management to a virtual network - internal mode](api-management-using-with-internal-vnet.md)
-- [Using a virtual network with Azure API Management](virtual-network-concepts.md)
+- [Using a virtual network with Azure API Management](virtual-network-concepts.md)