Merge pull request #218611 from asudbring/ip-manage-freshness

v-MarkAllen · web-flow · commit 5ac48092c2eb · 2022-11-16T14:03:41.000-05:00
IP manage article freshness update
diff --git a/articles/virtual-network/ip-services/virtual-network-public-ip-address.md b/articles/virtual-network/ip-services/virtual-network-public-ip-address.md
@@ -7,51 +7,56 @@ author: asudbring
 ms.service: virtual-network
 ms.subservice: ip-services
 ms.topic: conceptual
-ms.tgt_pltfrm: na
-ms.workload: infrastructure-services
-ms.date: 05/20/2021
+ms.date: 11/16/2022
 ms.author: allensu
+ms.custom: FY23 content-maintenance
 ---
 
 # Create, change, or delete an Azure public IP address
 
-Learn about a public IP address and how to create, change, and delete one. A public IP address is a resource with configurable settings. Assigning a public IP address to an Azure resource that supports public IP addresses enables:
+Learn about a public IP address and how to create, change, and delete one. A public IP address is a resource with configurable settings. 
+
+When you assign a public IP address to an Azure resource, you enable the following operations:
 
 - Inbound communication from the Internet to the resource, such as Azure Virtual Machines (VM), Azure Application Gateways, Azure Load Balancers, Azure VPN Gateways, and others.
+
 - Outbound connectivity to the Internet using a predictable IP address.
 
 [!INCLUDE [ephemeral-ip-note.md](../../../includes/ephemeral-ip-note.md)]
 
 ## Create a public IP address
 
-For instructions on how to create public IP addresses using the Portal, PowerShell, CLI, or Resource Manager templates, refer to the following pages:
+For instructions on how to create public IP addresses using the Azure portal, PowerShell, CLI, or Resource Manager templates, refer to the following pages:
 
- * [Create public IP addresses - Portal](./create-public-ip-portal.md?tabs=option-create-public-ip-standard-zones)
- * [Create public IP addresses - PowerShell](./create-public-ip-powershell.md?tabs=option-create-public-ip-standard-zones)
- * [Create public IP addresses - Azure CLI](./create-public-ip-cli.md?tabs=option-create-public-ip-standard-zones)
- * [Create public IP addresses - Template](./create-public-ip-template.md)
+* [Create a public IP address - Azure portal](./create-public-ip-portal.md?tabs=option-create-public-ip-standard-zones)
+ 
+* [Create a public IP address - PowerShell](./create-public-ip-powershell.md?tabs=option-create-public-ip-standard-zones)
+ 
+* [Create a public IP address - Azure CLI](./create-public-ip-cli.md?tabs=option-create-public-ip-standard-zones)
+ 
+* [Create a public IP address - Template](./create-public-ip-template.md)
 
 >[!NOTE]
->Though the portal provides the option to create two public IP address resources (one IPv4 and one IPv6), the PowerShell and CLI commands create one resource with an address for one IP version or the other. If you want two public IP address resources, one for each IP version, you must run the command twice, specifying different names and IP versions for the public IP address resources.
+>The portal provides the option to create an IPv4 and IPv6 address concurrently during resource deployment. The PowerShell and Azure CLI commands create one resource, either IPv4 or IPv6. If you want an IPv4 and a IPv6 address, execute the PowerShell or CLI command twice. Specify different names and IP versions for the public IP address resources.
 
 For more detail on the specific attributes of a public IP address during creation, see the following table:
 
    |Setting|Required?|Details|
    |---|---|---|
