THE CONNECTIONS BEHIND YOUR BUSINESS
Troubleshooting Outlook Connection Problems
Separate a mailbox or service problem from an Outlook app problem before changing profiles or credentials.
When Outlook will not connect, first separate a service or account problem from a device-specific issue. Start with read-only checks and preserve local mail before attempting repairs.
Start here: can you use Outlook on the web?
Open your organization’s known Microsoft 365 webmail address and sign in yourself. Do not follow an unfamiliar sign-in link supplied in an error message. Test a harmless external message and reply.
| What you find | Check next |
|---|---|
| Webmail and Outlook both fail | Service health, account access, licensing, mailbox capacity and delivery |
| Webmail works; one device fails | That device’s Outlook version, connection and account configuration |
| Only one recipient fails | Delivery error and recipient address, not the whole profile |
| Messages send but land in Junk | Authentication/content/reputation investigation, not a connection reset |
Record the exact error and time, without capturing passwords, tokens or private message contents.
1. Identify the Outlook version
New Outlook, classic Outlook for Windows, Outlook for Mac and mobile Outlook have different controls. Use the troubleshooting instructions for your version. Do not look for classic Outlook’s Work Offline switch in an application that does not offer it.
Check that the device has a working connection, accurate clock and supported updates. If permitted, compare another trusted connection to isolate a network problem. Do not disable security tools, certificate checks or organizational access controls to make sign-in succeed.
2. Check service and account status
An authorized Microsoft 365 administrator can review service health, mailbox/license status and relevant sign-in failures. A password prompt can reflect a policy or authentication problem, not necessarily a bad password.
Use the organization’s approved modern sign-in flow and MFA. Do not enable legacy authentication or create an app password as a generic fix. If access is blocked by policy, have the administrator investigate the specific reason.
3. Inspect local symptoms safely
In classic Outlook, check whether Work Offline is enabled and whether the status bar shows disconnected. Check Outbox for a stuck item and review mailbox storage. In other versions, follow their corresponding account and connection settings.
If only one mailbox or shared mailbox is affected, verify its permissions and configuration. Automatic discovery should use the organization’s supported setup; do not paste arbitrary server names from a search result.
4. Preserve local data before repairs
Restart and update the application before invasive changes. If a supported repair or new-profile test is needed, preserve the existing profile and local data first. POP accounts and PST archives may contain the only copy of some messages.
Do not delete a profile, OST/PST file or account merely because an online checklist says to start fresh. A replacement profile is a controlled diagnostic step, not proof that the original data is disposable.
5. Confirm recovery and escalate with evidence
Test sending, receiving, calendar access and any affected shared mailbox. A successful sign-in alone does not validate delivery. If the issue remains, provide the version, error, time, affected scope and whether webmail works to your administrator.
Keep message headers and diagnostic logs private and sanitized. Never send passwords or MFA codes to support. For mail-routing or authentication failures, use the related guides instead of repeatedly rebuilding Outlook.
Official references
- Microsoft: Issues Sending and Receiving Email
- Microsoft: Cannot Send or Receive in Outlook
- Microsoft: Outlook Connection Issues
Documentation checked 2026-10-18. Examples use reserved names and addresses; replace placeholders only for systems you are authorized to manage. Interfaces and included features depend on your provider and account.