Add IPv6 support for private peering using the Azure portal

This article describes how to add IPv6 support to connect via ExpressRoute to your resources in Azure using the Azure portal.

From a web browser, sign in to the Azure portal.

1. Create an ExpressRoute circuit or navigate to the existing circuit you want to change.

2. Select the Azure private peering configuration.

3. Add an IPv6 Private Peering to your existing IPv4 Private Peering configuration by selecting "Both" for Subnets, or only enable IPv6 Private Peering on your new circuit by selecting "IPv6". Provide a pair of /126 IPv6 subnets that you own for your primary link and secondary links. From each of these subnets, you assign the first usable IP address to your router as Azure uses the second usable IP for its router. Save your peering configuration once you defined all parameters.

   

4. After the configuration is accepted successfully, you should see something similar to the following example.

   

Follow these steps if you have an existing environment of Azure resources that you would like to use your IPv6 Private Peering with.

1. Navigate to the virtual network that your ExpressRoute circuit is connected to.

2. Navigate to the Address space tab and add an IPv6 address space to your virtual network. Save your address space.

   

3. Navigate to the Subnets tab and select the GatewaySubnet. Check Add IPv6 address space and provide an IPv6 address space for your subnet. The gateway IPv6 subnet should be /64 or larger. Save your configuration once you defined all parameters.

   

4. If you have an existing zone-redundant gateway, run the following command in PowerShell to enable IPv6 connectivity (note that it can take up to 1 hour for changes to reflect). Otherwise, create the virtual network gateway using any SKU and a Standard, Static public IP address. If you plan to use FastPath, use UltraPerformance or ErGw3AZ (note that this option is only available for circuits using ExpressRoute Direct).

   $gw = Get-AzVirtualNetworkGateway -Name "GatewayName" -ResourceGroupName "ExpressRouteResourceGroup"
   Set-AzVirtualNetworkGateway -VirtualNetworkGateway $gw
   

   Note

   If you have an existing gateway that is not zone-redundant (meaning it is Standard, High Performance, or Ultra Performance SKU) and uses a Basic public IP address, you will need to delete and recreate the gateway using any SKU and a Standard, Static public IP address.

Follow these steps if you plan to connect to a new set of Azure resources using your IPv6 Private Peering.

1. Create a dual-stack virtual network with both IPv4 and IPv6 address space. For more information, see Create a virtual network.

2. Create the dual-stack gateway subnet.

3. Create the virtual network gateway using any SKU and a Standard, Static public IP address. If you plan to use FastPath, use UltraPerformance or ErGw3AZ (note that this option is only available for circuits using ExpressRoute Direct). NOTE: Use the PowerShell instructions for this step as the Azure portal experience is still under development.

4. Link your virtual network to your ExpressRoute circuit.

While IPv6 support is available for connections to deployments in Azure operated by 21Vianet regions, it doesn't support the following use cases:

• Connections to existing ExpressRoute gateways that aren't zone-redundant. Newly created ExpressRoute gateways of any SKU (both zone-redundant and not) using a Standard, Static IP address can be used for dual-stack ExpressRoute connections

• Use of ExpressRoute with Virtual WAN

• Use of ExpressRoute with Route Server

• Coexistence with VPN Gateway for IPv6 traffic. You can still configure coexistence with VPN Gateway in a dual-stack virtual network, but VPN Gateway only supports IPv4 traffic.

• It isn't possible to connect a dual-stack ExpressRoute Virtual Network Gateway to an ExpressRoute Circuit that only has IPv4 enabled on the Private Peering. IPv6 must also be enabled on the ExpressRoute Circuit. You must also configure IPv6 on your on-premises CPE device.

To troubleshoot ExpressRoute problems, see the following articles:

• Verifying ExpressRoute connectivity
• Troubleshooting network performance