Merge pull request #220476 from tfitzmac/1205limits

add details about load balancer limits

Author: prmerger-automator[bot]

includes/azure-virtual-network-limits.md

@@ -5,7 +5,7 @@
  author: anavinahar
  ms.service: networking
  ms.topic: include
- ms.date: 01/14/2020
+ ms.date: 12/05/2022
  ms.author: anavin
  ms.custom: include file
 
@@ -81,13 +81,17 @@ The following limits apply only for networking resources managed through Azure R
 <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.
- 
+
+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        |