Merge pull request #109602 from KumudD/ipv6ga-part3

IPv6 GA - part4

Author: ShannonLeavitt

articles/virtual-network/ipv6-public-ip-address-prefix.md

@@ -10,23 +10,22 @@ ms.devlang: na
 ms.topic: article
 ms.tgt_pltfrm: na
 ms.workload: infrastructure-services
-ms.date: 10/15/2019
+ms.date: 03/31/2020
 ms.author: kumud
 ---
 
-# Reserved public IPv6 address prefix (Preview)
+# Reserved public IPv6 address prefix
 
 In Azure, dual stack (IPv4+IPv6) virtual networks (VNet) and virtual machines (VMs) are secure by default since they have no Internet connectivity. You can easily add an IPv6 Internet connectivity to your Azure Load Balancers and VMs with public IPv6 addresses that you obtain from Azure.
 
-Any public IPs that you reserve are associated with an Azure region of your choice and with your Azure subscription. You may move a reserved (static) IPv6 public IP between any of the Azure Load Balancers or VMs in your subscription. You may dissociate the IPv6 public IP entirely and it will be held for your use when you’re ready.
+Any public IPs that you reserve are associated with an Azure region of your choice and with your Azure subscription. You may move a reserved (static) IPv6 public IP between any of the Azure Load Balancers or VMs in your subscription. You may dissociate the IPv6 public IP entirely and it will be held for your use when you're ready.
 
 > [!WARNING]
 > Use caution to not delete your public IP addresses accidentally. Deleting a public IP removes it from your subscription and you will not be able to recover it (not even with the help of Azure support).
 
 In addition to reserving individual IPv6 addresses, you can reserve contiguous ranges of Azure IPv6 addresses (known as IP prefix) for your use.  Similar to individual IP addresses, reserved prefixes are associated with an Azure region of your choice and with your Azure subscription. Reserving a predictable, contiguous range of addresses has many uses. For example, you can greatly simplify IP *whitelisting* of your Azure-hosted applications by your company and your customers as your static IP ranges can be readily programmed into on-premises firewalls.  You can create individual public IPs from your IP prefix as needed and when you delete those individual Public IPs they are *returned* to your reserved range so that you can reuse them later. All the IP addresses in your IP Prefix are reserved for your exclusive use until such time as you delete your Prefix.
 
-> [!Important]
-> IPv6 for Azure Virtual Network is currently in public preview. This preview is provided without a service level agreement and is not recommended for production workloads. Certain features may not be supported or may have constrained capabilities. See the [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) for details.
+
 
 ## IPv6 prefix sizes
 The following public IP prefix sizes are available:
@@ -41,7 +40,7 @@ Prefix size is specified as a Classless Inter-Domain Routing (CIDR) mask size. F
 For costs associated with using Azure Public IPs, both individual IP addresses and IP ranges, see [Public IP Address pricing](https://azure.microsoft.com/pricing/details/ip-addresses/).
 
 ## Limitations
-IPv6 is supported on Basic Public IPs only with “dynamic” allocation that means that the IPv6 address will change if you delete and redeploy your application (VM’s or load balancers) in Azure. Standard IPv6 Public IP’s support solely static (reserved) allocation though Standard INTERNAL load balancers can also support dynamic allocation from within the subnet to which they are assigned.  
+IPv6 is supported on Basic Public IPs only with "dynamic" allocation that means that the IPv6 address will change if you delete and redeploy your application (VM's or load balancers) in Azure. Standard IPv6 Public IP's support solely static (reserved) allocation though Standard INTERNAL load balancers can also support dynamic allocation from within the subnet to which they are assigned.  
 
 As a best practice, we recommend that you use Standard Public IPs and Standard Load Balancers for your IPv6 applications.
 

articles/virtual-network/ipv6-reserve-public-ip-address-prefix.md

@@ -10,15 +10,13 @@ ms.devlang: na
 ms.topic: article
 ms.tgt_pltfrm: na
 ms.workload: infrastructure-services
-ms.date: 10/15/2019
+ms.date: 03/31/2020
 ms.author: kumud
 ---
 
 # Reserve public IPv6 address prefix
 IPv6 for Azure Virtual Network (VNet) enables you to host applications in Azure with IPv6 and IPv4 connectivity both within a virtual network and to and from the Internet. In addition to reserving individual IPv6 addresses, you can reserve contiguous ranges of Azure IPv6 addresses (known as IP Prefix) for your use. This articles describes how to create IPv6 public IP addresses and address ranges using Azure PowerShell and CLI.
 
-> [!Important]
-> IPv6 for Azure Virtual Network is currently in public preview. This preview is provided without a service level agreement and is not recommended for production workloads. Certain features may not be supported or may have constrained capabilities. See the [Supplemental Terms of Use for Microsoft Azure Previews](https://azure.microsoft.com/support/legal/preview-supplemental-terms/) for details.
 
 ## Create a single reserved IPv6 public IP