Hi @prasantc,
Welcome to Microsoft Q&A Forum, thank you for posting your query here!
Azure Traffic Manager operates on a DNS-based mechanism. For any on-premises VM to be recognized, it must have a public IP and a DNS name to ensure proper resolution.
Similarly, in Azure, the VM setup should include a public IP and a DNS name so that both the on-premises and Azure public IPs can be configured in Traffic Manager using priority routing.
Alternatively, if you want to avoid assigning public IPs to individual VMs, you can:
- Disable the public IP on the VM and use only a private IP.
- Add your vm's in the Load Balancer with a public IP in front of the VMs.
Noe: But the endpoint should have a public DNS not private DNS then only it will work
Feel free to reach out if you have any further questions or need additional information—I’m happy to assist!
Please provide your valuable comments
Please do not forget to "Accept the answer” and “upvote it” wherever the information provided helps you, this can be beneficial to other community members.it would be greatly appreciated and helpful to others.