Merge pull request #211058 from anavinahar/patch-262

Update azure-virtual-network-limits.md

Author: prmerger-automator[bot]

includes/azure-virtual-network-limits.md

@@ -74,12 +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>2<sup>       | 2 (1 Public and 1 internal)   |
+| Load Balancers per VM <sup>1<sup>       | 2 (1 Public and 1 internal)   |
 | Backend IP configurations per frontend  | 10,000                        |
 
-<sup>1</sup> The limit is up to 1,200 resources, in any combination of standalone virtual machine resources, availability set resources, and virtual machine scale-set placement groups.
-
-<sup>2</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.
+<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.
 
 **Gateway Load Balancer**