Skip to content

Commit abefefc

Browse files
authored
Merge pull request #110104 from EricTheRed999/patch-4
Update ipv6-overview.md
2 parents aa257c7 + bbf6181 commit abefefc

File tree

1 file changed

+5
-3
lines changed

1 file changed

+5
-3
lines changed

articles/virtual-network/ipv6-overview.md

Lines changed: 5 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -52,7 +52,8 @@ IPv6 for Azure VNet includes the following capabilities:
5252
- Optional outbound rules which provide full declarative control over outbound connectivity to scale and tune this ability to your specific needs.
5353
- Optional multiple front-end configurations which enable a single load balancer to use multiple IPv6 public IP addresses- the same frontend protocol and port can be reused across frontend addresses.
5454
- Optional IPv6 ports can be reused on backend instances using the *Floating IP* feature of load-balancing rules
55-
- [Standard IPv6 internal Load Balancer](ipv6-dual-stack-standard-internal-load-balancer-powershell.md) support to create resilient multi-tier applications within Azure VNETs.
55+
- Note: Load balancing does not perform any protocol translation (no NAT64).
56+
- [Standard IPv6 internal Load Balancer](ipv6-dual-stack-standard-internal-load-balancer-powershell.md) support to create resilient multi-tier applications within Azure VNETs.
5657
- Basic IPv6 public Load Balancer support for compatibility with legacy deployments
5758
- [Reserved IPv6 Public IP addresses and address ranges](ipv6-public-ip-address-prefix.md) provide stable, predictable IPv6 addresses which ease whitelisting of your azure-hosted applications for your company and your customers.
5859
- Instance-level Public IP provides IPv6 Internet connectivity directly to individual VMs.
@@ -67,8 +68,9 @@ IPv6 for Azure VNET is a foundational feature set which enables customers to hos
6768

6869
## Limitations
6970
The current IPv6 for Azure virtual network release has the following limitations:
70-
- IPv6 for Azure virtual network is available in all global Azure regions, but only in Global Azure- not yet in government clouds.
71-
- ExpressRoute and VPN gateways cannot be used in a VNET with IPv6 enabled, either directly or peered with "UseRemoteGateway".
71+
- IPv6 for Azure virtual network is available in all global Azure Commercial regions using all deployment methods. Deployment in the US Government cloud is temporarily limited to ARM (JSON) template, Command Line Interface (CLI) and Powershell. IPv6 support in the US Government cloud portal will be availble shortly.
72+
- ExpressRoute gateways CAN be used for IPv4-only traffic in a VNET with IPv6 enabled. Support for IPv6 traffic is on our roadmap.
73+
- VPN gateways CANNOT be used in a VNET with IPv6 enabled, either directly or peered with "UseRemoteGateway".
7274
- The Azure platform (AKS, etc.) does not support IPv6 communication for Containers.
7375

7476
## Pricing

0 commit comments

Comments
 (0)