Merge pull request #289822 from mbender-ms/lb-vnet-limits

load balancer - PRs for vnet limits

Author: v-dirichards

articles/azure-resource-manager/management/azure-subscription-service-limits.md

@@ -411,6 +411,9 @@ For limits specific to Media Services v2 (legacy), see [Media Services v2 (legac
 
 [!INCLUDE [azure-virtual-network-limits](../../../includes/azure-virtual-network-limits.md)]
 
+### <a name="load-balancer"></a>Azure Load Balancer limits
+[!INCLUDE [azure-load-balancer-limits](../../../includes/load-balancer-limits.md)]
+
 ### Application Gateway limits
 
 The following table applies to v1, v2, Standard, and WAF SKUs unless otherwise stated.

articles/load-balancer/load-balancer-basic-upgrade-guidance.md

@@ -107,4 +107,4 @@ No, this retirement won't impact your existing or new deployments on CSES. This
 For guidance on upgrading Basic Public IP addresses to Standard SKUs, see:
 
 > [!div class="nextstepaction"]
-> [Upgrading a Basic Public IP to Standard Public IP - Guidance](../virtual-network/ip-services/public-ip-basic-upgrade-guidance.md)
+> [Upgrading a Basic Public IP to Standard Public IP - Guidance](../virtual-network/ip-services/public-ip-basic-upgrade-guidance.md)

articles/load-balancer/load-balancer-common-deployment-errors.md

@@ -41,4 +41,4 @@ This article describes some common Azure Load Balancer deployment errors and pro
 ## Next steps
 
 * Look through the Azure Load Balancer [SKU comparison table](./skus.md)
-* Learn about [Azure Load Balancer limits](../azure-resource-manager/management/azure-subscription-service-limits.md#load-balancer)
+* Learn about [Azure Load Balancer limits](../azure-resource-manager/management/azure-subscription-service-limits.md#load-balancer)

articles/load-balancer/load-balancer-multivip-overview.md

@@ -83,4 +83,4 @@ In this example, you remove a frontend from your Load Balancer.
 
 ## Next steps
 
-- Review [Outbound connections](load-balancer-outbound-connections.md) to understand the effect of multiple frontends on outbound connection behavior.
+- Review [Outbound connections](load-balancer-outbound-connections.md) to understand the effect of multiple frontends on outbound connection behavior.

articles/load-balancer/skus.md

@@ -27,7 +27,7 @@ To compare and understand the differences between Basic and Standard SKU, see th
 | **Scenario** |  Equipped for load-balancing network layer traffic when high performance and ultra-low latency is needed. Routes traffic within and across regions, and to availability zones for high resiliency. | Equipped for small-scale applications that don't need high availability or redundancy. Not compatible with availability zones. |
 | **Backend type** | IP based, NIC based | NIC based |
 | **Protocol** | TCP, UDP | TCP, UDP |
-| **Backend pool endpoints** | Any virtual machines or virtual machine scale sets in a single virtual network. This includes usage of a single availability set. | Virtual machines in a single availability set or virtual machine scale set. |
+| **Backend pool endpoints** | Any virtual machines or virtual machine scale sets in a single virtual network | Virtual machines in a single availability set or virtual machine scale set |
 | **[Health probes](./load-balancer-custom-probe-overview.md#probe-protocol)** | TCP, HTTP, HTTPS | TCP, HTTP |
 | **[Health probe down behavior](./load-balancer-custom-probe-overview.md#probe-down-behavior)** | TCP connections stay alive on an instance probe down __and__ on all probes down. | TCP connections stay alive on an instance probe down. All TCP connections end when all probes are down. |
 | **Availability Zones** | Zone-redundant, zonal, or non-zonal frontend IP configurations can be used for inbound and outbound traffic | Not available |
@@ -60,4 +60,4 @@ For more information, see [Load balancer limits](../azure-resource-manager/manag
 - Learn about [Health Probes](load-balancer-custom-probe-overview.md).
 - Learn about using [Load Balancer for outbound connections](load-balancer-outbound-connections.md).
 - Learn about [Standard Load Balancer with HA Ports load balancing rules](load-balancer-ha-ports-overview.md).
-- Learn more about [Network Security Groups](../virtual-network/network-security-groups-overview.md).
+- Learn more about [Network Security Groups](../virtual-network/network-security-groups-overview.md).

articles/operator-nexus/reference-limits-and-quotas.md

@@ -95,4 +95,4 @@ The table here briefly mentions other Azure resources that are necessary. Howeve
 | Load Balancers (Standard)	   | [Load Balancer Limits](../azure-resource-manager/management/azure-subscription-service-limits.md#load-balancer) |
 | Public IP Address (Standard) | [Public IP Address Limits](../azure-resource-manager/management/azure-subscription-service-limits.md#publicip-address) |
 | Azure Monitor Metrics	       | [Azure Monitor Limits](../azure-resource-manager/management/azure-subscription-service-limits.md#azure-monitor-limits) |
-| Log Analytics Workspace	   | [Log Analytics Workspace Limits](/azure/azure-monitor/service-limits#log-analytics-workspaces) |
+| Log Analytics Workspace	   | [Log Analytics Workspace Limits](/azure/azure-monitor/service-limits#log-analytics-workspaces) |

includes/load-balancer-limits.md

@@ -0,0 +1,53 @@
+---
+ title: include file
+ description: include file
+ services: networking
+ author: anavinahar
+ ms.service: networking
+ ms.topic: include
+ ms.date: 10/24/2024
+ ms.author: anavin
+ ms.custom: include file
+
+---
+### 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)<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.
+<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.