Hello @Sir A ,
Thanks for reaching out.
I hope you are referring back-end application as multiple servers (such as server farm) on Server 1 and 2, if so then user request may end up in an infinite loop between connector and application with above manner as AAD proxy connector relay on DNS resolution which point it to backend application.
Therefore, the best practices for load balancing among multiple app servers, When the connector group that's assigned to the Application Proxy application has two or more connectors, and you’re running the back-end web application on multiple servers (server farm), a good load-balancing strategy is required. A good strategy ensures that servers pick up client requests evenly and prevents over- or under-utilization of servers in the server farm.
To learn more, refer : https://learn.microsoft.com/en-us/azure/active-directory/app-proxy/application-proxy-high-availability-load-balancing#best-practices-for-load-balancing-among-multiple-app-servers
**Scenarios : **
The simplest scenario is where the back-end web application doesn’t require session stickiness (session persistence). Any request from the user can be handled by any back-end application instance in the server farm. You can use a layer 4 load balancer and configure it with no affinity
You can Install one or more Azure AD proxy connect on individual server (server X) which is close to each back-end server (Server 1 and 2) and then create localhost or DNS entry which to point it to load balancer as shown below by this way load balancer ensures that servers pick up client requests evenly and prevents over- or under-utilization of servers in the server farm.
Hope this helps.
Please "Accept the answer" if the information helped you. This will help us and others in the community as well.