Skip to content

Commit 3a3439f

Browse files
authored
Update public-ip-addresses.md
1 parent b35d117 commit 3a3439f

File tree

1 file changed

+10
-30
lines changed

1 file changed

+10
-30
lines changed

articles/virtual-network/ip-services/public-ip-addresses.md

Lines changed: 10 additions & 30 deletions
Original file line numberDiff line numberDiff line change
@@ -50,41 +50,21 @@ Public IP addresses can be created with an IPv4 or IPv6 address. You may be give
5050

5151
Public IP addresses are created with one of the following SKUs:
5252

53-
### Standard
53+
| | Standard | Basic |
54+
| --- | --- | --- |
55+
| | Always use static allocation method.| For IPv4: Can be assigned using the dynamic or static allocation method. For IPv6: Can only be assigned using the dynamic allocation method.|
56+
| | Have an adjustable inbound originated flow idle timeout of 4-30 minutes, with a default of 4 minutes, and fixed outbound originated flow idle timeout of 4 minutes.|Have an adjustable inbound originated flow idle timeout of 4-30 minutes, with a default of 4 minutes, and fixed outbound originated flow idle timeout of 4 minutes.|
57+
| | - Designed to align with the "secure by default" model and be closed to inbound traffic when used as a frontend. Allowlisting data plane traffic with [network security group](../../virtual-network/network-security-groups-overview.md#network-security-groups) (NSG) is required (for example, on the NIC of a virtual machine with a Standard SKU Public IP attached).| Are open by default. Network security groups are recommended but optional for restricting inbound or outbound traffic.|
58+
| | Can be zone-redundant (which is advertised from all three zones), zonal (which is guaranteed in a specific pre-selected availability zone), or "no-zone" (which isn't associated with a specific pre-selected availability zone). To learn more about availability zones, see [Availability zones overview](../../availability-zones/az-overview.md?toc=%2fazure%2fvirtual-network%2ftoc.json) and [Standard Load Balancer and Availability Zones](../../load-balancer/load-balancer-standard-availability-zones.md?toc=%2fazure%2fvirtual-network%2ftoc.json). **Zone redundant IPs can only be created in [regions where three availability zones](../../availability-zones/az-region.md) are live.** IPs created before zones are live won't be zone redundant. | Don't support Availability Zone scenarios. Use standard SKU public IP for Availability Zone scenarios in applicable regions. To learn more about availability zones, see [Availability zones overview](../../availability-zones/az-overview.md?toc=%2fazure%2fvirtual-network%2ftoc.json) and [Standard Load Balancer and Availability Zones](../../load-balancer/load-balancer-standard-availability-zones.md?toc=%2fazure%2fvirtual-network%2ftoc.json).|
59+
| | Can be utilized with the [routing preference](routing-preference-overview.md) to enable more granular control of how traffic is routed between Azure and the Internet. | Don't support [routing preference](routing-preference-overview.md) or [cross-region load balancers](../../load-balancer/cross-region-overview.md) functionality.|
60+
| | Can be used as anycast frontend IPs for [cross-region load balancers](../../load-balancer/cross-region-overview.md) (preview functionality).|
5461

55-
Standard SKU public IP addresses:
56-
57-
- Always use static allocation method.
58-
- Have an adjustable inbound originated flow idle timeout of 4-30 minutes, with a default of 4 minutes, and fixed outbound originated flow idle timeout of 4 minutes.
59-
- Designed to align with the "secure by default" model and be closed to inbound traffic when used as a frontend. Allowlisting data plane traffic with [network security group](../../virtual-network/network-security-groups-overview.md#network-security-groups) (NSG) is required (for example, on the NIC of a virtual machine with a Standard SKU Public IP attached).
60-
- Can be zone-redundant (which is advertised from all three zones), zonal (which is guaranteed in a specific pre-selected availability zone), or "no-zone" (which isn't associated with a specific pre-selected availability zone). To learn more about availability zones, see [Availability zones overview](../../availability-zones/az-overview.md?toc=%2fazure%2fvirtual-network%2ftoc.json) and [Standard Load Balancer and Availability Zones](../../load-balancer/load-balancer-standard-availability-zones.md?toc=%2fazure%2fvirtual-network%2ftoc.json). **Zone redundant IPs can only be created in [regions where three availability zones](../../availability-zones/az-region.md) are live.** IPs created before zones are live won't be zone redundant.
61-
- Can be utilized with the [routing preference](routing-preference-overview.md) to enable more granular control of how traffic is routed between Azure and the Internet.
62-
- Can be used as anycast frontend IPs for [cross-region load balancers](../../load-balancer/cross-region-overview.md) (preview functionality).
63-
64-
> [!NOTE]
65-
> Only public IP addresses with basic SKU are available when using [instance metadata service IMDS](../../virtual-machines/windows/instance-metadata-service.md). Standard SKU is not supported.
66-
67-
> [!NOTE]
68-
> Diagnostic settings don't appear under the resource blade when using a standard SKU public IP address. To enable logging on your standard public IP address resource, navigate to diagnostic settings under the Azure Monitor blade and select your IP address resource.
69-
70-
> [!NOTE]
71-
> Inbound communication with a Standard SKU resource fails until you create and associate a [network security group](../../virtual-network/network-security-groups-overview.md#network-security-groups) and explicitly allow the desired inbound traffic.
72-
73-
### Basic
74-
75-
Basic SKU addresses:
76-
77-
- For IPv4: Can be assigned using the dynamic or static allocation method. For IPv6: Can only be assigned using the dynamic allocation method.
78-
- Have an adjustable inbound originated flow idle timeout of 4-30 minutes, with a default of 4 minutes, and fixed outbound originated flow idle timeout of 4 minutes.
79-
- Are open by default. Network security groups are recommended but optional for restricting inbound or outbound traffic.
80-
- Don't support Availability Zone scenarios. Use standard SKU public IP for Availability Zone scenarios in applicable regions. To learn more about availability zones, see [Availability zones overview](../../availability-zones/az-overview.md?toc=%2fazure%2fvirtual-network%2ftoc.json) and [Standard Load Balancer and Availability Zones](../../load-balancer/load-balancer-standard-availability-zones.md?toc=%2fazure%2fvirtual-network%2ftoc.json).
81-
- Don't support [routing preference](routing-preference-overview.md) or [cross-region load balancers](../../load-balancer/cross-region-overview.md) functionality.
8262

8363
> [!NOTE]
8464
> Basic SKU IPv4 addresses can be upgraded after creation to Standard SKU. To learn about SKU upgrade, refer to [Public IP upgrade](public-ip-upgrade-portal.md).
8565
8666
>[!IMPORTANT]
87-
> 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. Please review [Standard Load Balancer](../../load-balancer/load-balancer-overview.md?toc=%2fazure%2fvirtual-network%2ftoc.json) for details.
67+
> 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. Please review [Standard Load Balancer](../../load-balancer/load-balancer-overview.md?toc=%2fazure%2fvirtual-network%2ftoc.json) for details.
8868
8969
## IP address assignment
9070

@@ -158,4 +138,4 @@ For more information on IPv6 in Azure, see [here](ipv6-overview.md).
158138

159139
## Next steps
160140
* Learn about [Private IP Addresses in Azure](private-ip-addresses.md)
161-
* [Deploy a VM with a static public IP using the Azure portal](./virtual-network-deploy-static-pip-arm-portal.md)
141+
* [Deploy a VM with a static public IP using the Azure portal](./virtual-network-deploy-static-pip-arm-portal.md)

0 commit comments

Comments
 (0)