Hello @Pujari, Vaibhav ,
I understand that you are unable to work with mTLS (mutual authentication) when using Azure Load Balancer.
Azure Load Balancer itself doesn't directly support mutual TLS. Azure Load Balancer primarily operates at the transport layer (Layer 4) of the OSI model and is designed to distribute network traffic among multiple servers to ensure high availability and reliability of applications.
Azure Application Gateway supports certificate-based mutual authentication.
However, one thing to note here is that Azure Load Balancer is a pass-through network load balancer. Protocol handshakes always occur directly between the client and the back-end pool instance. Because the load balancer doesn't interact with the TCP payload nor does it provide TLS offload, you can build comprehensive encrypted scenarios.
So mutual authentication should work between your client and application.
Refer: https://learn.microsoft.com/en-us/azure/load-balancer/concepts
The only limitation that I could find is the below:
HTTPS probes don't support mutual authentication with a client certificate.
Requested you to share more details about your setup and you checked the health probes settings of your load balancer and found that it was using HTTPS protocol. You changed it to TCP protocol on port 443, and it works now.
Kindly let us know if the above helps or you need further assistance on this issue.
Please don’t forget to "Accept the answer" wherever the information provided helps you, this can be beneficial to other community members.