Outlook Down? Microsoft 365 and Exchange Online Outage, November 2026: What Happened and What to Do

Reviewed by IT Cares technicians · Updated November 16, 2026

Laptop on an office desk with an abstract screen showing a cloud icon with a warning triangle and an empty inbox, illustrating an Outlook outage
If Outlook on the web fails too, the problem is probably not your computer.

Quick fix: 5 steps

  1. Check status.cloud.microsoft for an active incident.
  2. Open Outlook on the web (outlook.office.com or outlook.live.com).
  3. Web fails too: it is an outage. Wait and tell colleagues by phone or text.
  4. Web works but the app does not: close Outlook in Task Manager, then File, Office Account, Update Options, Update Now.
  5. Still stuck: Safe Mode (outlook.exe /safe), then Repair. Full steps.

Outlook down: what happened in the Microsoft 365 outage of November 12 to 13, 2026

If Outlook stopped sending or receiving email on Thursday, November 12, 2026, you were very likely caught in a large Microsoft 365 and Exchange Online outage, not a problem with your computer. According to SecurityWeek's reporting, the disruption began on Thursday, November 12 and ran into Friday, November 13. According to BleepingComputer, which cites Microsoft's preliminary post-incident report, the impact started at about 11:20 AM Eastern Time on November 12 and Microsoft confirmed it had ended at 11:10 AM Eastern Time on November 13.

This guide does two jobs. First, it explains what is publicly known about the outage and what is not yet confirmed, with every claim attributed. Second, and more important for the long run, it gives you a complete "Outlook is down, is it just me?" routine that works for any future outage and for ordinary local problems. If your Outlook is still misbehaving today, skip ahead to how to tell an outage from a problem on your PC.

What we know and what is not confirmed yet (as of November 16, 2026)

