load balancer | Maintenance | Update load-balancer-troubleshoot-backend-traffic.md

Author: mbender-ms

articles/load-balancer/load-balancer-troubleshoot-backend-traffic.md

@@ -6,7 +6,7 @@ author: mbender-ms
 manager: dcscontentpm
 ms.service: azure-load-balancer
 ms.topic: troubleshooting
-ms.date: 02/23/2024
+ms.date: 03/05/2025
 ms.author: mbender
 ms.custom: engagement-fy23
 ---
@@ -107,8 +107,6 @@ When the flow maps back to itself, the outbound flow appears to originate from t
 
 The symptom for this scenario is intermittent connection timeouts when the flow returns to the same backend that originated the flow. Common workarounds include insertion of a proxy layer behind the internal load balancer and using Direct Server Return (DSR) style rules. For more information, see [Multiple frontends for Azure Load Balancer](load-balancer-multivip-overview.md).
 
-You can combine an internal load balancer with any third-party proxy or use internal [Application Gateway](../application-gateway/overview.md) for proxy scenarios with HTTP/HTTPS. While you could use a public load balancer to mitigate this issue, the resulting scenario is prone to [SNAT exhaustion](load-balancer-outbound-connections.md). Avoid this second approach unless carefully managed.
-
 ## Virtual machines removed from a load balancer are receiving traffic
 
 It is by design that existing TCP connections will continue to a virtual machine even after a backend is removed from a load balancer. Once a connection is routed to a backend instance by the load balancer, traffic is established directly between the client and the backend instance. Connections will continue untl the virtual machine is stopped or deallocated.