Skip to content

Commit 65e4cc8

Browse files
Merge pull request #288048 from thisisanniefang/patch-82
Clarify IP selection behavior in multiple frontend scenario for outbo…
2 parents a431d6a + 1fc0051 commit 65e4cc8

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

articles/load-balancer/load-balancer-outbound-connections.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -52,6 +52,8 @@ Calculate ports per instance as follows:
5252

5353
If you have Virtual Machine Scale Sets in the backend, it's recommended to allocate ports by "maximum number of backend instances". If more VMs are added to the backend than remaining SNAT ports allowed, scale out of Virtual Machine Scale Sets could be blocked, or the new VMs won't receive sufficient SNAT ports.
5454

55+
When multiple frontend IPs are configured using outbound rules, outbound connections may come from any of the frontend IPs configured to the backend instance. We do not recommend building any dependencies on which frontend IP may be selected for connections.
56+
5557
For more information about outbound rules, see [Outbound rules](outbound-rules.md).
5658

5759
## 2. Associate a NAT gateway to the subnet

0 commit comments

Comments
 (0)