Why Was Outlook Down? The November 2026 Microsoft Outage Explained in Plain English

Outlook was down because of a technical fault inside Microsoft, not a hack. Starting on Thursday 12 November 2026, at around 1pm US Eastern time (about 11:30pm in India), Microsoft's email system stopped working properly for people around the world, taking Outlook, Teams, SharePoint and Copilot with it. Microsoft says the problem was "introduced by an issue during an earlier network capacity upgrade", which left a large number of its servers failing their automatic health checks. It apologised, and it extended the time Outlook keeps trying to deliver delayed email to 48 hours. If your email is slow or missing, it will most likely arrive as Microsoft clears the backlog.

I'm Kunal Vohra, a security researcher and cybersecurity advisor who also works as a fractional CTO for startups. Here is what happened, in plain English, and what you should actually do about it.

What happened

On Thursday afternoon US time, people started reporting that Outlook would not load, emails would not send or arrive, and Teams calls failed. TechRadar counted more than 131,000 Outlook problem reports on Downdetector in the US at the peak, and reports from at least 74 countries. Other outlets counted fewer, but everyone agrees it was one of the biggest Microsoft outages in years.

It did not only affect Outlook. Microsoft's own incident notice named Exchange Online (the system behind Outlook email), Teams, SharePoint, Microsoft 365 Copilot and its Defender security product. News outlets reported knock-on problems for airlines including IndiGo, Akasa Air and Air India, for UK council and government services, and for apps that connect to Microsoft 365, including tools from Anthropic and OpenAI.

By Friday evening (UTC), more than 27 hours in, Microsoft said access was coming back but email delivery was still catching up, and it did not yet have a time for full recovery.

Why it happened, in plain English

Big services like Outlook run on thousands of servers. Software constantly checks each server's health, and any server that looks unwell is taken out of service so it cannot hurt anyone. Usually that is a good thing.

On 12 November, Microsoft said, a large number of servers were suddenly "unavailable" and failing those health checks. With so many taken out at once, the remaining servers had to carry the load, and they struggled too. Microsoft said the extra load was not coming from more people using it, but from servers going missing.

On 13 November Microsoft gave the cause: the problem came from "an issue during an earlier network capacity upgrade", in other words work done earlier to expand its network. Microsoft paused all its software updates, restarted servers, rerouted traffic and built a new way of checking server health to get things moving again. It has promised a full report on what went wrong.

When a giant goes down, it is rarely one dramatic failure. It is usually one small change that a safety system then makes much bigger.

Was it a cyberattack?

No, according to Microsoft. Its status updates said it had no indication of malicious activity, and its 13 November statement said: "This was a technical issue not related to cyber or AI / agents." Some headlines were more cautious early on, which is normal while an incident is still under investigation, but Microsoft's position is clear.

Are my emails lost?

Probably not. Here is why.

Microsoft extended its delivery window. Microsoft extended Outlook's email timeout to 48 hours, which means it keeps trying to deliver delayed messages for longer than usual instead of giving up.

Email is built to retry. When a message cannot be delivered right away, the sending mail server normally keeps it in a queue and tries again later. That is why people reported old emails "trickling in" as service came back.

But check what matters. Microsoft has not said nothing was lost. If you were expecting something important (a contract, a payment confirmation, a one-time code), ask the sender to confirm or resend. One-time codes from the outage window have probably expired anyway, so just request a new one.

What you should do now

1. Restart Outlook and check again. Close and reopen the app, or try Outlook on the web. Some fixes reach the web version first.

2. Check Microsoft's official status. Microsoft posts updates on its service status page (status.cloud.microsoft) and on its Microsoft 365 Status account on X. If you are at work, your IT team can see detailed notices in the Microsoft 365 admin centre.

3. Resend anything important you sent during the outage. If you sent something time-sensitive on 12 or 13 November and have no reply, a quick "did this arrive?" message is worth it.

4. Do not reset your password just because of the outage. This was not a hack, and your password was not involved. Changing it will not fix anything.

5. Watch out for outage scams. This one matters most. After every big outage, scammers send emails and texts like "Your mailbox was affected, verify your account" or "Click here to restore your messages". Microsoft does not ask you to log in through a link to fix an outage. Do not click; go to Outlook directly instead. A newer trick asks you to type a code into a real Microsoft page, which hands an attacker your account without your password. I explained how that works in my post on device code phishing.

Will it happen again?

Yes, sooner or later, to every big provider. Microsoft, Google, Amazon and Cloudflare have all had large outages, and the bigger and more connected these services get, the more people notice when one stumbles. What usually follows is a published report and changes to stop that particular failure happening again.

For you, the practical step is small: know a second way to reach the people who matter (a phone number, a messaging app) if email is down for a day. If you run a business, it is worth more thought. I wrote a separate guide on what the Microsoft 365 outage teaches startups, with a one-afternoon checklist, and my startup security checklist covers the basics every small team should have.

Frequently asked questions

Why was Outlook down on 12 and 13 November 2026? Microsoft says an issue introduced during an earlier network capacity upgrade caused a large number of its servers to fail automatic health checks and go offline, which overloaded the rest. It was not a cyberattack.

Is Outlook working now? Microsoft reported service access recovering on 13 November, with email delivery still catching up and no time for full recovery at that point. Check Microsoft's service status page for the latest.

Was my account hacked? No. Microsoft says the outage was a technical fault with no sign of malicious activity. You do not need to change your password because of it, but be careful with emails that use the outage as an excuse to ask you to log in.

Will I get my missing emails? Most likely. Microsoft extended its email delivery window to 48 hours, and delayed messages were reported arriving as service recovered. For anything important, ask the sender to confirm.

Was Teams down too? Yes. Teams, SharePoint, Copilot and other services that depend on Microsoft's email system were also affected.

Will Microsoft explain what went wrong? Microsoft has said it will publish a full post-incident report once its review is complete. No date has been given.

If you run a team and want help making sure the next outage is an inconvenience rather than a crisis, book a 30-minute call or get in touch.

Sources

• Massive Microsoft 365 outage disrupts Outlook, Teams, Copilot worldwide (BleepingComputer)
• Microsoft's massive M365 outage stretches past 27 hours as its fixes keep failing (The Register)
• Microsoft outage live: Outlook and Teams returning to normal levels (TechRadar)
• Microsoft explains what caused global outage (KPTV)
• Microsoft apologizes after major Outlook outage worldwide (Fox Business)
• Microsoft apologises for outage and reveals cause (Forbes)