-   |IP Version|Yes| Select IPv4 or IPv6 or Both. Selecting Both will result in 2 Public IP addresses being create- 1 IPv4 address and 1 IPv6 address. Learn more about [IPv6 in Azure VNETs](ipv6-overview.md?toc=%2fazure%2fvirtual-network%2ftoc.json).|
-   |SKU|Yes|All public IP addresses created before the introduction of SKUs are **Basic** SKU public IP addresses. You cannot change the SKU after the public IP address is created. A standalone virtual machine, virtual machines within an availability set, or virtual machine scale sets can use Basic or Standard SKUs. Mixing SKUs between virtual machines within availability sets or scale sets or standalone VMs is not allowed. **Basic** SKU: If you are creating a public IP address in a region that supports availability zones, the **Availability zone** setting is set to *None* by default. Basic Public IPs do not support Availability zones. **Standard** SKU: A Standard SKU public IP can be associated to a virtual machine or a load balancer front end. If you're creating a public IP address in a region that supports availability zones, the **Availability zone** setting is set to *Zone-redundant* by default. For more information about availability zones, see the **Availability zone** setting. The standard SKU is required if you associate the address to a Standard load balancer. To learn more about standard load balancers, see [Azure load balancer standard SKU](../../load-balancer/load-balancer-overview.md?toc=%2fazure%2fvirtual-network%2ftoc.json). When you assign a standard SKU public IP address to a virtual machine's network interface, you must explicitly allow the intended traffic with a [network security group](../../virtual-network/network-security-groups-overview.md#network-security-groups). Communication with the resource fails until you create and associate a network security group and explicitly allow the desired traffic.|
-   |Tier|Yes|Indicates if the IP address is associated with a region (**Regional**) or is "anycast" from multiple regions (**Global**). *Note that a "Global Tier" IP is preview functionality for Standard IPs, and currently only utilized for the Cross-Region Load Balancer*.|
+   |IP Version|Yes| Select **IPv4** or **IPv6** or **Both**. Selection of **Both** results in two public IP addresses created, one IPv4 and one IPv6. For more information, [Overview of IPv6 for Azure Virtual Network](ipv6-overview.md?toc=%2fazure%2fvirtual-network%2ftoc.json).|
+   |SKU|Yes|All public IP addresses created before the introduction of SKUs are **Basic** SKU public IP addresses. You can't change the SKU after the public IP address is created. </br></br>A standalone virtual machine, virtual machines within an availability set, or Virtual Machine Scale Sets can use Basic or Standard SKUs. Mixing SKUs between virtual machines within availability sets or scale sets or standalone VMs isn't allowed.</br></br> **Basic**: Basic public IP addresses don't support Availability zones. The **Availability zone** setting is set to **None** by default if the public IP address is created in a region that supports availability zones. </br></br> **Standard**: Standard public IP addresses can be associated to Azure resources that support public IPs, such as virtual machines, load balancers, and Azure Firewall. The **Availability zone** setting is set to **Zone-redundant** by default if the IP address is created in a region that supports availability zones. For more information about availability zones, see the **Availability zone** setting. </br></br>The standard SKU is required if you associate the address to a standard load balancer. For more information about standard load balancers, see [Azure load balancer standard SKU](../../load-balancer/load-balancer-overview.md?toc=%2fazure%2fvirtual-network%2ftoc.json). </br></br> When you assign a standard SKU public IP address to a virtual machine's network interface, you must explicitly allow the intended traffic with a [network security group](../../virtual-network/network-security-groups-overview.md#network-security-groups). Communication with the resource fails until you create and associate a network security group and explicitly allow the desired traffic.|
+   |Tier|Yes|Indicates if the IP address is associated with a region **(Regional)** or is *"anycast"* from multiple regions **(Global)**. </br></br> *A **Global tier** IP is preview functionality for Standard SKU IP addresses, and currently only utilized for the Cross-region Azure Load Balancer*.|
    |Name|Yes|The name must be unique within the resource group you select.|
-   |IP address assignment|Yes|**Dynamic:** Dynamic addresses are assigned after a public IP address is associated to an Azure resource and is started for the first time. Dynamic addresses can change if a resource such as a virtual machine is stopped (deallocated) and then restarted through Azure. The address remains the same if a virtual machine is rebooted or stopped from within the guest OS. When a public IP address resource is removed from a resource, the dynamic address is released.<br> **Static:** Static addresses are assigned when a public IP address is created. Static addresses aren't released until a public IP address resource is deleted. <br>Note: If you select *IPv6* for the **IP version**, the assignment method must be *Dynamic* for Basic SKU.  Standard SKU addresses are *Static* for both IPv4 and IPv6. |
-  |Routing preference |Yes| By default, the routing preference for public IP addresses is set to "Microsoft network", which delivers traffic over Microsoft's global wide area network to the user.  The selection of "Internet" minimizes travel on Microsoft's network, instead using the transit ISP network to deliver traffic at a cost-optimized rate.  A public IP addresses routing preference can’t be changed once created.  For more information on routing preference, see [What is routing preference (preview)?](routing-preference-overview.md).   |
-   |Idle timeout (minutes)|No|How many minutes to keep a TCP or HTTP connection open without relying on clients to send keep-alive messages. If you select IPv6 for **IP Version**, this value is set to 4 minutes and cannot be changed. |
-   |DNS name label|No|Must be unique within the Azure location you create the name in (across all subscriptions and all customers). Azure automatically registers the name and IP address in its DNS so you can connect to a resource with the name. Azure appends a default subnet such as *location.cloudapp.azure.com* to the name you provide to create the fully qualified DNS name. If you choose to create both address versions, the same DNS name is assigned to both the IPv4 and IPv6 addresses. Azure's default DNS contains both IPv4 A and IPv6 AAAA name records. The default DNS responds with both records during DNS lookup. The client chooses which address (IPv4 or IPv6) to communicate with. You can use the Azure DNS service to configure a DNS name with a custom suffix that resolves to the public IP address. For more information, see [Use Azure DNS with an Azure public IP address](../../dns/dns-custom-domain.md?toc=%2fazure%2fvirtual-network%2ftoc.json#public-ip-address).|
-   |Name (Only visible if you select IP Version of **Both**)|Yes, if you select IP Version of **Both**|The name must be different than the name you enter for the first **Name** in this list. If you choose to create both an IPv4 and an IPv6 address, the portal creates two separate public IP address resources, one with each IP address version assigned to it.|
+   |IP address assignment|Yes|**Dynamic:** Dynamic addresses are assigned after a public IP address is associated to an Azure resource and is started for the first time. Dynamic addresses can change if a resource such as a virtual machine is stopped (deallocated) and then restarted through Azure. The address remains the same if a virtual machine is rebooted or stopped from within the guest OS. When a public IP address resource is removed from a resource, the dynamic address is released.<br></br> **Static:** Static addresses are assigned when a public IP address is created. Static addresses aren't released until a public IP address resource is deleted. <br></br> *If you select **IPv6** for the **IP version**, the assignment method must be *Dynamic* for Basic SKU.  Standard SKU addresses are *Static* for both IPv4 and IPv6.* |
+  |Routing preference |Yes| By default, the routing preference for public IP addresses is set to **Microsoft network**. The **Microsoft network** setting delivers traffic over Microsoft's global wide area network to the user. </br></br> The selection of **Internet** minimizes travel on Microsoft's network. The **Internet** setting uses the transit ISP network to deliver traffic at a cost-optimized rate. A public IP addresses routing preference can’t be changed once created. For more information on routing preference, see [What is routing preference (preview)?](routing-preference-overview.md).   |
+   |Idle timeout (minutes)|No| The number of minutes to keep a TCP or HTTP connection open without relying on clients to send keep-alive messages. If you select IPv6 for **IP Version**, this value is set to 4 minutes, and can't be changed. |
+   |DNS name label|No|Must be unique within the Azure location you create the name in across all subscriptions and all customers. Azure automatically registers the name and IP address in its DNS so you can connect to a resource with the name. </br></br> Azure appends a default subnet such as **location.cloudapp.azure.com** to the name you provide to create the fully qualified DNS name. If you choose to create both address versions, the same DNS name is assigned to both the IPv4 and IPv6 addresses. Azure's default DNS contains both IPv4 A and IPv6 AAAA name records. </br></br> The default DNS responds with both records during DNS lookup. The client chooses which address (IPv4 or IPv6) to communicate with. You can use the Azure DNS service to configure a DNS name with a custom suffix that resolves to the public IP address. </br></br>For more information, see [Use Azure DNS with an Azure public IP address](../../dns/dns-custom-domain.md?toc=%2fazure%2fvirtual-network%2ftoc.json#public-ip-address).|
+   |Name (Only visible if you select IP Version of **Both**)|Yes, if you select IP Version of **Both**|The name must be different than the name you entered previously for **Name** in this list. If you create both an IPv4 and an IPv6 address, the portal creates two separate public IP address resources. The deployment creates one IPv4 address and one IPv6 address.|
    |IP address assignment (Only visible if you select IP Version of **Both**)|Yes, if you select IP Version of **Both**| Same restrictions as IP address assignment above. |
    |Subscription|Yes|Must exist in the same [subscription](../../azure-glossary-cloud-terminology.md?toc=%2fazure%2fvirtual-network%2ftoc.json#subscription) as the resource to which you'll associate the public IPs.|
    |Resource group|Yes|Can exist in the same, or different, [resource group](../../azure-glossary-cloud-terminology.md?toc=%2fazure%2fvirtual-network%2ftoc.json#resource-group) as the resource to which you'll associate the public IPs.|
-   |Location|Yes|Must exist in the same [location](https://azure.microsoft.com/regions), also referred to as region, as the resource to which you'll associate the Public IPs.|
-   |Availability zone| No | This setting only appears if you select a supported location and IP address type. **Basic** SKU public IPs and **Global** Tier public IPs don't support Availability Zones. You can select no-zone (default option), a specific zone, or zone-redundant. The choice will depend on your specific domain failure requirements. For a list of supported locations and more information about Availability Zones, see [Availability zones overview](../../availability-zones/az-overview.md?toc=%2fazure%2fvirtual-network%2ftoc.json).  
+   |Location|Yes|Must exist in the same [location](https://azure.microsoft.com/regions), also referred to as region, as the resource to which you'll associate the public IPs.|
+   |Availability zone| No | This setting only appears if you select a supported location and IP address type. **Basic** SKU public IPs and **Global** Tier public IPs don't support Availability Zones. You can select no-zone (default option), a specific zone, or zone-redundant. The choice will depend on your specific domain failure requirements.</br></br>For a list of supported locations and more information about Availability Zones, see [Availability zones overview](../../availability-zones/az-overview.md?toc=%2fazure%2fvirtual-network%2ftoc.json).  
 
 ## View, modify settings for, or delete a public IP address
 
@@ -77,9 +82,9 @@ For more detail on the specific attributes of a public IP address during creatio
 
 ## Virtual Machine Scale Sets
 
-When using a virtual machine scale set with Public IPs, there are not separate Public IP objects associated with the individual virtual machine instances. However, a Public IP Prefix object [can be used to generate the instance IPs](https://azure.microsoft.com/resources/templates/vmss-with-public-ip-prefix/).
+There aren't separate public IP objects associated with the individual virtual machine instances for a Virtual Machine Scale Set with public IPs. A public IP prefix object [can be used to generate the instance IPs](https://azure.microsoft.com/resources/templates/vmss-with-public-ip-prefix/).
 
-To list the Public IPs on a virtual machine scale set, you can use PowerShell ([Get-AzPublicIpAddress -VirtualMachineScaleSetName](/powershell/module/az.network/get-azpublicipaddress)) or CLI ([az virtual machine scale set list-instance-public-ips](/cli/azure/vmss#az-vmss-list-instance-public-ips)).
+To list the Public IPs on a Virtual Machine Scale Set, you can use PowerShell ([Get-AzPublicIpAddress -VirtualMachineScaleSetName](/powershell/module/az.network/get-azpublicipaddress)) or CLI ([az Virtual Machine Scale Set list-instance-public-ips](/cli/azure/vmss#az-vmss-list-instance-public-ips)).
 
 For more information, see [Networking for Azure Virtual Machine Scale Sets](../../virtual-machine-scale-sets/virtual-machine-scale-sets-networking.md#public-ipv4-per-virtual-machine).
 
