Recently we've been experiencing issues adding domain bindings to our app services that are hosted behind traffic manager.
Key Takeaways
- Azure seriously struggles and often fails to attach app service bindings to the Traffic Manager instance that they sit behind. This used to work fine, but recently started failing. When we configure geo-redundant app services, host them behind a Traffic Manager that uses Performance routing, and then try to assign SSL bindings to the Traffic Manager hostname using App Managed Certs the process almost always fails (and takes a long time to do so).
- To get Traffic Manager bindings you must use Priority routing in Traffic Manager and you'll only then be able to apply bindings to the instance that is the top priority. You must then cycle through each app service updating the bindings for each service when it's configured as the most prioritized route.
- Custom Domain names work fine. Bindings get applied just fine using TM Performance based route even with App Managed Certs. These certs all get deployed quickly without issue. This is the part that's a bit confusing and that Microsoft Support failed to explain.
