You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/virtual-network/ipv6-add-to-existing-vnet-cli.md
+3-25Lines changed: 3 additions & 25 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,16 +11,14 @@ ms.devlang: na
11
11
ms.topic: article
12
12
ms.tgt_pltfrm: na
13
13
ms.workload: infrastructure-services
14
-
ms.date: 10/23/2019
14
+
ms.date: 03/13/2020
15
15
ms.author: kumud
16
16
---
17
17
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
19
19
20
20
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.
21
21
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.
@@ -30,25 +28,6 @@ If you decide to install and use Azure CLI locally instead, this quickstart requ
30
28
31
29
### Register the service
32
30
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
-
It takes up to 30 minutes for feature registration to complete. You can check your registration status by running the following Azure CLI command:
40
-
41
-
```azurelci
42
-
az feature show --name AllowIPv6VirtualNetwork --namespace Microsoft.Network
43
-
az feature show --name AllowIPv6CAOnStandardLB --namespace Microsoft.Network
44
-
```
45
-
After the registration is complete, run the following command:
46
-
47
-
```azurelci
48
-
az provider register --namespace Microsoft.Network
49
-
```
50
-
51
-
### Create a Standard Load Balancer
52
31
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).
53
32
54
33
## Create IPv6 addresses
@@ -166,8 +145,7 @@ You can view the IPv6 dual stack virtual network in Azure portal as follows:
166
145
167
146
168
147
169
-
> [!NOTE]
170
-
> The IPv6 for Azure virtual network is available in the Azure portal in read-only for this preview release.
Copy file name to clipboardExpand all lines: articles/virtual-network/ipv6-add-to-existing-vnet-powershell.md
+4-28Lines changed: 4 additions & 28 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,49 +11,26 @@ ms.devlang: na
11
11
ms.topic: article
12
12
ms.tgt_pltfrm: na
13
13
ms.workload: infrastructure-services
14
-
ms.date: 10/21/2019
14
+
ms.date: 03/13/2020
15
15
ms.author: kumud
16
16
---
17
17
18
-
# Upgrade an IPv4 application to IPv6 in Azure virtual network - PowerShell (Preview)
18
+
# Upgrade an IPv4 application to IPv6 in Azure virtual network - PowerShell
19
19
20
20
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:
21
21
- IPv6 address space for the virtual network and subnet
22
22
- a Standard Load Balancer with both IPv4 and IPV6 frontend configurations
23
23
- VMs with NICs that have both an IPv4 + IPv6 configuration
24
24
- IPv6 Public IP so the load balancer has Internet-facing IPv6 connectivity
25
25
26
-
> [!Important]
27
-
> 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.
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.
32
31
33
32
## Prerequisites
34
33
35
-
### Register the service
36
-
37
-
Before you deploy a dual stack application in Azure, you must configure your subscription for this preview feature using the following Azure PowerShell:
It takes up to 30 minutes for feature registration to complete. You can check your registration status by running the following Azure PowerShell command:
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).
58
35
59
36
## Retrieve the resource group
@@ -172,8 +149,7 @@ You can view the IPv6 dual stack virtual network in Azure portal as follows:
172
149
173
150
174
151
175
-
> [!NOTE]
176
-
> The IPv6 for Azure virtual network is available in the Azure portal in read-only for this preview release.
0 commit comments