Skip to content

Commit cad409a

Browse files
authored
Merge pull request #109601 from KumudD/ipv6ga-part2
IPv6 GA part 3
2 parents 65a0aba + 20e6edf commit cad409a

File tree

2 files changed

+2
-30
lines changed

2 files changed

+2
-30
lines changed

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

Lines changed: 2 additions & 29 deletions
Original file line numberDiff line numberDiff line change
@@ -11,46 +11,21 @@ ms.devlang: na
1111
ms.topic: article
1212
ms.tgt_pltfrm: na
1313
ms.workload: infrastructure-services
14-
ms.date: 10/23/2019
14+
ms.date: 04/01/2020
1515
ms.author: kumud
1616
---
1717

18-
# Add IPv6 to an IPv4 application in Azure virtual network - Azure CLI (Preview)
18+
# Add IPv6 to an IPv4 application in Azure virtual network - Azure CLI
1919

2020
This article shows you how to add IPv6 addresses to an application that is using IPv4 public IP address in an Azure virtual network for a Standard Load Balancer using Azure CLI. The in-place upgrade includes a virtual network and subnet, a Standard Load Balancer with IPv4 + IPV6 frontend configurations, VMs with NICs that have a IPv4 + IPv6 configurations, network security group, and public IPs.
2121

22-
> [!Important]
23-
> 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.
2422

2523
[!INCLUDE [cloud-shell-try-it.md](../../includes/cloud-shell-try-it.md)]
2624

2725
If you decide to install and use Azure CLI locally instead, this quickstart requires you to use Azure CLI version 2.0.28 or later. To find your installed version, run `az --version`. See [Install Azure CLI](/cli/azure/install-azure-cli) for install or upgrade info.
2826

2927
## Prerequisites
3028

31-
### Register the service
32-
33-
Before you deploy a dual stack application in Azure, you must configure your subscription for this preview feature using the following Azure CLI:
34-
35-
```azurecli
36-
az feature register --name AllowIPv6VirtualNetwork --namespace Microsoft.Network
37-
az feature register --name AllowIPv6CAOnStandardLB --namespace Microsoft.Network
38-
```
39-
40-
It takes up to 30 minutes for feature registration to complete. You can check your registration status by running the following Azure CLI command:
41-
42-
```azurecli
43-
az feature show --name AllowIPv6VirtualNetwork --namespace Microsoft.Network
44-
az feature show --name AllowIPv6CAOnStandardLB --namespace Microsoft.Network
45-
```
46-
47-
After the registration is complete, run the following command:
48-
49-
```azurecli
50-
az provider register --namespace Microsoft.Network
51-
```
52-
53-
### Create a Standard Load Balancer
5429
This article assumes that you deployed a Standard Load Balancer as described in [Quickstart: Create a Standard Load Balancer - Azure CLI](../load-balancer/quickstart-load-balancer-standard-public-cli.md).
5530

5631
## Create IPv6 addresses
@@ -168,8 +143,6 @@ You can view the IPv6 dual stack virtual network in Azure portal as follows:
168143

169144
![IPv6 dual stack virtual network in Azure](./media/ipv6-add-to-existing-vnet-powershell/ipv6-dual-stack-vnet.png)
170145

171-
> [!NOTE]
172-
> The IPv6 for Azure virtual network is available in the Azure portal in read-only for this preview release.
173146

174147
## Clean up resources
175148

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

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -362,7 +362,6 @@ You can view the IPv6 dual stack virtual network in Azure portal as follows:
362362

363363

364364

365-
366365
## Clean up resources
367366

368367
When no longer needed, you can use the [az group delete](/cli/azure/group#az-group-delete) command to remove the resource group, VM, and all related resources.

0 commit comments

Comments
 (0)