You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
| Rules per NIC (across all IPs on a NIC)<sup>1<sup>| 300 |
75
75
| High-availability ports rule | 1 per internal frontend |
76
76
| Outbound rules per Load Balancer | 600 |
77
77
| Backend pool size | 5,000 |
78
78
| Azure global Load Balancer Backend pool size | 300 |
79
-
| Backend IP configurations per frontend <sup>1<sup> | 10,000 |
79
+
| Backend IP configurations per frontend <sup>2<sup> | 10,000 |
80
80
| Backend IP configurations across all frontends | 500,000 |
81
81
82
-
<sup>1</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.
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.
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.
83
84
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).
0 commit comments