Skip to content

Commit 1199ba7

Browse files
authored
Merge pull request #291744 from anavinahar/patch-247930
Update azure-virtual-network-limits.md
2 parents 49dbf02 + f6ba9bb commit 1199ba7

File tree

1 file changed

+0
-45
lines changed

1 file changed

+0
-45
lines changed

includes/azure-virtual-network-limits.md

Lines changed: 0 additions & 45 deletions
Original file line numberDiff line numberDiff line change
@@ -61,51 +61,6 @@ The following limits apply only for networking resources managed through **Azure
6161

6262
<sup>2</sup>Public IP addresses limit refers to the total amount of Public IP addresses, including Basic and Standard.
6363

64-
#### <a name="load-balancer"></a>Load balancer limits
65-
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).
66-
67-
**Standard Load Balancer**
68-
69-
| Resource | Limit |
70-
|-----------------------------------------|-------------------------------|
71-
| Load balancers | 1,000 |
72-
| Frontend IP configurations | 600 |
73-
| Rules (Load Balancer + Inbound NAT) per resource | 1,500 |
74-
| Rules per NIC (across all IPs on a NIC), rules per IP (IP based LB)<sup>1<sup> | 300 |
75-
| High-availability ports rule | 1 per internal frontend |
76-
| Outbound rules per Load Balancer | 600 |
77-
| Backend pool size | 5,000 |
78-
| Azure global Load Balancer Backend pool size | 300 |
79-
| Backend IP configurations per frontend <sup>2<sup> | 10,000 |
80-
| Backend IP configurations across all frontends | 500,000 |
81-
82-
<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.
83-
<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.
84-
85-
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).
86-
87-
**Gateway Load Balancer**
88-
89-
| Resource | Limit |
90-
|-----------------------------------------|------------------------------|
91-
| Resources chained per Load Balancer (LB frontend configurations or VM NIC IP configurations combined) | 100 |
92-
93-
All limits for Standard Load Balancer also apply to Gateway Load Balancer.
94-
95-
**Basic Load Balancer**
96-
97-
| Resource | Limit |
98-
|-----------------------------------------|------------------------------|
99-
| Load balancers | 1,000 |
100-
| Rules per resource | 250 |
101-
| Rules per NIC (across all IPs on a NIC) | 300 |
102-
| Frontend IP configurations <sup>3<sup> | 200 |
103-
| Backend pool size | 300 IP configurations, single availability set |
104-
| Availability sets per Load Balancer | 1 |
105-
| Load Balancers per VM | 2 (1 Public and 1 internal) |
106-
107-
<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.
108-
10964
<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).
11065

11166
| Resource | Default limit | Maximum limit |

0 commit comments

Comments
 (0)