Update private-link-service-overview.md

Updated for clarity on the impact of TCP Proxy v2 configuration on a Private Link service. This is important to update as customers faced the issue of health probes failing due to other PLS with shared backends and load balancers not having TCP Proxy v2 configuration.

Author: altheapm

articles/private-link/private-link-service-overview.md

@@ -109,7 +109,7 @@ Visibility controls the exposure settings whereas auto-approval controls the app
 ## Getting connection Information using TCP Proxy v2
 
 > [!NOTE]
-> Only one connection between a PLS and Internal Load Balancer is supported when using TCP Proxy v2 
+> TCP Proxy v2 configuration on a Private Link service activates for all load balancers and their backend VMs. If TCP Proxy v2 is configured on one PLS, configure it on other PLS resources if they are sharing the same load balancer or backend pool, otherwise health probes will fail. 
 
 In the private link service, the source IP address of the packets coming from private endpoint is network address translated (NAT) on the service provider side using the NAT IP allocated from the provider's virtual network. The applications receive the allocated NAT IP address instead of actual source IP address of the service consumers. If your application needs an actual source IP address from the consumer side, you can enable proxy protocol on your service and retrieve the information from the proxy protocol header. In addition to source IP address, proxy protocol header also carries the LinkID of the private endpoint. Combination of source IP address and LinkID can help service providers uniquely identify their consumers. 
 
@@ -149,7 +149,7 @@ The following are the known limitations when using the Private Link service:
 
 - For an Inbound NAT rule with type set to *backend pool* to operate with Azure Private Link Service, a load balancing rule must be configured.
 
-- TCP Proxy v2 only supports one connection between a PLS and Internal Load Balancer
+- TCP Proxy v2 configuration on a Private Link service activates for all load balancers and their backend VMs. If TCP Proxy v2 is configured on one PLS, configure it on other PLS resources if they are sharing the same load balancer or backend pool, otherwise health probes will fail.
 
 ## Next steps