ADFS traffic manager profiles/endpoints/regions reflecting in degrading state though all ADFS/WAP services are in healthy state

Hi Shwetha J,

Welcome to Microsoft Q&A and thank you for posting your query here!

Thanks for the detailed breakdown—it's great that you've already validated key areas like SSL, probe responses, diagnostics, and host headers.

Even when ADFS/WAP services are healthy and manual probes return HTTP 200 OK, Azure Traffic Manager may still show endpoints as "Degraded" due to how it interprets probe responses. A few additional factors to consider:

Expected Status Code Ranges: Traffic Manager only considers an endpoint healthy if the probe receives a response within the configured expected status code range. If your application returns a redirect (e.g., 302) or any other code outside the default 200 range, it will be marked as degraded unless explicitly configured. You can update the Expected status code ranges in your Traffic Manager profile to include these codes if appropriate.

Probe Path Logic: If your probe path points to dynamic content (e.g., ASP pages), intermittent issues or logic errors could cause non-200 responses. Microsoft recommends using a dedicated probe endpoint like /Probe.aspx that includes logic to verify application health (e.g., checking database connectivity or session state). More on this in Troubleshooting degraded state on Azure Traffic Manager.

Traffic Manager Behavior with All Endpoints Degraded: If all endpoints in a profile are marked as degraded, Traffic Manager will still route traffic to all endpoints to avoid a complete outage. This explains why users in some regions can still sign in successfully despite the degraded status.

If you've already validated the probe responses and configuration, I recommend reviewing the probe path and expected status codes. Also, consider enabling resource logs for deeper diagnostics.

i hope the above response helps, if not please do me know if you have any questions on this!

thanks,

Harish.