We all know that moment on a Thursday afternoon when you hit refresh on Outlook, nothing loads, and you start blaming your Wi-Fi. Then your coworker says theirs is broken too. Then your friend in another city texts the same thing. Yeah, on 12 November that wasn’t your Wi-Fi. It was Microsoft, and it was pretty much everywhere.

A Microsoft 365 outage took down Outlook and hit Teams, Copilot, OneDrive and other workplace apps for users in more than 70 countries. By Friday, more than 18 hours after it started, Microsoft was still working to get everything back to normal.

Here is what happened, what Microsoft has said so far, and what you can do if your email is still acting weird.

When it started and how big it got

Microsoft’s first post on its Microsoft 365 Status account on X came at 12:54 p.m. ET on Thursday, according to HollywoodLife. It said: “We’re investigating reports of users experiencing issues accessing Exchange Online mailboxes through multiple connection methods in the Americas,” as quoted by ABC News.

That “in the Americas” part didn’t last long. Microsoft soon said the problem “may affect Microsoft 365 service connectivity for users in any region.”

The reports came in fast. On Downdetector, Outlook complaints peaked at just over 130,000, with Chicago, Seattle and New York among the hot spots, NBC Chicago reported. Microsoft 365 reports topped 45,000 at around the same time. These are self-reported numbers, so the real count of people hit is probably much higher.

By about 07:00 GMT on Friday, Downdetector still had at least 43,000 Outlook reports from users in 72 countries, according to Al Jazeera.

Which Microsoft services went down

Outlook took the worst of it. People couldn’t open their mailboxes on the web, in the app or on their phones, and a lot of the emails that did go through showed up late. If you use the Outlook desktop app, you could still see emails that had already downloaded, Al Jazeera noted, but new ones weren’t coming in.

The full list was longer. Microsoft named these services as affected under its main incident, MO1550821, according to Cybersecurity News and WindowsForum:

Service What users saw
Outlook / Exchange Online Mailboxes wouldn’t load, email delayed
Microsoft Teams Problems early on; chats and calls mostly kept working
SharePoint Online Access problems
Microsoft 365 Copilot Disrupted
Microsoft Defender XDR Affected
Purview, Power BI, To Do, Planner Affected, per WindowsForum

Windows Central and XDA Developers also listed OneDrive and Azure in the reports they saw.

For a while it looked like half the internet was down, because people also reported problems with Google, Steam and AWS. That turned out mostly wrong. AWS and Cloudflare spokespeople told Windows Central their services were not down.

Who got hit

This wasn’t only office workers missing a few emails. Governments felt it too.

Al Jazeera reported that government systems in Singapore and Japan were disrupted, and so were communications at the Supreme Court of the Philippines. In Australia, the country’s spy agency and federal police were among those affected. Home Affairs Minister Tony Burke said at a press conference in Sydney that Microsoft had told him “there is an update that has gone awry.”

In the US, New York City Emergency Management warned residents that “you may experience delays or temporary disruptions” when reaching city agencies by email or through online services that use Microsoft systems, ABC News reported. The city told people to call 311 for non-emergencies and 911 for emergencies.

The outage also hit integrations that other tech companies use, “including the AI firms OpenAI and Anthropic,” according to Al Jazeera.

What caused the Microsoft outage?

Short answer: Microsoft hasn’t said for sure yet. Here’s what it has said.

First, it blamed “elevated load across multiple regions.” Then it walked that back a bit. Its status account said: “We determined the elevated load isn’t driven by an increase in traffic, but by a number of servers being unexpectedly unavailable,” as quoted by NBC Chicago.

So it wasn’t too many people logging in. Servers dropped out, and the ones left standing got crushed trying to handle everyone else’s connections.

Cybersecurity News reported that failed automated health checks, the system that decides if a server is ready to take requests, were a big part of the mess. Microsoft also said “a core process on affected servers was becoming overwhelmed.” Some servers it brought back went down again once traffic hit them. Microsoft told ABC News those servers “can become unresponsive again once they receive traffic.”

