Merge pull request #109599 from KumudD/newipv6ga

IPv6 - GA

Author: PRMerger16

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-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')]",