Azure Traffic Manager API always returns "CheckingEndpoint" for groups

Hi Andres Moreno,

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

When the Azure Traffic Manager API continually returns EndpointMonitorStatus: "CheckingEndpoint" for one or more endpoints, it usually means the system is waiting for the results of its initial health probes. This status should be temporary and generally occurs just after endpoints are added or enabled in a Traffic Manager profile. However, if you are seeing this persistently for about 10 days, here are the steps and considerations for troubleshooting based on Microsoft documentation:

Step-by-Step Troubleshooting

1.Verify Endpoint Status and Monitoring Configuration

• Confirm the endpoint is enabled and correctly configured for monitoring (HTTP, HTTPS, or TCP).
• Check that your health probe settings (path, port, protocol) are accurate. For HTTP/S, Microsoft recommends using a dedicated health check page (e.g., /health.aspx), which should return an expected status code.​
• Reference: Azure Traffic Manager endpoint monitoring details

2.Understand the Meaning of 'CheckingEndpoint'

• "CheckingEndpoint" means Azure Traffic Manager is still awaiting a healthy response from the endpoint’s health probes or hasn’t yet received the initial probe results after enabling or adding an endpoint.
• If it remains in this state for long periods, there may be issues preventing successful probe completion, such as network restrictions, firewalls, or misconfigured endpoint URLs.

3.Check Network Connectivity and Firewall Rules

• Ensure the endpoint is reachable from external Azure infrastructure. Firewalls, NSGs, or hybrid setups sometimes block Traffic Manager’s probes.
• Verify that your endpoint can respond to probes reliably and that there is no intermittent connectivity issue.​

4.Review Health Probe Logs and Diagnostic Data

• Enable diagnostic logging on the endpoint and review logs for probe requests and responses. Look for clues such as non-200 response codes, timeouts, or redirects (Traffic Manager treats redirects as failures by default unless otherwise configured).​
• Reference: Troubleshooting degraded status article.

5.Check Azure Service Health and Recent Outages

• Since your issue started during a period of Azure problems, check the Azure Service Health dashboard for related incidents. Sometimes, platform-wide outages can delay probe initialization or impact traffic routing.

6.Update or Recreate Endpoints

• If the problem persists after these checks, try disabling/enabling or updating the affected endpoints. Sometimes, re-creating the endpoint can resolve stuck monitoring states.

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

Thanks,

Harish.