Merge pull request #239636 from cburuzie/patch-47

Update azure-virtual-network-limits.md

Author: prmerger-automator[bot]

includes/azure-virtual-network-limits.md

@@ -74,13 +74,10 @@ The following limits apply only for networking resources managed through Azure R
 | High-availability ports rule            | 1 per internal frontend       |
 | Outbound rules per Load Balancer        | 600                           |
 | Backend pool size                       | 5,000                         |
-| Load Balancers per VM <sup>1<sup>       | 2 (1 Public and 1 internal)   |
-| Backend IP configurations per frontend <sup>2<sup> | 10,000                        |
+| Backend IP configurations per frontend <sup>1<sup> | 10,000                        |
 | Backend IP configurations across all frontends | 500,000 |
 
-<sup>1</sup> An exception to this limit is that 2 public load balancers can be in front of a VM if an IPv4 address config is used for one load balancer and IPv6 address config is used for the second. Note that this limit does not apply to IP-based load balancers. For more information on IP-based backend pools, refer to our documentation on [IP-based load balancers](../articles/load-balancer/backend-pool-management.md).
-
-<sup>2</sup> Backend IP configurations are aggregated across all load balancer rules including load balancing, inbound NAT, and outbound rules. Each rule a backend pool instance is configured to counts as one configuration.
+<sup>1</sup> Backend IP configurations are aggregated across all load balancer rules including load balancing, inbound NAT, and outbound rules. Each rule a backend pool instance is configured to counts as one configuration.
 
 Load Balancer doesn't apply any throughput limits. However, throughput limits for virtual machines and virtual networks still apply. For more information, see [Virtual machine network bandwidth](../articles/virtual-network/virtual-machine-network-throughput.md).