Microsoft Entra service status
Check whether the provider lists a problem with the feature you use. Look at the update time and any affected regions.
Live Domain Check
Is Microsoft Entra Down? Check entra.microsoft.com Status and Outages
Run a live reachability check for entra.microsoft.com. Compare the regional responses with the problem you see in Microsoft Entra.
Find Microsoft Entra help and reporting links, specific checks, and step-by-step guidance below the live result.
Ready
Running automatic check…
Checking reachability from multiple regions.
Checked
-
Verdict
-
Response Time
-
Final URL
-
Regional checks
Is Microsoft Entra working for you?
Share a quick update and see what other visitors are experiencing.
What’s happening? Choose one to send your report.
Loading community reports…
—problem reports
—working reports
Past 24 hours15-minute totals · current interval in progress
Most reported problems
No problems reported in this period.
Visitor reports are separate from our automated checks and don’t confirm an outage. How reports work · Privacy
Understanding Microsoft Entra connection and service problems
Microsoft Entra sign-in, directory administration and an individual enterprise application can fail independently.
The checker above requests entra.microsoft.com from eight configured locations and shows the responses and measurement times. Compare those observations with the actual Microsoft Entra action that failed. A homepage response alone cannot verify an account, app workflow or transaction.
Distinguish Microsoft account access from mail, storage and meetings using the relevant product check: Microsoft 365 status check, Outlook status check, OneDrive status check. Compare results separately; these links do not establish a shared outage.
Looking for another service? Browse infrastructure checks.
Microsoft Entra status information and official help
Microsoft Entra help and reporting
Use the organisation's authorised security/identity administrator and product support.
Open entra.microsoft.com
Open the website in your browser and compare it with the result above.
Where to report problems with Microsoft Entra
Open Microsoft Entra help / reporting. Use the provider's customer-service or account-help route for the affected product. Sign-in may be required for private account questions.
Details to include in your report
Tenant/app identifier, UTC time, sign-in error and correlation/request ID without tokens.
Attach the checker’s downloaded JSON if it helps show the hostname, regional responses and original timestamps. Describe what happened in your browser or app as well. A report sent to WebsiteDown.org is not automatically forwarded to Microsoft Entra.
What to check when Microsoft Entra is not working
These are troubleshooting comparisons, not claims that Microsoft Entra is currently experiencing a particular incident.
Start with the action that failed
Capture the sign-in error and correlation ID and identify the tenant and target app.
Narrow down the affected service
An authorised administrator should compare sign-in logs and service health before changing Conditional Access or federation settings.
Read the actual checker response
A 403 Forbidden or 429 Too Many Requests means the host answered but refused or limited that request. A timeout gives no HTTP response. Keep those outcomes separate and check the available-region count before treating the result as broad evidence.
How to check if Microsoft Entra is down
- Save the error. Note what you were doing and when it failed. Save unfinished work before refreshing.
- Run the entra.microsoft.com check. Look at the regional results and when they were checked. Checking again may return a cached result.
- Check for a service notice. Open Microsoft Entra status and check whether the named service and incident time fit your error.
- Try another browser or network. Use the specific checks above to narrow down the problem. If it continues, send the error and time through the official help link.
If Microsoft Entra Is Not Working Only For You, Start Here
Use these local troubleshooting steps after the down-check workflow when Microsoft Entra seems broken only for you. This section focuses on app, browser, account, and network fixes.
1. Compare browser sessions
Open entra.microsoft.com in your current browser, then test in a private window or second browser. If only one session fails, compare its account, cookie and extension context before assuming the entire service is unavailable.
2. Preserve a working account session
Keep an existing working session and preserve unsaved work. For a sign-in failure, use the official account-help route. Avoid repeated password or security resets until you confirm this is not a broader Microsoft Entra issue.
3. Try another network
If possible, compare Wi-Fi with mobile data and note which one fails. Leave any required work VPN or security settings in place.
4. Capture support-ready evidence
Save timestamp, device, network type, exact error, final URL, and status code. Use the check workflow above before contacting Microsoft Entra support.
Frequently asked questions about Microsoft Entra problems
Is Microsoft Entra down, or is the problem limited to one feature?
Run the entra.microsoft.com check and compare its original timestamps and responses with your actual error. Microsoft Entra sign-in, directory administration and an individual enterprise application can fail independently.
Where can I report a problem with Microsoft Entra?
Use the community buttons on this page to share whether the service works for you. For help from Microsoft Entra, use the official help/reporting resource linked above. Use the organisation's authorised security/identity administrator and product support.
What should I check first when Microsoft Entra is not working?
Capture the sign-in error and correlation ID and identify the tenant and target app. An authorised administrator should compare sign-in logs and service health before changing Conditional Access or federation settings.
What information helps Microsoft Entra support investigate?
Tenant/app identifier, UTC time, sign-in error and correlation/request ID without tokens.