Allow Traffic Manager to Support Absolute Monitoring Endpoints
Current endpoint monitoring in Traffic Manger only supports a relative path. For flexibility, it would be great to support a full url path like http://www.example.com/health
Traffic Manager constructs the probing URL by appending the endpoint FQDN with the relative path. So if the FQDN of your endpoint is example.com and a relative path is /index.html then the probing path would be example.com/index.html
You can also specify custom host header for each endpoint if required and set expected HTTP codes for the profile; in case the application does not return 200OK for the probes. Please see https://docs.microsoft.com/en-us/azure/traffic-manager/traffic-manager-monitoring
Could you elaborate on the scenario that would require absolute URLs for each endpoint?
Cameron Vetter commented
Yes, this... Between this limitation and the requirement of 200's (not allowing 300's), traffic manager is limited to a very narrow set of use cases.