Outlook Disconnected from Server: Why It Happens and How to Get Back Online (2026 Updated Guide)
Quick answer
When Outlook shows “Disconnected” or “Trying to connect” in the bottom status bar, it has lost its connection to the mail server. Nine times out of ten the cause is one of four things: Work Offline mode is on, the device’s internet connection has dropped, an authentication token has expired, or the OST file has corrupted. Check Work Offline first (one click), then verify your network, then sign out and back in. If those don’t fix it, the issue is the profile or a Microsoft 365 service incident — and we’ll show you which is which.
Before you start
- Confirm the symptom. Look at the bottom-right of Outlook. If it says Disconnected, Trying to connect, or Working Offline, you’re in the right place. If it says Connected but mail isn’t arriving, that’s a different problem — usually a sync delay or a rule.
- Check whether webmail works (
outlook.office.comfor work accounts,outlook.live.comfor personal). If webmail works, the connection between Outlook and the server is the problem, not the server. If webmail also fails, escalate to your provider — there’s nothing useful you can do on the device. - Don’t restart your computer first. It often works, but it skips the diagnostic step. Knowing why Outlook disconnected is more useful than randomly restarting until it reconnects, because the cause tends to repeat.
What this means
Outlook maintains a continuous connection to the mail server while it’s running. Email arrives in real time because the server pushes new messages down the open channel. When Outlook can’t maintain that channel — for any reason — it stops trying and reports Disconnected in the status bar.
The status bar message itself doesn’t tell you why. That’s why the standard advice (“restart Outlook, restart your computer, check your internet”) works some of the time but never tells you what to do when it fails. The honest answer is: there are five distinct root causes, and you need to identify which one you have before you can fix it.
Where this error appears
| What you see | Likely cause |
|---|---|
| Bottom status bar says Working Offline | Work Offline mode is toggled on |
| Status bar says Disconnected, network is fine | Authentication token expired, profile issue, or Microsoft 365 service incident |
| Status bar says Trying to connect indefinitely | Network blocking the server, VPN issue, or DNS problem |
| Disconnected only on one device, fine on phone/web | Local profile or OST corruption |
| Disconnected at the same time across multiple devices | Microsoft 365 service incident — check the Service Health dashboard |
| Started after a recent Windows or Office update | Update broke the modern auth handshake; rare but documented |
Common causes
The five real causes, in roughly the order of frequency:
- Work Offline is toggled on. A single click on the Send/Receive → Work Offline button on the ribbon will toggle it. Easy to enable accidentally. Costs nothing to check first.
- Network connectivity has dropped or degraded. Wi-Fi is on but the router has lost its uplink, VPN has disconnected, or the device has switched to a captive-portal Wi-Fi network where authentication hasn’t completed.
- Authentication token has expired. Modern auth tokens (the way Microsoft 365 authenticates you) expire periodically and refresh transparently — except when they don’t. A failed refresh produces silent disconnection.
- Microsoft 365 service incident. Genuine outages affecting Outlook clients happen — check
status.office.comorportal.office.com/servicestatusif you have admin access. If it’s an incident, no fix on your end will help. - OST file corruption. The local data file has corrupted in a way that prevents synchronization. Less common but still real.
- Cached Exchange Mode misconfiguration. A specific edge case: cached mode enabled with a damaged offline cache or insufficient disk space can cause repeating disconnection.
Fixes to try first
1. Check Work Offline
This is the cheapest, fastest, and most embarrassing-to-skip step.
In classic Outlook, go to the Send/Receive tab on the ribbon. Look at the Work Offline button on the right. If it’s highlighted (toggled on), click it once to turn it off. Outlook will reconnect.
In new Outlook for Windows, this control is hidden — open settings (gear icon at top right), search for “offline,” and toggle the offline mode setting if it’s enabled.
Restart Outlook after toggling. The status bar should change to Connected within a few seconds.
2. Verify your network is actually working
Open a browser and load microsoft.com. If that works, the device is online. If it doesn’t, fix the network first — Outlook can’t connect to a server you can’t reach.
If you’re on a corporate network, check whether you’re connected to the VPN. Many M365 tenants are configured so that Outlook can reach the server outside the VPN but some features (autodiscover, address book lookup) require it. Reconnect VPN and re-check.
3. Sign out and sign back in
In classic Outlook, this is File → Office Account → Sign Out at the top right, then sign back in with your work or school account. In new Outlook, click your profile picture top-right, sign out, and sign in again.
This forces a fresh authentication token. About 30% of “stuck disconnected” cases resolve at this step alone.
4. Check Microsoft 365 service health
If you have access to the Microsoft 365 admin center, go to Health → Service health and look for any active Exchange Online incidents. If you don’t have admin access, ask whoever does, or check downdetector.com for general crowdsourced outage signals.
If there’s an active incident, stop. Wait it out. Microsoft will resolve it; you can’t.
5. Restart Outlook properly
Not “close the window” — that often just minimizes Outlook to the system tray. Right-click the Outlook icon in the system tray and click Exit, or use Task Manager to confirm OUTLOOK.EXE has fully terminated. Then restart it.
If that doesn’t help, restart the device. Yes, the cliché works occasionally — for token-cache issues that won’t otherwise clear.
Advanced fixes
If the basic triage hasn’t fixed it, the cause is one of three things: profile, OST, or modern-auth state.
Run Outlook in safe mode
Press Windows + R, type outlook.exe /safe, press Enter. Outlook starts with no add-ins loaded. If it connects in safe mode, an add-in is interfering — disable add-ins one at a time (File → Options → Add-ins) until the offender is identified. Recently-installed add-ins are the most common culprit.
Disable Cached Exchange Mode temporarily
In classic Outlook, go to File → Account Settings → Account Settings, double-click your Exchange/M365 account, and uncheck Use Cached Exchange Mode. Restart Outlook. If it connects without cached mode, the OST file or local cache is the problem — re-enable cached mode but force a fresh OST (next step).
Force a fresh OST
Close Outlook completely (verify in Task Manager). Navigate to your OST location:
C:\Users\<username>\AppData\Local\Microsoft\Outlook\Rename your .ost file (e.g., name@example.com.ost becomes name@example.com.ost.bak). Reopen Outlook. A new OST will download from the server. This is non-destructive — your mail lives on the server, not in the OST.
The download can take 30 minutes to several hours depending on mailbox size. Don’t interrupt it.
Rebuild the Outlook profile
A clean profile is the surgical fix for stuck-disconnected cases that survive everything else.
Open Control Panel → Mail (Microsoft Outlook) → Show Profiles. Click Add, name it (e.g., “Outlook2”), set up your account fresh in the new profile, and set Outlook to use the new profile by default. Start Outlook.
If the new profile connects, the old profile was corrupted. Once you’ve confirmed the new profile is healthy, you can delete the old one.
Repair the Microsoft 365 installation
Last device-level resort before reinstalling. Settings → Apps → Installed apps, find Microsoft 365, Modify → Quick Repair. If that doesn’t help, Online Repair does the heavy lift — 30–60 minutes, internet required, preserves user data. Our repair Microsoft 365 guide covers the full sequence.
Disable IPv6 if your network is mixed-stack
A persistent edge case: on networks where IPv6 is partially deployed, Outlook can attempt IPv6 connections that hang while IPv4 would have worked. This is rare but documented. Open network adapter properties, uncheck Internet Protocol Version 6 (TCP/IPv6), save, and test. Re-enable it if it doesn’t help.
If you’re on a work or school device
The disconnection may be intentional. Some organizations enforce Conditional Access policies that block Outlook from reaching Microsoft 365 unless the device is compliant, the user is in a specific location, or multi-factor authentication has been completed in the last N hours. If conditional access is blocking you, you’ll typically see a different message (“You can’t access this resource right now”) — but in some configurations, the device just sits at Disconnected with no clear reason.
If you suspect this, escalate to your IT admin. Specifically ask: “Is there a conditional access policy that might be blocking Outlook for me right now?” An admin can answer that in two minutes by checking the sign-in logs in Entra ID.
There’s also a separate failure mode where new users haven’t been fully provisioned. The full admin diagnostic is in our new Microsoft 365 user can’t sign in guide.
When to stop
Stop and escalate if:
- You’ve worked through this list, the device is online, webmail works, the OST has been refreshed, the profile rebuilt, and Outlook still says Disconnected. At that point, the issue is on the server or account side and needs admin investigation.
- You see Outlook keeps asking for password or Outlook error 0x800CCC0E alongside the disconnection. Those are distinct problems with their own fix paths.
- The device is encrypted, managed, or part of a corporate environment, and the next step would be a profile rebuild or registry edit. Get the IT admin involved before changing anything that could trigger a recovery prompt or compliance failure.
- It’s been more than 90 minutes and you’re now trying random Reddit suggestions. Past that point, fresh eyes (or a clean device profile) is faster than another 30 minutes of cargo-cult fixes.
Related errors
- Outlook keeps asking for password — the authentication-loop variant
- Outlook error 0x800CCC0E — the explicit connection error code
- Outlook search not working — often related when indexing breaks alongside connectivity
Official references
- Microsoft Support: Outlook is offline or disconnected — how to fix it
- Microsoft 365 Service Health: status.office.com
- Microsoft Learn: Cached Exchange Mode in Outlook
FAQ
Why does Outlook keep saying “Trying to connect” forever?
The client is attempting to reach the server but the connection is timing out. Most often this means a network path is broken: VPN dropped, captive portal blocking traffic, ISP issue, or a corporate firewall blocking the M365 endpoints. Test by loading webmail in a browser. If webmail loads, the network is fine and the issue is local — restart Outlook in safe mode and check the OST. If webmail also fails, fix the network first.
My Outlook says “Disconnected” but my email is still receiving on my phone. What’s wrong?
The server is fine and the account is fine. The phone has a working connection to it. The desktop client has lost its connection — usually because of an expired token, a corrupted OST, or Work Offline mode. Start with the Work Offline check, then sign out and back in, then refresh the OST.
Does Outlook reconnect automatically when my internet comes back?
Usually yes, within 30–60 seconds of network restoration. If it doesn’t reconnect within two minutes of a restored network, the auth token has likely also expired. Sign out and sign back in to force a refresh.
I clicked Work Offline by accident and now nothing reconnects. What do I do?
Toggle Work Offline back off (same button, Send/Receive → Work Offline), then click Send/Receive All Folders on the same ribbon. If the status bar stays on Disconnected for more than a minute, restart Outlook. If it still won’t reconnect, sign out and back in.
Is “Disconnected” the same as Outlook 0x800CCC0E?
No. 0x800CCC0E is a specific connection error that almost always involves IMAP or POP — it’s a hard failure with an explicit code. Disconnected is a generic status message that covers any reason the client has stopped maintaining its connection, including authentication, network, and service-side causes. They overlap (a 0x800CCC0E can leave you Disconnected) but they aren’t the same thing. Work the 0x800CCC0E guide if the explicit error code is what you’re seeing.
Can a Microsoft 365 outage cause this for everyone in my company at once?
Yes, and it’s the easiest case to diagnose. If multiple users in your organization all show Disconnected at the same time, check Microsoft 365 service health. If there’s an active Exchange Online or Microsoft Authentication Service incident, the disconnection is a symptom, not something you can fix from the client. Wait for Microsoft to resolve it.