Traffic Manager Private Endpoints
For Traffic Manager, allow us to use private endpoints (load-balancer) for fail over. It looks like someone created a work around using Web Apps but would like to have a supported method for RFC1918 addresses.
Nic Neate commented
I think that the link for the workaround in the original idea above should be this one: https://docs.microsoft.com/en-gb/archive/blogs/mihansen/using-azure-traffic-manager-for-private-endpoint-failover-automation. That describes a way to use a Function App to monitor a private endpoint, and reprogram your ATM profile to enable only endpoints that are currently available.
This really needs to be native Traffic Manager function though. We need to be able to configure connectivity from Traffic Manager to a private VNet in Azure, and probes to endpoints in private subnets in that VNet.
Richard Timmering commented
Windows Server 2016 DNS has the ability to do all of this and more. Running a B series VM with Windows server 2016 DNS or 2019 DNS is cheaper for 150k queries than a traffic manager profile. Just offering an alternative while waiting on the feature. https://docs.microsoft.com/en-us/windows-server/networking/dns/what-s-new-in-dns-server
Brian Nigl commented
Agreed. We have several customers with Azure footprints in the US and EU regions, and application spanning regions. Having an internal traffic manager supporting geographic affinity would be ideal, especially when our customers view the need for EU user traffic to remain in the EU.