Update azure-virtual-network-limits.md

Author: anavinahar

includes/azure-virtual-network-limits.md

@@ -61,51 +61,6 @@ The following limits apply only for networking resources managed through **Azure
 
 <sup>2</sup>Public IP addresses limit refers to the total amount of Public IP addresses, including Basic and Standard. 
 
-#### <a name="load-balancer"></a>Load balancer limits
-The following limits apply only for networking resources managed through Azure Resource Manager per region per subscription. Learn how to [view your current resource usage against your subscription limits](../articles/networking/check-usage-against-limits.md).
-
-**Standard Load Balancer**
-
-| Resource                                | Limit         |
-|-----------------------------------------|-------------------------------|
-| Load balancers                          | 1,000                         |
-| Frontend IP configurations              | 600                           |
-| Rules (Load Balancer + Inbound NAT) per resource  | 1,500               |
-| Rules per NIC (across all IPs on a NIC), rules per IP (IP based LB)<sup>1<sup> | 300                           |
-| High-availability ports rule            | 1 per internal frontend       |
-| Outbound rules per Load Balancer        | 600                           |
-| Backend pool size                       | 5,000                         |
-| Azure global Load Balancer Backend pool size                       | 300                         |
-| Backend IP configurations per frontend <sup>2<sup> | 10,000                        |
-| Backend IP configurations across all frontends | 500,000 |
-
-<sup>1<sup> Each NIC can have a total of 300 rules (load balancing, inbound NAT, and outbound rules combined) configured across all IP configurations on the NIC. For IP based LBs, this limit is per IP.
-<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.
-
-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).
-
-**Gateway Load Balancer**
-
-| Resource                                | Limit        |
-|-----------------------------------------|------------------------------|
-| Resources chained per Load Balancer (LB frontend configurations or VM NIC IP configurations combined) | 100 |
-
-All limits for Standard Load Balancer also apply to Gateway Load Balancer.
-
-**Basic Load Balancer**
-
-| Resource                                | Limit        |
-|-----------------------------------------|------------------------------|
-| Load balancers                          | 1,000                        |
-| Rules per resource                      | 250                          |
-| Rules per NIC (across all IPs on a NIC) | 300                          |
-| Frontend IP configurations <sup>3<sup>  | 200                          |
-| Backend pool size                       | 300 IP configurations, single availability set |
-| Availability sets per Load Balancer     | 1                            |
-| Load Balancers per VM                   | 2 (1 Public and 1 internal)  |
-
-<sup>3</sup> The limit for a single discrete resource in a backend pool (standalone virtual machine, availability set, or virtual machine scale-set placement group) is to have up to 250 Frontend IP configurations across a single Basic Public Load Balancer and Basic Internal Load Balancer.
-
 <a name="virtual-networking-limits-classic"></a>The following limits apply only for networking resources managed through the **classic** deployment model per subscription. Learn how to [view your current resource usage against your subscription limits](../articles/networking/check-usage-against-limits.md).
 
 | Resource | Default limit | Maximum limit |