On Friday, Microsoft was rolling back a recent network change, Al Jazeera reported. WindowsForum says the timing of that change matched the start of the outage, but Microsoft has not said the change caused it. The company says it will publish a post-incident report once things are fixed. Windows Central says that kind of report can take weeks.

Was it a cyberattack?

No, according to Microsoft. Charles Lamanna, Microsoft’s executive vice president of Copilot, Agents and Platform, posted on X late Thursday that “there is no indication this is the result of malicious or cyber activity,” Al Jazeera reported.

Why the fix took so long

If you were wondering why this dragged into a second day, Microsoft’s own updates tell the story. It tried fixes that didn’t work, then tried more.

Here’s roughly how it went:

  1. Thursday afternoon: Microsoft started moving traffic around its worldwide servers. “We’ve paused all deployments, we’re moving additional traffic off the affected infrastructure,” it said, per ABC News.
  2. Thursday, about 6 p.m. ET: It said it was “returning a portion of affected servers to the service,” ABC reported.
  3. Late Thursday: Microsoft admitted its changes “were not taking effect as expected,” Al Jazeera said. More than 12 hours in, it described its progress as “marginal success.”
  4. Early Friday: Microsoft said it was “confirming that developed patches have been applied and working as intended.” WindowsForum reported the patch went first to regions entering peak business hours.
  5. Friday, 7:33 a.m. ET: Microsoft said it was “seeing encouraging recovery progress, with service availability and email delivery performance improving across a growing portion of affected Microsoft 365 infrastructure,” per Windows Central. Downdetector reports had fallen from nearly 130,000 to under 10,000.

As of Friday morning ET, Microsoft had not said the incident was fully resolved, and some users still reported intermittent issues.

Did you lose your emails?

Probably not. Microsoft said delivery may be delayed rather than lost, and it extended the email timeout window to 48 hours, so messages stuck in the queue get more time to reach you instead of bouncing back. Windows Central confirmed that 48-hour window was still in place on Friday morning.

If your inbox still looks off, here’s what you can do:

  • Check the official status. Go to status.cloud.microsoft or follow @MSFT365Status on X. If you’re an IT admin, look up MO1550821 and EX1550543 under Health > Service health in the Microsoft 365 admin center.
  • Use the desktop app. Outlook on your computer can still show mail that already downloaded, even when the web version won’t load.
  • Don’t mess with your settings. Logging out, resetting passwords or changing your account setup won’t fix a problem on Microsoft’s side. It can make things worse once service comes back.
  • Pick up the phone for urgent stuff. If someone needed your reply yesterday, call or text them. Your email may be sitting in a queue.
  • Resend anything time-sensitive later. Once your mailbox loads normally, check your Sent folder and resend anything that looks stuck.

This is the third big Microsoft outage of the year

If this feels familiar, that’s because it is. In January, Microsoft 365 went down across North America for almost 10 hours, and in late August thousands of Outlook users around the world got locked out, Al Jazeera noted. That’s on top of the AWS outage in October 2025 and the CrowdStrike crash in July 2024 that grounded flights and froze bank systems.

Tech analyst Rupert Goodwins summed up how most people felt when he told Al Jazeera: “It’s very embarrassing for Microsoft and really, really annoying for the rest of us.”

Walter Pasquarelli, an affiliate researcher at the University of Cambridge’s Bennett School of Public Policy, pointed at a different problem: “this is first and foremost a communication risk.” When one company runs email for governments, courts and police across dozens of countries, one bad day reaches all of them at once.

For investors, the thing to watch is that post-incident report. If it shows a botched update caused this, expect more questions from big customers about how Microsoft tests changes before rolling them out. If you follow tech and security stocks, check our list of the top 15 cybersecurity stocks in the USA.

LEAVE A REPLY

Please enter your comment!
Please enter your name here