Microsoft Account help and reporting
Use the appropriate personal or work-account recovery route.
Live Domain Check
Run a live reachability check for account.microsoft.com. Compare the regional responses with the problem you see in Microsoft Account.
Find Microsoft Account help and reporting links, specific checks, and step-by-step guidance below the live result.
Checking reachability from multiple regions.
Personal Microsoft Account sign-in is different from work/school identity and Microsoft 365 service health.
The checker above requests account.microsoft.com from eight configured locations and shows the responses and measurement times. Compare those observations with the actual Microsoft Account 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 Entra status check, Microsoft 365 status check, Outlook status check. Compare results separately; these links do not establish a shared outage.
Looking for another service? Browse work app checks.
Use the appropriate personal or work-account recovery route.
Open the website in your browser and compare it with the result above. This link opens the service, not its status page.
We have not linked a separate status page for this service. Check the official help page for current notices.
Open Microsoft Account help / reporting. Use the contact, technical-help or account route described there. Sign-in, support entitlement and available channels can vary; a public community discussion is not a private support ticket.
Account type, sign-in page, device/browser, error code and time; never share recovery or verification codes.
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 Account.
These are troubleshooting comparisons, not claims that Microsoft Account is currently experiencing a particular incident.
Record whether the account is personal or organisational and which sign-in or verification step fails.
Use the matching official recovery/support route and retain an existing signed-in session where possible.
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.
Use these local troubleshooting steps after the down-check workflow when Microsoft Account seems broken only for you. This section focuses on app, browser, account, and network fixes.
Open account.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.
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 Account issue.
If possible, compare Wi-Fi with mobile data and note which one fails. Leave any required work VPN or security settings in place.
Save timestamp, device, network type, exact error, final URL, and status code. Use the check workflow above before contacting Microsoft Account support.
Run the account.microsoft.com check and compare its original timestamps and responses with your actual error. Personal Microsoft Account sign-in is different from work/school identity and Microsoft 365 service health.
Use the official help/reporting resource linked above. Use the appropriate personal or work-account recovery route.
Record whether the account is personal or organisational and which sign-in or verification step fails. Use the matching official recovery/support route and retain an existing signed-in session where possible.
Account type, sign-in page, device/browser, error code and time; never share recovery or verification codes.