What is new public ip used for when migrating the existing APIM to availability zone

Question

Hi, we're checking the feasibility of availability zone to the existing APIM (single region) and curious about the "new public IP" part in the message.

The migration document says "There are no downtime requirements for any of the migration options."

https://learn.microsoft.com/en-us/azure/reliability/migrate-api-mgt#downtime-requirements

and we need to prepare a new public IP address to prevent from the downtime.

Question :

1. Not sure what is under the hood when doing migration.
2. After the migration, which public IP will be used ? the original one or the newly created one ?
3. Do we have to change the related ACL for possible public IP change ?

Thank you

Answer 1

Hi , Welcome to MS Q&A

To answer your questions , please check below

1. Migration Process: The migration process for APIM involves transferring your APIM configuration, including APIs, policies, subscriptions, and other settings, from one environment to another. This could be from a development to a production environment, between regions, or across different deployment types (e.g., from a standalone to a highly available configuration).
2. Which public IP will be used after migration: the original one or the newly created one? After migration, the public IP address used depends on the migration scenario and configuration changes made during the process. If you're migrating within the same region and keeping the same deployment topology (e.g., no change in availability zones), the original public IP address associated with your APIM instance may continue to be used. However, if you're migrating to a new region, changing the deployment topology (e.g., enabling availability zones), or for other reasons requiring a new public IP, a newly created public IP address would be used.
3. Do we have to change the related ACL for public IP change? Yes, if you're using Access Control Lists (ACLs) to restrict access to your APIM instance based on IP addresses, you'll likely need to update the ACL rules to include the new public IP address after migration.

Please let me know if further questions , kindly accept answer , if it helps, Thanks!

Answer 2

@NC0202 Thanks for reaching out.

When migrating an API Management instance to availability zones, a new public IP address resource must be specified. After the migration, the newly created public IP address will be used for management operations, but the original public IP address will continue to be used for API requests.

This means that you do not need to update the firewall rules or any other access control lists that reference the public IP address of your API Management instance.

However, if you have configured custom domains for your APIs, you will need to update the DNS records to point to the new public IP address.