An Azure networking service that is used to provision private networks and optionally to connect to on-premises datacenters.
Hi @Ivan Alsadi,
Thank you for reaching out on Microsoft Q&A forum.
This behavior is by design and is correctly described in the official Microsoft documentation and the Azure blog.
As stated in the Azure blog “Azure Public IPs are now zone‑redundant by default”, Standard SKU Public IPs in regions that support Availability Zones are zone‑redundant unless you explicitly pin them to a single zone. [azure.microsoft.com]
To verify the configuration, please do the following:
- Open the Public IP resource in the Azure Portal
- Navigate to JSON View
- Take a screenshot of the JSON showing:
-
"sku": { "name": "Standard" }- The
"zones"property
- The
Interpretation of what you see:
- If you see: "zones": [ "1", "2", "3" ] → This is explicit zone‑redundant and is definitive proof.
- If you see: "zones": [ "1" ] → This is zonal, pinned to a single Availability Zone.
Please share a screenshot of the JSON view. If the JSON shows zones 1, 2, 3, that is explicit proof of zone redundancy. If it shows Standard SKU with no zones, that is also considered zone‑redundant by default in Availability Zone–enabled regions.
Kindly let us know if the above helps or you need further assistance on this issue.
If the answer is helpful, kindly upvote it. If you have extra questions about this answer, please click "Comment".