added note about internal load balancer not working with ipv6 + floating ip

Author: brianlehr

articles/load-balancer/load-balancer-floating-ip.md

@@ -68,7 +68,7 @@ netsh interface ipv4 set interface “interfacename” weakhostsend=enabled
 
 ## <a name = "limitations"></a>Limitations
 
-- Floating IP is not currently supported on secondary IP configurations for Load Balancing scenarios
+- Floating IP is not currently supported on secondary IP configurations for Load Balancing scenarios.  Note that this does not apply to Public load balancers with dual-stack configurations or to architectures that utilize a NAT Gateway for outbound connectivity.
 
 ## Next steps
 

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

@@ -67,6 +67,7 @@ IPv6 for Azure VNET is a foundational feature set which enables customers to hos
 ## Limitations
 The current IPv6 for Azure virtual network release has the following limitations:
 - VPN gateways currently support IPv4 traffic only, but they still CAN be deployed in a Dual-stacked VNET.
+- Dual-stack configurations that use Floating IP can only be used with Public load balancers (not Internal load balancers)
 - Application Gateway v2 does not currently support IPv6. It can operate in a dual stack VNet using only IPv4, but the gateway subnet must be IPv4-only. Application Gateway v1 does not support dual stack VNets.
 - 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.