Merge pull request #272383 from siddomala/IPv6update

route server ipv6 update

Author: prmerger-automator[bot]

articles/expressroute/expressroute-howto-add-ipv6-portal.md

@@ -80,7 +80,8 @@ Follow these steps if you plan to connect to a new set of Azure resources using
 While IPv6 support is available for connections to deployments in global Azure 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 Virtual WAN
+* Use of ExpressRoute with [Route Server](../route-server/route-server-faq.md#does-azure-route-server-support-ipv6)
 * FastPath with non-ExpressRoute Direct circuits
 * FastPath with circuits in the following peering locations: Dubai
 * 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.

articles/route-server/route-server-faq.md

@@ -38,10 +38,10 @@ Azure Router Server needs to ensure connectivity to the backend service that man
 
 ### Does Azure Route Server support IPv6?
 
-No. We'll add IPv6 support in the future. If you have deployed an ExpressRoute virtual network gateway in a virtual network with an IPv6 address space and later deploy an Azure Route Server in the same virtual network, this will break ExpressRoute connectivity for IPv6 traffic.
+No. We'll add IPv6 support in the future. If you have deployed a virtual network with an IPv6 address space and later deploy an Azure Route Server in the same virtual network, this will break connectivity for IPv6 traffic.
 
 > [!WARNING]
-> When you deploy an Azure Route Server in a virtual network with an IPv6 address space, this will also break ExpressRoute connectivity for IPv4 traffic. This issue will be fixed in our next release to ensure IPv4 traffic continues to work as expected.
+> If you have deployed a virtual network with an IPv6 address space and later deploy an Azure Route Server in the same virtual network, this will also break connectivity for IPv4 traffic. This issue will be fixed in our next release to ensure IPv4 traffic continues to work as expected.
 
 ## Routing
 

articles/virtual-network/ip-services/ipv6-overview.md

@@ -107,7 +107,9 @@ The current IPv6 for Azure Virtual Network release has the following limitations
 
 - ICMPv6 isn't currently supported in Network Security Groups.
 
-- Azure Virtual WAN currently supports IPv4 traffic only.
+- Azure Virtual WAN currently supports IPv4 traffic only. 
+
+- Azure Route Server currently [supports IPv4 traffic only](../../route-server/route-server-faq.md#does-azure-route-server-support-ipv6).
 
 - Azure Firewall doesn't currently support IPv6. It can operate in a dual stack virtual network using only IPv4, but the firewall subnet must be IPv4-only.