updated

Author: KumudD

articles/virtual-network/ipv6-add-to-existing-vnet-powershell.md

@@ -11,49 +11,26 @@ ms.devlang: na
 ms.topic: article
 ms.tgt_pltfrm: na
 ms.workload: infrastructure-services
-ms.date: 10/21/2019
+ms.date: 04/01/2020
 ms.author: kumud
 ---
 
-# Upgrade an IPv4 application to IPv6 in Azure virtual network - PowerShell (Preview)
+# Upgrade an IPv4 application to IPv6 in Azure virtual network - PowerShell
 
 This article shows you how to add IPv6 connectivity to an existing IPv4 application in an Azure virtual network with a Standard Load Balancer and Public IP. The in-place upgrade includes:
 - IPv6 address space for the virtual network and subnet
 - a Standard Load Balancer with both IPv4 and IPV6 frontend configurations
 - VMs with NICs that have both an IPv4 + IPv6 configuration
 - IPv6 Public IP so the load balancer has Internet-facing IPv6 connectivity
 
-> [!Important]
-> IPv6 support 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.
+
 
 [!INCLUDE [cloud-shell-try-it.md](../../includes/cloud-shell-try-it.md)]
 
 If you choose to install and use PowerShell locally, this article requires the Azure PowerShell module version 6.9.0 or later. Run `Get-Module -ListAvailable Az` to find the installed version. If you need to upgrade, see [Install Azure PowerShell module](/powershell/azure/install-Az-ps). If you are running PowerShell locally, you also need to run `Connect-AzAccount` to create a connection with Azure.
 
 ## Prerequisites
 
-### Register the service
-
-Before you deploy a dual stack application in Azure, you must configure your subscription for this preview feature using the following Azure PowerShell:
-
-Register as follows:
-```azurepowershell
-Register-AzProviderFeature -FeatureName AllowIPv6VirtualNetwork -ProviderNamespace Microsoft.Network
-Register-AzProviderFeature -FeatureName AllowIPv6CAOnStandardLB -ProviderNamespace Microsoft.Network
-```
-It takes up to 30 minutes for feature registration to complete. You can check your registration status by running the following Azure PowerShell command:
-Check on the registration as follows:
-```azurepowershell
-Get-AzProviderFeature -FeatureName AllowIPv6VirtualNetwork -ProviderNamespace Microsoft.Network
-Get-AzProviderFeature -FeatureName AllowIPv6CAOnStandardLB -ProviderNamespace Microsoft.Network
-```
-After the registration is complete, run the following command:
-
-```azurepowershell
-Register-AzResourceProvider -ProviderNamespace Microsoft.Network
-```
-
-### Create a Standard Load Balancer
 This article assumes that you deployed a Standard Load Balancer as described in [Quickstart: Create a Standard Load Balancer - Azure PowerShell](../load-balancer/quickstart-create-standard-load-balancer-powershell.md).
 
 ## Retrieve the resource group
@@ -172,8 +149,7 @@ You can view the IPv6 dual stack virtual network in Azure portal as follows:
 
   ![IPv6 dual stack virtual network in Azure](./media/ipv6-add-to-existing-vnet-powershell/ipv6-dual-stack-vnet.png)
 
-> [!NOTE]
-> The IPv6 for Azure virtual network is available in the Azure portal in read-only for this preview release.
+
 
 ## Clean up resources
 

articles/virtual-network/ipv6-configure-standard-load-balancer-template-json.md

@@ -1,5 +1,5 @@
 ---
-title: Deploy an IPv6 dual stack application in Azure virtual network - Resource Manger template (preview)
+title: Deploy an IPv6 dual stack application in Azure virtual network - Resource Manger template
 titlesuffix: Azure Virtual Network
 description: This article shows how to deploy an IPv6 dual stack application with Standard Load Balancer in Azure virtual network using Azure Resource Manager VM templates.
 services: virtual-network
@@ -10,11 +10,11 @@ ms.service: virtual-network
 ms.devlang: NA
 ms.topic: article
 ms.workload: infrastructure-services
