***EDIT***
The issue was that you have to point your CNAME to the TrafficManager and not to the API Management Url. Also, it appears that you can't do load-balanced development portals (maybe unless you use Premium) since when you try and manage that portal in azure
it redirects you to the load-balanced admin page and you can't know which one you are editing unless you take the others out of the traffic manager. If you try and go to the azure url manually it will give cert errors in Chrome that you can't get passed
(IE could but it won't let you login as an admin). You can mark this closed. Thanks!
Original Post:
I am having an issue where the TrafficManager isn’’t working, even though both endpoints are showing green:
myapi-dev.trafficmanager.net
It should redirect to these two endpoints:
mysitewest.portal.azure-api.net
mysiteeast.portal.azure-api.net
When trying to go to http(s)://yourapidomain-dev.trafficmanager.net it gives a 503 error saying “Service Unavailable”, but if you go to the endpoint links individually they work.
Here are the Powershell commands used to manually add the API Management resources to the TrafficManager (since only web and cloud apps are supported in the UI portal):
Add-AzureTrafficManagerEndpoint -TrafficManagerProfile $TrafficManagerProfile -DomainName "targetbaseapideveast.portal.azure-api.net" -Type "Any" -Status "Enabled" -Location "East US" | Set-AzureTrafficManagerProfile
Add-AzureTrafficManagerEndpoint -TrafficManagerProfile $TrafficManagerProfile -DomainName targetbaseapidevwest.portal.azure-api.net -Type "Any" -Status "Enabled" -Location "West US" | Set-AzureTrafficManagerProfile
Thank you!