Sending, receiving, and organizing email in Outlook.com
Because Outlook fails across multiple devices on both Wi‑Fi and LTE, check Microsoft’s service status first; if Outlook shows no active incident, run Microsoft’s Sign-in Helper for an account-specific access problem.
1. Check for an Outlook.com service incident
Open Microsoft’s Outlook.com known-issues page and select the Service Health Status link. Microsoft directs users who cannot access Outlook.com to check that status first.^1^
- If Outlook is listed as affected: no device or network change will resolve it. Wait for the status to show that service has recovered, then try signing in again.
- If no incident is listed: continue below.
2. Determine whether the mailbox or the whole Microsoft account is affected
Try signing in to the Microsoft account dashboard rather than Outlook.
- Microsoft account dashboard also fails: use Microsoft’s Sign-in Helper. Enter the affected email address and follow the account-specific instructions it returns.^2^
- The dashboard works, but Outlook.com and every Outlook app fail: this points away from a general password or Internet problem and toward Outlook mailbox access. Do not repeatedly reset the password unless the Sign-in Helper directs you to do so.
Microsoft’s Outlook.com sign-in guidance also directs unresolved sign-in failures to the account troubleshooter.^3^
3. Escalate an Outlook-only failure
If service health is normal and the Sign-in Helper finds no account problem:
- On the Outlook.com sign-in support page, select the support option for users who cannot sign in.
- Report that the same mailbox fails:
- in Outlook.com and the Outlook app;
- on multiple devices;
- over both Wi‑Fi and LTE;
- while other applications connect normally.
- Include the exact error text, the approximate time it started, and whether the Microsoft account dashboard works.
These details let support distinguish an Outlook mailbox-access problem from a device, network, or general Microsoft-account failure. Since different devices and independent networks have already produced the same result, repeating router restarts or basic Wi‑Fi troubleshooting is unlikely to add useful information.
References