-ms.date: 07/15/2019
+ms.date: 04/01/2020
 ms.author: kumud
 ---
 
-# Deploy an IPv6 dual stack application in Azure virtual network - Template (Preview)
+# Deploy an IPv6 dual stack application in Azure virtual network - Template
 
 This article provides a list of IPv6 configuration tasks with the portion of the Azure Resource Manager VM template that applies to. Use the template described in this article to deploy a dual stack (IPv4 + IPv6) application using Standard Load Balancer in Azure that includes a dual stack virtual network with IPv4 and IPv6 subnets, a Standard Load Balancer with dual (IPv4 + IPv6) front-end configurations, VMs with NICs that have a dual IP configuration, network security group, and public IPs. 
 
@@ -53,7 +53,7 @@ Template section to add:
             "name": "ipconfig-v6",
             "properties": {
               "privateIPAllocationMethod": "Dynamic",
-	      "privateIPAddressVersion":"IPv6",
+          "privateIPAddressVersion":"IPv6",
               "subnet": {
                 "id": "[variables('v6-subnet-id')]"
               },
@@ -118,7 +118,7 @@ If you're using a network virtual appliance, add IPv6 routes in the Route Table.
 ### IPv6 Public IP addresses
 
 ```JSON
-	{
+    {
       "apiVersion": "[variables('ApiVersion')]",
       "type": "Microsoft.Network/publicIPAddresses",
       "name": "lbpublicip-v6",
@@ -128,14 +128,14 @@ If you're using a network virtual appliance, add IPv6 routes in the Route Table.
       },
       "properties": {
         "publicIPAllocationMethod": "Static",
-		"publicIPAddressVersion": "IPv6"
+        "publicIPAddressVersion": "IPv6"
       }
 ```
 
 ### IPv6 Front end for Load Balancer
 
 ```JSON
-		  {
+          {
             "name": "LBFE-v6",
             "properties": {
               "publicIPAddress": {
@@ -163,7 +163,7 @@ If you're using a network virtual appliance, add IPv6 routes in the Route Table.
             "name": "ipconfig-v6",
             "properties": {
               "privateIPAllocationMethod": "Dynamic",
-	      "privateIPAddressVersion":"IPv6",
+          "privateIPAddressVersion":"IPv6",
               "subnet": {
                 "id": "[variables('v6-subnet-id')]"
               },

articles/virtual-network/ipv6-configure-template-json.md

@@ -1,5 +1,5 @@
 ---
-title: Deploy an IPv6 dual stack application with Basic Load Balancer in Azure virtual network - Resource Manger template (preview)
+title: Deploy an IPv6 dual stack application with Basic Load Balancer in Azure virtual network - Resource Manger template
 titlesuffix: Azure Virtual Network
 description: This article shows how to deploy an IPv6 dual stack application in Azure virtual network using Azure Resource Manager VM templates.
 services: virtual-network
@@ -10,11 +10,11 @@ ms.service: virtual-network
 ms.devlang: NA
 ms.topic: article
 ms.workload: infrastructure-services
-ms.date: 06/26/2019
+ms.date: 04/01/2020
 ms.author: kumud
 ---
 
-# Deploy an IPv6 dual stack application with Basic Load Balancer in Azure - Template (Preview)
+# Deploy an IPv6 dual stack application with Basic Load Balancer in Azure - Template
 
 This article provides a list of IPv6 configuration tasks with the portion of the Azure Resource Manager VM template that applies to. Use the template described in this article to deploy a dual stack (IPv4 + IPv6) application with Basic Load Balancer that includes a dual stack virtual network with IPv4 and IPv6 subnets, a Basic Load Balancer with dual (IPv4 + IPv6) front-end configurations, VMs with NICs that have a dual IP configuration, network security group, and public IPs.
 
@@ -55,7 +55,7 @@ Template section to add:
             "name": "ipconfig-v6",
             "properties": {
               "privateIPAllocationMethod": "Dynamic",
-	      "privateIPAddressVersion":"IPv6",
+          "privateIPAddressVersion":"IPv6",
               "subnet": {
                 "id": "[variables('v6-subnet-id')]"
               },
@@ -120,21 +120,21 @@ If you're using a network virtual appliance, add IPv6 routes in the Route Table.
 ### IPv6 Public IP addresses
 
 ```JSON
-	{
+    {
       "apiVersion": "[variables('ApiVersion')]",
       "type": "Microsoft.Network/publicIPAddresses",
       "name": "lbpublicip-v6",
       "location": "[resourceGroup().location]",
       "properties": {
         "publicIPAllocationMethod": "Dynamic",
-		"publicIPAddressVersion": "IPv6"
+        "publicIPAddressVersion": "IPv6"
       }
 ```
 
 ### IPv6 Front end for Load Balancer
 
 ```JSON
-		  {
+          {
             "name": "LBFE-v6",
             "properties": {
               "publicIPAddress": {
@@ -162,7 +162,7 @@ If you're using a network virtual appliance, add IPv6 routes in the Route Table.
             "name": "ipconfig-v6",
             "properties": {
               "privateIPAllocationMethod": "Dynamic",
-	      "privateIPAddressVersion":"IPv6",
+          "privateIPAddressVersion":"IPv6",
               "subnet": {
                 "id": "[variables('v6-subnet-id')]"
               },

articles/virtual-network/ipv6-overview.md

@@ -1,5 +1,5 @@
 ---
-title: Overview of IPv6 for Azure Virtual Network (Preview)
+title: Overview of IPv6 for Azure Virtual Network
 titlesuffix: Azure Virtual Network
 description: IPv6 description of IPv6 endpoints and data paths in an Azure virtual network.
 services: virtual-network
@@ -10,19 +10,17 @@ ms.service: virtual-network
 ms.devlang: NA
 ms.topic: article
 ms.workload: infrastructure-services
-ms.date: 12/19/2019
+ms.date: 04/01/2020
 ms.author: kumud
 ---
 
-# What is IPv6 for Azure Virtual Network? (Preview)
+# What is IPv6 for Azure Virtual Network?
 
 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. Due to the exhaustion of public IPv4 addresses, new networks for mobility and Internet of Things (IoT) are often built on IPv6. Even long established ISP and mobile networks are being transformed to IPv6. IPv4-only services can find themselves at a real disadvantage in both existing and emerging markets. Dual stack IPv4/IPv6 connectivity enables Azure-hosted services to traverse this technology gap with globally available, dual-stacked services that readily connect with both the existing IPv4 and these new IPv6 devices and networks.
 
 Azure's original IPv6 connectivity makes it easy to provide dual stack (IPv4/IPv6) Internet connectivity for applications hosted in Azure. It allows for simple deployment of VMs with load balanced IPv6 connectivity for both inbound and outbound initiated connections. This feature is still available and more information is available [here](../load-balancer/load-balancer-ipv6-overview.md).
 IPv6 for Azure virtual network is much more full featured- enabling full IPv6 solution architectures to be deployed in Azure.
 
-> [!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.
 
 The following diagram depicts a simple dual stack (IPv4/IPv6) deployment in Azure:
 
@@ -69,8 +67,8 @@ IPv6 for Azure VNET is a foundational feature set which enables customers to hos
 
 ## Limitations
 The current IPv6 for Azure virtual network release has the following limitations:
-- IPv6 for Azure virtual network (Preview) is available in all global Azure regions, but only in Global Azure- not yet in government clouds.
-- ExpressRoute and VPN gateways cannot be used in a VNET with IPv6 enabled, either directly or peered with “UseRemoteGateway”. 
+- IPv6 for Azure virtual network is available in all global Azure regions, but only in Global Azure- not yet in government clouds.
+- ExpressRoute and VPN gateways cannot be used in a VNET with IPv6 enabled, either directly or peered with "UseRemoteGateway". 
 - The Azure platform (AKS, etc.) does not support IPv6 communication for Containers.  
 
 ## Pricing

articles/virtual-network/ipv6-virtual-machine-scale-set.md

@@ -15,14 +15,14 @@ ms.date: 10/29/2019
 ms.author: kumud
 ---
 
-# Deploy virtual machine scale sets with IPv6 in Azure (Preview)
+# Deploy virtual machine scale sets with IPv6 in Azure
 
-This article shows you how to deploy a dual stack (IPv4 + IPv6) Virtual Machine Scale Set with a dual stack external load balancer in an Azure virtual network. The process to create an IPv6-capable virtual machine scale set is nearly identical to the process for creating individual VMs described [here](ipv6-configure-standard-load-balancer-template-json.md). You’ll start with the steps that are similar to ones described for individual VMs:
-1.	Create IPv4 and IPv6 Public IPs.
-2.	Create a dual stack load balancer.  
-3.	Create network security group (NSG) rules.  
+This article shows you how to deploy a dual stack (IPv4 + IPv6) Virtual Machine Scale Set with a dual stack external load balancer in an Azure virtual network. The process to create an IPv6-capable virtual machine scale set is nearly identical to the process for creating individual VMs described [here](ipv6-configure-standard-load-balancer-template-json.md). You'll start with the steps that are similar to ones described for individual VMs:
+1.    Create IPv4 and IPv6 Public IPs.
+2.    Create a dual stack load balancer.  
+3.    Create network security group (NSG) rules.  
 
-The only step that is different from individual VMs is creating the network interface (NIC) configuration that uses the virtual machine scale set resource:  networkProfile/networkInterfaceConfigurations. The JSON structure is similar to that of the Microsoft.Network/networkInterfaces object used for individual VMs with the addition of setting the NIC and the IPv4 IpConfiguration as the primary interface using the **“primary”: true**  attribute as seen in the following example:
+The only step that is different from individual VMs is creating the network interface (NIC) configuration that uses the virtual machine scale set resource:  networkProfile/networkInterfaceConfigurations. The JSON structure is similar to that of the Microsoft.Network/networkInterfaces object used for individual VMs with the addition of setting the NIC and the IPv4 IpConfiguration as the primary interface using the **"primary": true**  attribute as seen in the following example:
 
 ```json
           "networkProfile": {
@@ -31,9 +31,9 @@ The only step that is different from individual VMs is creating the network inte
                 "name": "[variables('nicName')]",
                 "properties": {
                   "primary": true,
-		  "networkSecurityGroup": {
-		    "id": "[resourceId('Microsoft.Network/networkSecurityGroups','VmssNsg')]"
-		  },                  
+          "networkSecurityGroup": {
+            "id": "[resourceId('Microsoft.Network/networkSecurityGroups','VmssNsg')]"
+          },                  
                   "ipConfigurations": [
                     {
                       "name": "[variables('ipConfigName')]",

articles/virtual-network/virtual-network-ipv4-ipv6-dual-stack-cli.md

@@ -21,15 +21,21 @@ This article shows you how to deploy a dual stack (IPv4 + IPv6) application with
 
 To deploy a dual stack (IPV4 + IPv6) application using Standard Load Balancer, see [Deploy an IPv6 dual stack application with Standard Load Balancer using Azure CLI](virtual-network-ipv4-ipv6-dual-stack-standard-load-balancer-cli.md).
 
+<<<<<<< HEAD
 
+=======
+>>>>>>> 65a0ababa1a16cf76af39f63094bcd9011d714d7
 
 If you don't have an Azure subscription, create a [free account](https://azure.microsoft.com/free/?WT.mc_id=A261C142F) now.
 
 [!INCLUDE [cloud-shell-try-it.md](../../includes/cloud-shell-try-it.md)]
 
 If you decide to install and use Azure CLI locally instead, this quickstart requires you to use Azure CLI version 2.0.49 or later. To find your installed version, run `az --version`. See [Install Azure CLI](/cli/azure/install-azure-cli) for install or upgrade info.
 
+<<<<<<< HEAD
 
+=======
+>>>>>>> 65a0ababa1a16cf76af39f63094bcd9011d714d7
 ## Create a resource group
 
 Before you can create your dual-stack virtual network, you must create a resource group with [az group create](/cli/azure/group). The following example creates a resource group named *DsResourceGroup01* in the *eastus* location:
@@ -362,6 +368,10 @@ You can view the IPv6 dual stack virtual network in Azure portal as follows:
 
   ![IPv6 dual stack virtual network in Azure](./media/virtual-network-ipv4-ipv6-dual-stack-powershell/dual-stack-vnet.png)
 
+<<<<<<< HEAD
+=======
+
+>>>>>>> 65a0ababa1a16cf76af39f63094bcd9011d714d7
 
 
 ## Clean up resources

articles/virtual-network/virtual-network-ipv4-ipv6-dual-stack-powershell.md

@@ -11,43 +11,21 @@ ms.devlang: na
 ms.topic: article
 ms.tgt_pltfrm: na
 ms.workload: infrastructure-services
-ms.date: 12/17/2019
+ms.date: 04/01/2020
 ms.author: kumud
 ---
 
-# Deploy an IPv6 dual stack application using Basic Load Balancer - PowerShell (Preview)
+# Deploy an IPv6 dual stack application using Basic Load Balancer - PowerShell
 
 This article shows you how to deploy a dual stack (IPv4 + IPv6) application with Basic Load Balancer using Azure PowerShell that includes a dual stack virtual network and subnet, a Basic Load Balancer with dual (IPv4 + IPv6) front-end configurations, VMs with NICs that have a dual IP configuration, network security group, and public IPs.
 
 To deploy a dual stack (IPV4 + IPv6) application using Standard Load Balancer, see [Deploy an IPv6 dual stack application with Standard Load Balancer using Azure PowerShell](virtual-network-ipv4-ipv6-dual-stack-standard-load-balancer-powershell.md).
 
-> [!Important]
-> IPv6 support 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.
 
 [!INCLUDE [cloud-shell-try-it.md](../../includes/cloud-shell-try-it.md)]
 
 If you choose to install and use PowerShell locally, this article requires the Azure PowerShell module version 6.9.0 or later. Run `Get-Module -ListAvailable Az` to find the installed version. If you need to upgrade, see [Install Azure PowerShell module](/powershell/azure/install-Az-ps). If you are running PowerShell locally, you also need to run `Connect-AzAccount` to create a connection with Azure.
 
-## Prerequisites
-Before you deploy a dual stack application in Azure, you must configure your subscription for this preview feature using the following Azure PowerShell:
-
-Register as follows:
-
-```azurepowershell
-Register-AzProviderFeature -FeatureName AllowIPv6VirtualNetwork -ProviderNamespace Microsoft.Network
-Register-AzProviderFeature -FeatureName AllowIPv6CAOnStandardLB -ProviderNamespace Microsoft.Network
-```
-It takes up to 30 minutes for feature registration to complete. You can check your registration status by running the following Azure PowerShell command:
-Check on the registration as follows:
-```azurepowershell
-Get-AzProviderFeature -FeatureName AllowIPv6VirtualNetwork -ProviderNamespace Microsoft.Network
-Get-AzProviderFeature -FeatureName AllowIPv6CAOnStandardLB -ProviderNamespace Microsoft.Network
-```
-After the registration is complete, run the following command:
-
-```azurepowershell
-Register-AzResourceProvider -ProviderNamespace Microsoft.Network
-```
 
 ## Create a resource group
 
@@ -268,7 +246,7 @@ Create virtual NICs with [New-AzNetworkInterface](/powershell/module/az.network/
     -PrivateIpAddressVersion IPv4 `
     -LoadBalancerBackendAddressPool $backendPoolv4 `
     -PublicIpAddress  $RdpPublicIP_1
-  	
+      
   $Ip6Config=New-AzNetworkInterfaceIpConfig `
     -Name dsIp6Config `
     -Subnet $vnet.subnets[0] `
@@ -369,8 +347,6 @@ You can view the IPv6 dual stack virtual network in Azure portal as follows:
 
   ![IPv6 dual stack virtual network in Azure](./media/virtual-network-ipv4-ipv6-dual-stack-powershell/dual-stack-vnet.png)
 
-> [!NOTE]
-> The IPv6 for Azure virtual network is available in the Azure portal in read-only for this preview release.
 
 ## Clean up resources