• ExpressRoute gateways CAN be used for IPv4-only traffic in a VNET with IPv6 enabled. Support for IPv6 traffic is on our roadmap.

• VPN gateways CANNOT be used in a VNET with IPv6 enabled, either directly or peered with "UseRemoteGateway".

• The Azure platform (AKS, etc.) does not support IPv6 communication for Containers.

• IPv6-only Virtual Machines or Virtual Machines Scale Sets are not supported, each NIC must include at least one IPv4 IP configuration.

• When adding IPv6 to existing IPv4 deployments, IPv6 ranges can not be added to a VNET with existing resource navigation links.

• Forward DNS for IPv6 is supported for Azure public DNS today but Reverse DNS is not yet supported.

That doesn't even being to cover it! There's all sorts of other fun limitations scattered all over the place, you'd have to spend weeks scraping them together into a pile of shame.

Examples include:

• The maximum prefix IPv6 prefix size available is just 16 addresses, which is hilariously tiny and totally negates the core benefit of IPv6's huge address space: https://docs.microsoft.com/en-us/azure/virtual-network/publi...

• Forced NAT of IPv6, which entirely defeats the purpose and benefit of this protocol over IPv4.

• NAT doesn't interact with IPv6 address family. NAT can't be deployed on a subnet with an IPv6 prefix. https://docs.microsoft.com/en-us/azure/virtual-network/nat-g...

• If you add an IPv6 address to a rule, [Azure] firewall fails. https://docs.microsoft.com/en-us/azure/firewall/overview#kno...

• None of their PaaS services support IPv6 firewall rules. https://stackoverflow.com/questions/40461803/allow-ipv6-addr...

Etc, etc, etc...