You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/virtual-network/ip-services/public-ip-addresses.md
+17-18Lines changed: 17 additions & 18 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -70,7 +70,6 @@ Full details are listed in the table below:
70
70
|[Routing preference](routing-preference-overview.md)| Supported to enable more granular control of how traffic is routed between Azure and the Internet. | Not supported.|
71
71
| Global tier | Supported via [cross-region load balancers](../../load-balancer/cross-region-overview.md).| Not supported. |
72
72
73
-
74
73
Virtual machines attached to a backend pool do not need a public IP address to be attached to a public load balancer. But if they do, matching SKUs are required for load balancer and public IP resources. You can't have a mixture of basic SKU resources and standard SKU resources. You can't attach standalone virtual machines, virtual machines in an availability set resource, or a virtual machine scale set resources to both SKUs simultaneously. New designs should consider using Standard SKU resources. For more information about a standard load balancer, see [Standard Load Balancer](../../load-balancer/load-balancer-overview.md?toc=%2fazure%2fvirtual-network%2ftoc.json).
75
74
76
75
## IP address assignment
@@ -94,6 +93,23 @@ Static public IP addresses are commonly used in the following scenarios:
94
93
| Basic public IPv4 |:white_check_mark:|:white_check_mark:|
95
94
| Basic public IPv6 | x |:white_check_mark:|
96
95
96
+
## Availability Zone
97
+
98
+
Standard SKU Public IPs can be created as non-zonal, zonal, or zone-redundant in [regions that support availability zones](../../availability-zones/az-region.md). Basic SKU Public IPs do not have any zones and are created as non-zonal.
99
+
A public IP's availability zone can't be changed after the public IP's creation.
100
+
101
+
| Value | Behavior |
102
+
| --- | --- |
103
+
| Non-zonal | A non-zonal public IP address is placed into a zone for you by Azure and doesn't give a guarantee of redundancy. |
104
+
| Zonal | A zonal IP is tied to a specific availability zone, and shares fate with the health of the zone. |
105
+
| Zone-redundant | A zone-redundant IP is created in all zones for a region and can survive any single zone failure. |
106
+
107
+
In regions without availability zones, all public IP addresses are created as nonzonal. Public IP addresses created in a region that is later upgraded to have availability zones remain non-zonal.
108
+
109
+
> [!IMPORTANT]
110
+
> We are updating Standard non-zonal IPs to be zone-redundant by default on a region by region basis. This means that in the following 12 regions, all IPs created (except zonal) are zone-redundant.
111
+
> Region availability: Central Canada, Central Poland, Central Israel, Central France, Central Qatar, East Norway, Italy North, Sweden Central, South Africa North, South Brazil, West Central Germany, West US 2.
112
+
97
113
## Domain Name Label
98
114
99
115
Select this option to specify a DNS label for a public IP resource. This functionality works for both IPv4 addresses (32-bit A records) and IPv6 addresses (128-bit AAAA records). This selection creates a mapping for **domainnamelabel**.**location**.cloudapp.azure.com to the public IP in the Azure-managed DNS.
@@ -128,23 +144,6 @@ The value of the **Domain Name Label Scope** must match one of the options below
128
144
129
145
For example, if **SubscriptionReuse** is selected as the option, and a customer who has the example domain name label **contoso.fjdng2acavhkevd8.westus.cloudapp.Azure.com** deletes and re-deploys a public IP address using the same template as before, the domain name label will remain the same. If the customer deploys a public IP address using this same template under a different subscription, the domain name label would change (e.g. **contoso.c9ghbqhhbxevhzg9.westus.cloudapp.Azure.com**).
130
146
131
-
## Availability Zone
132
-
133
-
Standard SKU Public IPs can be created as non-zonal, zonal, or zone-redundant in [regions that support availability zones](../../availability-zones/az-region.md). Basic SKU Public IPs do not have any zones and are created as non-zonal.
134
-
A public IP's availability zone can't be changed after the public IP's creation.
135
-
136
-
| Value | Behavior |
137
-
| --- | --- |
138
-
| Non-zonal | A non-zonal public IP address is placed into a zone for you by Azure and doesn't give a guarantee of redundancy. |
139
-
| Zonal | A zonal IP is tied to a specific availability zone, and shares fate with the health of the zone. |
140
-
| Zone-redundant | A zone-redundant IP is created in all zones for a region and can survive any single zone failure. |
141
-
142
-
In regions without availability zones, all public IP addresses are created as nonzonal. Public IP addresses created in a region that is later upgraded to have availability zones remain non-zonal.
143
-
144
-
> [!IMPORTANT]
145
-
> We are updating Standard non-zonal IPs to be zone-redundant by default on a region by region basis. This means that in the following 12 regions, all IPs created (except zonal) are zone-redundant.
146
-
> Region availability: Central Canada, Central Poland, Central Israel, Central France, Central Qatar, East Norway, Italy North, Sweden Central, South Africa North, South Brazil, West Central Germany, West US 2.
147
-
148
147
## Other public IP address features
149
148
150
149
There are other attributes that can be used for a public IP address (Standard SKU only).
0 commit comments