Skip to content

Commit 4dd8132

Browse files
Merge pull request #295186 from thisisanniefang/patch-91
Clarify GWLB consumer chain limit
2 parents 2a12ce9 + a429c24 commit 4dd8132

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

includes/load-balancer-limits.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ Load Balancer doesn't apply any throughput limits. However, throughput limits fo
3434

3535
| Resource | Limit |
3636
|-----------------------------------------|------------------------------|
37-
| Resources chained per Load Balancer (LB frontend configurations or VM NIC IP configurations combined) | 100 |
37+
| Resources chained per Gateway Load Balancer frontend (Load Balancer frontend configurations or VM NIC IP configurations combined) | 100 |
3838

3939
All limits for Standard Load Balancer also apply to Gateway Load Balancer.
4040

@@ -50,4 +50,4 @@ All limits for Standard Load Balancer also apply to Gateway Load Balancer.
5050
| Availability sets per Load Balancer | 1 |
5151
| Load Balancers per VM | 2 (1 Public and 1 internal) |
5252

53-
<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.
53+
<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.

0 commit comments

Comments
 (0)