Hello @vijaiya prathap ,
Thanks for reaching Azure Q and A platform.
Thanks for bring these questions, as it would be useful for the community.
Please do go through the below mentioned points, which would give you an mere understanding of the concept of Traffic Manager.
- Traffic Manager performs DNS based load balancing. As we know the concept and working of the Traffic Manager.
- If you see the below image, you would get confused on why we have mentioned that Traffic Manager recommended traffic is non-http.
- Traffic Manager is a DNS-based traffic load balancer that enables you to distribute traffic optimally to services across global Azure regions, while providing high availability and responsiveness. Because Traffic Manager is a DNS-based load-balancing service, **it load balances only at the domain level. **
- Please check the below image:
- So, As explained in How Traffic Manager Works, Traffic Manager works at the DNS level. It uses DNS responses to direct clients to the appropriate service endpoint. Clients connect to the service endpoint directly, not through Traffic Manager. Therefore, Traffic Manager doesn't see the HTTP traffic between the client and the server.
- To explain in the simple manner, if you have a Virtual Machine, which has a domain name to connect to the Virtual Machine on the remote access 3389. Then using Traffic Manager, it could give you the nearest VM endpoint via DNS based load balancing.
Please do let us know if you have more query on this ask.
--Please don't forget to "[Accept the answer]" and “[Upvote]” if the reply is helpful--
Please don’t forget to close the thread by clicking "Accept the answer" wherever the information provided helps you, as this can be beneficial to other community members.
Regards, Priya Kumar