Skip to content

Commit ec3ceda

Browse files
committed
modified docs to reflect further testing on secondary configurations
1 parent 15b598a commit ec3ceda

File tree

1 file changed

+1
-0
lines changed

1 file changed

+1
-0
lines changed

articles/load-balancer/load-balancer-floating-ip.md

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -149,6 +149,7 @@ sudo ufw allow 80/tcp
149149

150150
- With Floating IP enabled on a load balancing rule, your application must use the primary IP configuration of the network interface for outbound.
151151
- If your application binds to the frontend IP address configured on the loopback interface in the guest OS, Azure's outbound won't rewrite the outbound flow, and the flow fails. Review [outbound scenarios](load-balancer-outbound-connections.md).
152+
- You can't use Floating IP on secondary IP configurations for Load Balancing scenarios. This limitation doesn't apply to Public load balancers where the secondary IP configuration is IPv6 an part of a dual-stack configuration or to architectures that utilize a NAT Gateway for outbound connectivity.
152153

153154
## Next steps
154155

0 commit comments

Comments
 (0)