APIM zone redundant changes

Question

APIM zone redundant changes

Eddie Vincent 205

Scenario: Upgrading an older version of APIM (pre 2024) to add zone redundancy/resiliency.

Platform version stv2.1.
Premium SKU.
VNet injected APIM version.
Standard public IP address (pre-zone redundancy feature).
Internal VNet option: https://free.blessedness.top/en-us/azure/api-management/api-management-using-with-internal-vnet
Deploying via code (not Azure portal) preferred.
APIM is within a supported region for this setup.
Wanting to change the public IP address to zone redundant and the "locations" section within APIM itself - units and availability zones section as can be seen below.

User's image

With the above points in mind I am looking for the best way of doing this, especially when taking into account the decoupled nature of the Public IP address and APIM instance (since the below is now apparently possible also).

User's image

Questions include:

Is an APIM instance with the managed "no public IP" option (May 2024) only available for newly built APIM instances and not pre-existing?
If no then how would you upgrade to a managed option from pre-existing APIM?
If yes what are the concerns about future proofing the environment, were the non-managed/decoupled option ever to become EOL.

Appreciate any constructive responses, thanks!

Pravallika KV 165 Reputation points Microsoft External Staff Moderator

2025-10-23T08:46:15.4366667+00:00

Hi Eddie Vincent, following up to see if above provided response was helpful. If you have any further queries, do let us know.
Eddie Vincent 205 Reputation points

2025-10-23T11:34:58.8433333+00:00

All good with me, thankyou for your quick response.
Pravallika KV 165 Reputation points Microsoft External Staff Moderator

2025-10-23T11:47:35.6+00:00

Thanks for the confirmation @Eddie Vincent. I have posted the answer. Please accept as Yes if the answer is helpful so that it can help others in the community. If you any further queries, do let us know.

Answer accepted by question author

0 additional answers

Your answer

Pravallika KV 165 Reputation points Microsoft External Staff Moderator

2025-10-23T08:46:15.4366667+00:00

Hi Eddie Vincent, following up to see if above provided response was helpful. If you have any further queries, do let us know.
Eddie Vincent 205 Reputation points

2025-10-23T11:34:58.8433333+00:00

All good with me, thankyou for your quick response.
Pravallika KV 165 Reputation points Microsoft External Staff Moderator

2025-10-23T11:47:35.6+00:00

Thanks for the confirmation @Eddie Vincent. I have posted the answer. Please accept as Yes if the answer is helpful so that it can help others in the community. If you any further queries, do let us know.

Answer 1

Hi Eddie Vincent,

Thanks for reaching out to Microsoft Q&A,

Pre-2024 APIM instances cannot directly switch to the fully managed “no public IP” option; it’s only available for new deployments.
Zone redundancy requires adding multiple units and specifying availability zones in the locations section.
Existing public IPs can be decoupled, but upgrading to a managed zone-redundant IP usually requires creating a new IP.
Future-proofing favors using decoupled or managed IPs to simplify scaling and ensure resiliency.
Migration to a new managed APIM instance is recommended for full AZ and managed IP benefits.
Deployment via ARM/Bicep/terraform allows code-driven updates of units, zones, and public IP assignments.

Hope it helps!

Please do not forget to click "Accept the answer” and Yes, this can be beneficial to other community members.

User's image

If you have any other questions, let me know in the "comments" and I would be happy to help you.

Share via

APIM zone redundant changes

0 additional answers

Your answer