Reported by the sources we opened:

  • The outage began about 11:20 AM ET on Thursday, November 12, and Microsoft confirmed customer impact ended at 11:10 AM ET on Friday, November 13 (BleepingComputer, citing Microsoft's preliminary post-incident report).
  • Microsoft listed incident EX1550543 for Exchange Online and MO1550821 for the broader Microsoft 365 service in the admin center (SecurityWeek).
  • Affected services included Exchange Online and Outlook, Teams, Copilot, and, per SecurityWeek, possibly SharePoint Online and Defender XDR. Some Google Workspace users also reported Outlook access problems.
  • Microsoft said in a Friday update: "At this time, we have no evidence of malicious activity associated with this incident" (SecurityWeek).

Not confirmed or still changing:

  • The final post-incident report. BleepingComputer says it was expected later that week (we did not find it published as of November 16), so details may change.
  • Some news outlets reported that Microsoft extended the retry window for delayed email to 48 hours. We could not confirm that figure on a Microsoft page, so treat it as unverified.
  • Whether free consumer addresses (Outlook.com, Hotmail) were hit. Coverage conflicts, and the reports we read focus on business Microsoft 365 tenants.

A plain timeline, using only what the sources state

When (Eastern Time)What was reportedSource
Thursday Nov 12, about 11:20 AMOutage begins; people in the Americas first report trouble reaching Exchange Online mailboxesBleepingComputer, SecurityWeek
Thursday afternoon (just before 3 PM)Incidents EX1550543 and MO1550821 visible as service degradations in the Microsoft 365 admin center; Microsoft later flags possible impact to Teams, SharePoint Online, Copilot and Defender XDRSecurityWeek
Thursday, about 9:00 PMRestarting affected servers shows signs of improvement, but full recovery is not confirmedSecurityWeek
Friday Nov 13Microsoft deploys a fix and services stabilize; no evidence of malicious activityBleepingComputer, SecurityWeek
Friday Nov 13, 11:10 AMMicrosoft confirms customer impact has endedBleepingComputer

Note one thing about the timing: the outage came two days after Microsoft's November Patch Tuesday. That is a coincidence of dates, not a cause. Microsoft's own account points to a networking gateway bug, not to the Windows updates. If you are also seeing update installation errors on your PC, that is a separate story, covered in our November 2026 Patch Tuesday known issues guide.

Who was affected and how it looked

For most people the symptoms were the same whatever the app: Outlook on Windows or Mac stuck on "Trying to connect" or "Disconnected", Outlook on the web (OWA) showing errors or an endless spinner, phones not syncing mail, and messages sent to affected mailboxes arriving hours late. Calendar-dependent features such as scheduling a Teams meeting from Outlook were also reported broken. Because the failure sat in Microsoft's network layer rather than in your device, nothing you did locally could fix it: reinstalling Outlook, rebuilding the profile or rebooting the router changed nothing, and some of those actions made life harder once the service returned.

That last point is worth remembering. During an active incident, the right move is to confirm it is an incident, wait, and avoid destructive "fixes". We explain the safe order of checks below.

Why it happened: Microsoft's preliminary explanation

Microsoft's explanation has shifted as the incident moved from "investigating" to "post-incident report", so here are both stages, clearly separated.

During the outage (SecurityWeek, November 12 to 13)

Microsoft said traffic on its infrastructure rose because many servers had become unavailable, and that overall traffic had not increased. It said a process that establishes secure connections became overwhelmed, causing affected servers to stop handling requests. Engineers began rolling back a recent network configuration change that coincided with the start of the disruption, tested a workaround that bypasses the component handling health checks, and looked into elevated processor usage.

After the outage (BleepingComputer, citing the preliminary report)

Microsoft's preliminary post-incident report described three factors that combined:

  1. A software bug introduced in July in an update for the Microsoft 365 networking gateway servers, which could overwhelm servers under certain traffic conditions.
  2. Extra traffic after Microsoft Teams automatically failed over to the networking infrastructure used by Exchange Online, about 15 hours before the outage began.
  3. Reduced capacity, because nearly 14% of gateway server capacity was already offline because of an unrelated issue.

According to the same report, servers stopped responding within two hours and, at the low point, more than 80% of them were unresponsive. Traffic redirected to other servers overwhelmed those too. Safeguards meant to contain problems between regions failed, so the disruption spread worldwide, and restarting servers was hard because backed-up traffic overwhelmed them again. Microsoft said its load testing missed the bug because it ran on less powerful hardware than production, and the bug is worse on machines with more cores and newer hardware.

Microsoft also said Teams, OneDrive and SharePoint could switch to alternative infrastructure and recover earlier, while Exchange Online could not. That is why email was the hardest hit and the slowest to return. After the fix, Microsoft said it added capacity, improved monitoring and added safeguards so traffic redirection cannot cascade the same way. Charles Lamanna, an executive vice president at Microsoft, apologized publicly on X, writing "We are deeply sorry for the impact to all our customers." The final report is still pending, so expect details to be refined.

Was it a cyberattack?

Microsoft said it had no evidence of malicious activity linked to the incident. The outage is best understood as a software and capacity failure. That said, there is a separate and genuine security story from the same week: an Outlook spoofing flaw, CVE-2026-124194, which Microsoft's Security Update Guide lists as "Exploitation Detected" and CISA added to its Known Exploited Vulnerabilities catalog on November 10. We found nothing from Microsoft or CISA linking it to the outage, and it is a different kind of problem. Do not confuse the two. If you want a practical rule: keep Office updated (File, then Office Account, then Update Options, then Update Now) and be careful with unexpected message files, whatever the outage status is.

One more safety note. Every large outage produces a wave of scam messages that exploit the confusion: "your mailbox was suspended, click to restore", or a fake "Microsoft support" call offering to fix your email. Microsoft's own recovery guidance for accounts states that support agents cannot send password reset links, and the same caution applies here. Our guide on fake passkey prompts and Microsoft 365 phishing shows what the lures look like.

Person checking a smartphone beside a laptop in an office to see whether Outlook is down

Was my email lost? What happens to messages sent during an outage

This is the question that worries people most, and the answer for ordinary email is reassuring. Email is a store-and-forward system. When a sender's mail server cannot hand a message to your server, it does not throw the message away. It keeps it in a queue and retries, typically for days before giving up and sending the sender a "delivery failed" notice. Microsoft's own systems apply the same principle internally. Some outlets reported that Microsoft extended the timeout window to 48 hours so that messages would keep retrying; we could not verify that exact number on a Microsoft page, so the safe reading is: most messages sent during the outage should eventually have been delivered, but we cannot guarantee it for every case.

What can go wrong in practice:

If you are an administrator and a specific, important message is still missing, use message trace in the Exchange admin center to see what happened to it. If you are a regular user, ask the sender to resend and check your Junk folder too.

Outlook down or is it just me? A 5-minute test that works every time

This is the part of the page that stays useful long after the November 2026 incident. The goal is to decide, in a few minutes and without changing anything, whether the problem is Microsoft's side, your account, your network or your Outlook app. Work through the tests in this order, because each one rules out a whole category.

Test 1: Check Microsoft's own status (30 seconds)

Open the Microsoft 365 service status page (status.cloud.microsoft) and, if you are an administrator, the Service health page in the Microsoft 365 admin center. Incidents have IDs that start with letters such as EX for Exchange Online or MO for Microsoft 365 broadly, as in the November 2026 case. The official @MSFT365Status account on X also posts updates. Be aware that the public status page can lag behind reality in the first hour of an incident, so a green page does not prove you are fine. It only means Microsoft has not flagged a problem yet.

Test 2: Try Outlook on the web (1 minute)

In a browser, go to outlook.office.com (work or school account) or outlook.live.com (personal Outlook.com, Hotmail and Live addresses) and sign in. This test is the most valuable one, because it bypasses your installed app and your Outlook profile entirely.

ResultWhat it most likely meansNext step
Web works, app does notProblem is local: app, profile, add-in, cache or network settingGo to the local fixes
Web also fails with errors or a spinnerLikely a Microsoft-side incident, or a network blockTest 3, then wait
Web asks for password repeatedly or says account lockedAccount or sign-in problem, not an outageReset password; see Outlook account hacked recovery if you suspect a takeover
Web works on phone data but not on Wi-FiYour router, DNS or a firewallRestart the router, try another network

Test 3: Compare devices and networks (2 minutes)

Try the same account on your phone using mobile data with Wi-Fi turned off, and on a colleague's computer if you are at work. If several people on different networks all fail at once, it is almost certainly the service. If only your computer fails, it is local. During the November 12 incident, outages hit users in many countries at the same time, which is the classic multi-user pattern.

Test 4: Ask the crowd (30 seconds)

Search "Outlook down" on a social network, or open an outage-tracking site such as Downdetector. A sharp spike in reports in the last hour is a strong signal. SecurityWeek and other outlets reported very large report counts in the November incident. Crowd data is noisy and can lag, so use it to confirm, not to rule out.

The decision rule

  1. Status page shows an incident, or web access fails for you and others: it is an outage. Wait, do not rebuild anything, and check back every 30 to 60 minutes.
  2. Web works but the app fails: it is local. Use the fixes below.
  3. Web works and the app works but one mailbox or one message is wrong: it is a delivery, rule or account issue, covered in the FAQ.

What to do while Microsoft fixes it: the "do not" list

When you confirm an outage, a few actions help and a few hurt.

Do:

Do not:

For businesses, the Microsoft 365 admin center is the authoritative place to read incident updates and, in some cases, the expected resolution time. If you manage a small team and want the incident explained in plain language, our Microsoft 365 services in Canada page describes how we support it.

Illustration of a cloud connected to server blocks with several dimmed and one amber warning light, representing a Microsoft 365 outage

Outlook still not working after the outage? Local fixes in order of likelihood

If Outlook on the web works but your desktop Outlook still shows "Disconnected", "Trying to connect", a password prompt loop or missing mail, the incident is over for you and what remains is a local problem, often triggered by the outage itself (a stale connection, a cache that did not recover, or an old build). Work through these in order. They are standard Microsoft-supported steps, not tricks. Our broader guide to Outlook not working covers further cases.

Fix 1: Check that Outlook is not working offline

In classic Outlook, open the Send/Receive tab and look at the Work Offline button. If it is highlighted, click it to turn offline mode off. Also look at the status bar at the bottom: "Working Offline", "Disconnected" or "Trying to connect" tells you where it is stuck. To see more detail, hold Ctrl and right-click the Outlook icon in the system tray near the clock, then choose Connection Status. A server line showing "Established" is good. "Disconnected" or repeated failures means it still cannot reach Exchange.

Fix 2: Close Outlook fully and reopen

Closing the window is not always enough. Press Ctrl+Shift+Esc to open Task Manager, find Microsoft Outlook (or OUTLOOK.EXE) under Processes, choose End task, then start Outlook again. For the new Outlook the process is olk.exe. This clears a stuck connection left from the outage.

Fix 3: Update Office

Old builds are a frequent cause of Outlook refusing to connect or crashing. In any Office app go to File, then Office Account, then Update Options, then Update Now. This is also the route that installs the Office-side security fix for the Outlook flaw mentioned earlier, which Windows Update alone does not provide, according to reporting we reviewed. Restart Outlook when it finishes.

Fix 4: Start Outlook in Safe Mode

Hold the Ctrl key while you click the Outlook icon and choose Yes when asked about Safe Mode, or press Windows+R and type outlook.exe /safe. Safe Mode disables add-ins. If Outlook now connects and behaves, an add-in is the culprit. Go to File, then Options, then Add-ins, choose COM Add-ins from the Manage list, click Go, and untick add-ins one at a time (start with third-party ones, such as meeting or CRM tools). Reports on Microsoft's own Q&A forum mention older Outlook builds combined with the Teams Meeting add-in preventing Outlook from starting, with an Office update as the fix, but treat that as a community report, not a confirmed Microsoft bulletin.

Fix 5: Repair the account connection

In classic Outlook choose File, then Info, then Account Settings, then Account Settings, select your account and click Repair. Follow the prompts. If you are asked to sign in again, do so with your normal password and complete the multifactor prompt. If sign-in loops, remove saved credentials: open Control Panel, then Credential Manager, then Windows Credentials and remove entries whose names begin with MicrosoftOffice or contain your email address, then reopen Outlook and sign in once more.

Fix 6: Repair the Office installation

Open Settings, then Apps, then Installed apps, find Microsoft 365 (or Microsoft Office), choose Modify, then pick Quick Repair. If that does not help, run Online Repair, which takes longer and needs internet, but replaces more files. For the new Outlook app, the path suggested by Microsoft Q&A community answers is Settings, then Apps, then Installed apps, then Outlook (new), then Advanced options, then Repair. If Repair does not help there, use Reset, which clears the app's local data, so make sure your mail is on the server first.

Fix 7: Create a new Outlook profile (last resort)

Only after the steps above. Close Outlook, open Control Panel, then Mail (Microsoft Outlook), then Show Profiles, click Add, name it, and enter your email. Set the new profile as the default and open Outlook. For an Exchange or Microsoft 365 mailbox your mail is on the server, so you lose little, but check beforehand that you have no local-only items. A PST file that you added manually is not lost by creating a profile, but you must add it back. If you have an old POP account that stores mail only on your computer, back up the PST first, because a profile change can orphan it.

Mac, mobile and web specifics

Three realistic scenarios

These are illustrative examples, not real client cases. The numbers are invented to show how the decision rule plays out.

Scenario 1: The 8-person accounting office (outage)

At 11:40 on Thursday, three employees say Outlook is "Disconnected". The office manager runs Test 2: Outlook on the web shows an error for her and for two colleagues, on both office Wi-Fi and a phone on mobile data. She checks status.cloud.microsoft and the admin center, sees the Exchange Online incident, and stops. She sends a group text: "Email is down at Microsoft, use phone for urgent client matters". Nobody rebuilds a profile. On Friday afternoon everything reconnects and Outbox items send on their own. Total lost time: a few hours of waiting, not days of cleanup.

Scenario 2: The freelancer whose web works but app does not (local)

A freelance designer sees a green status page on Friday evening. Outlook on the web works. The desktop app still says "Trying to connect". Following the order above, she closes Outlook in Task Manager (no change), runs Update Now (finds a pending update, installs it) and Outlook connects. Fix 2 and Fix 3 together took about 12 minutes. If those had failed, Safe Mode and Repair were next.

Scenario 3: The retailer with a missing supplier email (delivery)

A shop owner expected a supplier's price list on Thursday afternoon and nothing arrived. By Monday it is still missing, although other mail has returned. She checks Junk and a Sent Items search, then asks the supplier to resend. The supplier's system had bounced the message after its own retry window ran out, an example of why a resend request is the fastest fix for individual missing messages. She also asks her IT provider to run a message trace for any remaining gaps.

Outlook down checklist (copy and keep)

Outage vs local problem checklist

  • ☐ Checked status.cloud.microsoft (and the admin center if I am an admin)
  • ☐ Tried Outlook on the web (outlook.office.com or outlook.live.com)
  • ☐ Tried my phone on mobile data, Wi-Fi off
  • ☐ Asked a colleague whether they are affected
  • ☐ Notified key contacts by phone or text
  • ☐ Did NOT delete my profile, reinstall Office or reset my password
  • ☐ If web works: closed Outlook in Task Manager and reopened
  • ☐ Ran Update Now (File, Office Account, Update Options)
  • ☐ Tried Safe Mode and disabled add-ins one by one
  • ☐ Ran Quick Repair, then Online Repair if needed
  • ☐ Checked the Outbox and Junk folder for stuck or misfiled mail
  • ☐ Asked senders of missing important messages to resend
Desk with laptop, handwritten troubleshooting checklist, pencil, mug and a small wrench

Outage, account problem or local fault: how to tell them apart

SignMicrosoft outageYour accountYour PC or app
Web versionFails or errorsAsks for password or says lockedWorks
Other peopleMany affected at onceOnly youOnly you
Status page / admin centerIncident listed (may lag)No incidentNo incident
Typical message"Disconnected", server errors"Need password", "account locked""Not responding", add-in errors
Best responseWait, communicate, avoid rebuildsReset password, review sign-in activityUpdate, Safe Mode, Repair

What it costs: doing it yourself versus paying a technician (CAD)

For a normal outage the cost of fixing is zero, because there is nothing to fix on your side, and the real cost is lost productivity. Doing the local steps yourself is also free: the status checks, Safe Mode, Update Now and Repair cost only your time, usually 20 to 45 minutes for a first-timer. Paying a technician makes sense when the same problem returns, when several staff are affected, or when you are not sure whether anything is at risk. At IT Cares, our single Expert Consultation is 119.99$ CAD for up to 60 minutes of remote support, which is usually enough to trace why one machine will not reconnect, repair a profile and verify that mail flows. Compare that with the cost of a day of missed email for a small team, and you can decide whether it is worth it. For businesses that depend on email, the better investment is a short continuity plan: a second communication channel, a documented status-check routine, and a person who knows how to run message trace.

Make the next outage a non-event: a small business continuity plan

  1. Name an owner. One person checks the status page and decides "outage or local" so ten people do not each try ten different fixes.
  2. Have a second channel. A group chat on a different platform, a shared phone list, and an auto-reply template ready to switch on.
  3. Keep Office updated. Use Update Now monthly, or automatic updates.
  4. Know your admin access. Make sure at least two people can open the Microsoft 365 admin center, with multifactor authentication set up. Microsoft is moving away from SMS codes, so read our note on the end of SMS MFA and passkeys.
  5. Back up your data. An outage is not data loss, but a bad day makes you realize that mail, files and calendars live in one place. See why OneDrive sync is not a backup.
  6. Choose secure email setups. Our guide to secure business email on Microsoft 365 and Google Workspace covers tenant settings worth reviewing.

Official resources

When to call a pro

Most outage days need patience, not a technician. Consider calling in help when:

IT Cares has provided remote support, and on-site help across Quebec, since 2014. Call 1 (888) 711-9428 or use our Outlook and email support page. We connect remotely, show you what is wrong and fix it while you watch. Google rating: 4.9 stars from 78 reviews.

Last verified: November 16, 2026. This page will be updated when Microsoft publishes its final post-incident report.

Still stuck? Get a technician on it now

Remote support from IT Cares: we connect to your device, fix it with you watching, and explain what happened.

Frequently asked questions

Is Outlook down right now?
Check status.cloud.microsoft, then try Outlook on the web (outlook.office.com or outlook.live.com). If the web version also fails and others report the same, it is likely a Microsoft-side incident. If the web works, the problem is on your device or app. The large November 12 to 13, 2026 outage ended at 11:10 AM ET on November 13, according to BleepingComputer citing Microsoft.
What caused the Microsoft 365 outage in November 2026?
According to Microsoft's preliminary post-incident report as reported by BleepingComputer, a software bug introduced in July in an update to Microsoft 365 networking gateway servers combined with extra traffic after a Teams failover and about 14% of gateway capacity already offline. The final report was still pending when we last checked.
Was the outage a cyberattack?
Microsoft said in a Friday update that it had no evidence of malicious activity associated with the incident, according to SecurityWeek. A separate Outlook spoofing flaw, CVE-2026-124194, confirmed on Microsoft's Security Update Guide and in CISA's KEV catalog, was disclosed the same week; we found nothing linking it to the outage.
Did I lose emails sent during the outage?
Normally no. Email is queued and retried by the sender's server. Some outlets reported Microsoft extended the retry window to 48 hours, but we could not verify that on a Microsoft page. If an important message is missing, ask the sender to resend, check Junk, and ask an administrator to run a message trace.
Why does Outlook still say Disconnected after the outage ended?
A connection can get stuck after a long incident. Close Outlook in Task Manager and reopen it, turn off Work Offline on the Send/Receive tab, run Update Now, then try Safe Mode and Repair. If Outlook on the web works, the problem is local.
Should I delete my Outlook profile or reinstall Office during an outage?
No. While the service is down it will not help, and you can lose cached data or create new problems. Confirm an outage first, wait, and only use local fixes if the web version works and the app does not.
How do I check Microsoft 365 status as a regular user?
Open status.cloud.microsoft for the public status page, follow @MSFT365Status on X, and test Outlook on the web. Remember that the public page can lag behind reality early in an incident. Administrators can read incident IDs and updates in the Microsoft 365 admin center under Service health.
What do incident codes like EX1550543 and MO1550821 mean?
They are Microsoft service incident IDs shown in the admin center. SecurityWeek reported EX1550543 for Exchange Online and MO1550821 for the broader Microsoft 365 service during the November 2026 outage. Prefixes such as EX and MO usually identify the service area.
Were Outlook.com and Hotmail accounts affected?
Reports conflict. Several outlets focused on business Microsoft 365 and Exchange Online, and some said consumer addresses were also named. We could not confirm it on a Microsoft page, so check outlook.live.com and the status page for your own account.
Was Teams affected as well?
Yes. SecurityWeek reported Microsoft flagged possible disruption to Teams, and calendar and meeting scheduling problems were widely reported. BleepingComputer, citing Microsoft's report, says Teams, OneDrive and SharePoint could switch to alternative infrastructure and recover earlier than Exchange Online.
Can scammers exploit an outage?
Yes. Expect fake messages saying your mailbox is suspended or that you must verify your account, and fake support calls. Do not click links or call numbers from a message. Microsoft says support agents cannot send password reset links for account recovery.
Do I need to update Office after this outage?
The outage itself did not require a patch on your device, but keeping Office current is good practice and the Outlook spoofing flaw reported the same week is fixed through Office updates, per the reports we reviewed. Use File, Office Account, Update Options, Update Now.
When should I call IT Cares?
If Outlook on the web works but your app still fails after update, Safe Mode and repair, if several staff are still affected after Microsoft says service is restored, or if you see signs of a hijacked account. Call 1 (888) 711-9428 for remote support.

Sources and official references

Last verified: November 16, 2026

Need Help?