Outlook refusing to connect to your email server is one of the most productivity-killing IT problems in a business environment. Whether it is stuck on “Trying to connect…”, showing a red disconnected status bar, or throwing authentication prompts in a loop, the fix is usually one of a handful of well-known issues. This guide covers both Microsoft 365 (Exchange Online) and on-premises Exchange Server scenarios.
Step 1: Check Whether the Problem Is Outlook or the Server
Before touching Outlook, verify the server is actually reachable:
- For Microsoft 365: check status.office365.com or the Microsoft 365 admin centre Service Health dashboard for any active incidents. Microsoft 365 outages are not uncommon and can affect thousands of tenants simultaneously.
- For on-premises Exchange: try accessing Outlook Web App (OWA) via a browser using your Exchange server’s URL. If OWA works but Outlook does not, the problem is client-side. If OWA also fails, the issue is server-side.
- Ask a colleague if their Outlook is working. If everyone is affected, it is a server or network issue.
Step 2: Restart Outlook in Safe Mode
Hold Ctrl while clicking the Outlook icon (or run outlook.exe /safe from Run). Safe mode disables all add-ins. If Outlook connects successfully in safe mode, a faulty add-in is the culprit. To identify it, go to File → Options → Add-ins, set the dropdown to COM Add-ins, click Go, and disable them one by one until the problematic one is found.
Step 3: Clear the Outlook Credential Cache
Stale or corrupted saved credentials are a very common cause of Outlook authentication loops, particularly after a password change or MFA policy update. Open Credential Manager (search in the Start menu), go to Windows Credentials, and remove all entries that contain MicrosoftOffice, outlook, mso, or your Exchange server address. Restart Outlook and enter fresh credentials when prompted.
If you have recently changed your Microsoft 365 password, also sign out of and back into the Microsoft 365 Sign-in Status shown in the bottom-right of the Outlook status bar, or via File → Office Account → Sign Out.
Step 4: Rebuild the Outlook Profile
A corrupted Outlook profile can cause persistent connectivity failures that no amount of credential clearing or add-in disabling will fix. To create a fresh profile:
- Close Outlook and open Control Panel → Mail → Show Profiles
- Click Add, name the new profile, and follow the setup wizard to add your email account
- Set the new profile as the default and relaunch Outlook
Your emails are stored on the server (or in a local OST/PST file), so creating a new profile does not delete any data — it simply recreates the local configuration Outlook uses to connect.
Step 5: Check Autodiscover
Outlook relies on the Autodiscover service to automatically find the correct server settings. If Autodiscover is misconfigured or unreachable, Outlook may connect partially or not at all. To test Autodiscover in Outlook, hold Ctrl, right-click the Outlook icon in the system tray, and select Test E-mail AutoConfiguration. Enter your email address, click Test, and check the results tab for errors.
For Microsoft 365, Autodiscover should resolve to autodiscover.outlook.com. If it is resolving to an on-premises server that no longer exists or has incorrect DNS records, that will cause connection failures that look like an Outlook bug but are actually a DNS or hybrid configuration issue.
Step 6: Repair the Office Installation
If nothing else resolves the issue, the Outlook installation itself may be corrupted. Go to Settings → Apps → Installed Apps, find Microsoft 365 or Office, click the three-dot menu, and select Modify. Choose Quick Repair first — it does not need an internet connection and takes a few minutes. If that does not resolve the issue, run Online Repair, which performs a full reinstall while preserving your profile and data.
On-Premises Exchange: Additional Checks
For clients running on-premises Exchange Server, connectivity failures may also stem from:
- An expired SSL certificate on the Exchange server (Outlook will refuse to connect)
- The Exchange services (Microsoft Exchange Transport, Information Store, RPC Client Access) having stopped or crashed — check Services in the Exchange server’s management console
- A full Exchange transaction log drive causing the information store to dismount
- Firewall rules blocking RPC or HTTPS traffic between clients and the Exchange server
If your Exchange server is on-premises and Outlook issues are recurring, it may be worth evaluating a migration to Exchange Online as part of a Microsoft 365 adoption. Speak to BIT Tech about migration planning and ongoing Exchange management.
