Convert Azure Public IP from non-zone-redundant to zone-redundant without changing IP

Hello Pavel Radkovič

No, it is not possible to convert an existing Azure Standard Public IP from non‑zone‑redundant to zone‑redundant while retaining the same IP address once the Public IP has already been created and associated with a resource such as an Application Gateway. Microsoft documentation clearly states that the availability zone configuration of a Public IP is immutable after creation, meaning a Public IP that was created as non‑zonal or zonal cannot later be changed to zone‑redundant in place.

Although Microsoft announced in September 2024 that new Standard Public IPs are zone‑redundant by default in supported regions (including Germany West Central), this behavior applies only to newly created Public IPs or Basic‑to‑Standard upgrades and does not retroactively modify existing Standard Public IPs.

For Application Gateway Standard_v2 or WAF_v2, Microsoft confirms that enabling zone redundancy requires redeploying the Application Gateway if it was originally deployed without zone awareness.

The supported migration options are either to deploy a new zone‑redundant Application Gateway with a new zone‑redundant Public IP and perform a DNS cutover, or to delete and redeploy the Application Gateway while reusing the same Public IP only if that IP already meets the desired zonal configuration, which is not the case for non‑zone‑redundant IPs. As a result, there is no supported workaround that preserves the same Public IP address while migrating a non‑zone‑redundant Application Gateway to a zone‑redundant architecture; DNS‑based migration remains the only supported and documented approach for production environments.

Reference docs: https://azure.microsoft.com/en-us/blog/azure-public-ips-are-now-zone-redundant-by-default/

Reference docs: https://docs.azure.cn/en-us/reliability/migrate-app-gateway-v2

Pleaseand “up-vote” wherever the information provided helps you, this can be beneficial to other community members.

Direct in-place conversion of an existing non–zone-redundant Standard public IP to a zone-redundant one while keeping the same IP address is not supported.

Key points from the platform behavior:

• Standard SKU public IPs support availability zones and can be created as non-zonal, zonal, or zone-redundant in regions that support availability zones.
• Once created, a public IP address cannot change its availability zone or zone-redundancy characteristics.
• In regions that did not originally have availability zones, public IPs created there are later made zone-redundant automatically when the region is upgraded, but this does not apply to changing an already non-zonal/zonal IP to zone-redundant on demand.

Because of this immutability, there is no supported way to:

• Take an existing non–zone-redundant Standard public IP, and
• Turn it into a zone-redundant Standard public IP,
• While preserving the exact same IP address.

The supported migration pattern is:

1. Create a new zone-redundant Standard public IP in the same region (Germany West Central) with the desired zone-redundant setting.
2. Associate the new public IP with the Application Gateway frontend configuration.
3. Perform any required DNS updates to point to the new IP.
4. After validation and cutover, remove or repurpose the old non–zone-redundant IP.

This approach does not preserve the original IP, so DNS changes (and associated TTL/propagation planning) are unavoidable when moving to a zone-redundant public IP.

References:

• Public IP addresses
• Upgrade Basic Public IP Address to Standard SKU in Azure
• Create, change, or delete an Azure public IP address
• Manage a public IP address with a load balancer