Software · Outage

Microsoft 365 is down worldwide: Outlook email, Teams and Copilot knocked out

Microsoft 365 is suffering a global outage this Thursday. Exchange Online mailboxes became inaccessible through several connection methods, and Microsoft's main incident (MO1550821) also affects Teams, SharePoint Online, Microsoft 365 Copilot and Defender XDR; the mail incident is EX1550543 in the admin center.

THE BUYER'S PULSESoftware9 min read
An office at a standstill during the Microsoft 365 outage, monitors showing network errors while workers check their phones
An office at a standstill: network errors on screen after screen. Illustration: The Buyer's Pulse.

Illustration: The Buyer's Pulse.

It began in the Americas, and Microsoft later confirmed it can affect users in any region. On Downdetector, user reports for Outlook peaked at around 130,000 near 1:10 p.m. ET, with Microsoft 365 reports around 46,000–47,000.

A modern server room — the kind of infrastructure a suite like Microsoft 365 runs on. · Video by ALL IZ Well via Pexels
EX1550543The mail incident, tracked in the Microsoft 365 admin center
MO1550821The main incident: Teams, SharePoint Online, Copilot and Defender XDR
~130,000Outlook reports at the Downdetector peak — user reports, not a user count
No ETANo restoration time given; the outage remains open

The cause, according to Microsoft itself — which corrected its first explanation — was not a traffic spike: a set of servers went out of service unexpectedly and saturated the remaining infrastructure. The company is testing a configuration change tied to servers failing their automated health checks, restarting the affected ones, keeping every deployment paused and redistributing traffic.

As of this writing there is no estimated time for restoration and the outage remains open. It is the day's second failure: Teams already suffered another one in the morning, now resolved.

How the failure unfolded

Microsoft says the Microsoft 365 incident began at 1:26 p.m. ET, although its engineers had begun investigating reports of Exchange Online mailbox connectivity problems in the Americas earlier in the day. The first advisory covered the mail service; the wider incident, MO1550821, then confirmed that customers might be unable to connect to Exchange Online, Microsoft Teams, SharePoint Online, Microsoft 365 Copilot and Microsoft Defender XDR at all.

The explanation changed as the afternoon went on. Microsoft first pointed to elevated load on part of its infrastructure across several regions. It then corrected itself in an update on X: "We determined the elevated load isn't driven by an increase in traffic, but by a number of servers being unexpectedly unavailable; straining the remaining infrastructure. We're working to safely return them to service." In other words, capacity disappeared first — and the demand that remained fell on fewer machines.

The mitigation followed from that diagnosis. Microsoft paused all deployments, redistributed connection traffic across its worldwide infrastructure, moved additional traffic away from the affected systems and began restarting the affected servers to restore capacity. It also acknowledged that, although the first reports came from the Americas, the issue could affect Microsoft 365 service connectivity for users in any region.

For the people trying to work through it, the failure was simple to describe: mailboxes that would not open through any of the usual doors. Microsoft's mail advisory covers access through multiple connection methods, which is why switching between the web app, the desktop client and the phone did not help: the problem sat behind all of them, in the service itself, not in any one application.

The public curve of the outage comes from Downdetector, which collects reports filed by users themselves. Complaints surged on Thursday afternoon across Outlook, Microsoft 365, Teams, Copilot, Azure, OneDrive and the Microsoft Store. Outlook reports peaked at just shy of 130,000 around 1:10 p.m. ET, and Microsoft 365 reports passed 47,000 shortly after; Teams peaked at about 4,600 reports and Copilot at about 6,000. By 3:20 p.m. ET roughly 69,000 users were still reporting Outlook problems, with about 31,000 more reporting Microsoft 365 issues. Those figures measure how many people filed a report, not how many were affected: Microsoft has not given a number for affected customers.

The second failure of the day

The afternoon outage was not the first. Earlier on Thursday, a separate Teams incident — tracked as TM1550488 — ran from 9:45 a.m. to 10:53 a.m. ET and hit users in North and South America with delays and failures when sending messages, errors creating or updating conversations, and problems retrieving chat messages. Microsoft attributed that one to resource contention inside its infrastructure, which pushed utilization up until the service could not process messaging requests normally, and says it was fully resolved. The company has not said whether the two incidents are related.

The curve, hour by hour

The rounded peak hides a precise count. According to USA Today's live coverage, Downdetector logged exactly 128,874 Outlook reports at 1:09 p.m. ET. From there the curve fell in stages, and the stages matter more than the peak. By 1:50 p.m. ET, Outlook reports were down to 92,914 and Microsoft 365 reports to about 37,000 — a clear improvement, but still a mass incident by any measure, less than an hour after the worst moment.

The fall then slowed. USA Today reports that outage reports dropped further around 3 p.m. ET, but settled into a relative plateau between 3:30 p.m. and 4 p.m., with just over 58,000 Outlook reports still coming in. Microsoft 365 followed the same shape at a lower level: about 19,000 reports around 3:55 p.m. ET. The last readings in USA Today's live file, just before 5 p.m. ET, put Outlook at about 49,000 reports and Microsoft 365 at about 18,800.

For an operations manager, that shape — a fast partial fall, then a plateau, then a slow decline — is the practical timeline of the incident. It says recovery was real but uneven, and that tens of thousands of users were still filing reports hours after the peak. A falling curve is not a restored service: it is evidence about direction, not a time to stand a company back up.

How Microsoft worked the fix

The mitigation also has a clock. At 1:07 p.m. ET, Microsoft confirmed in an X post, reported by USA Today, that the issue could affect Microsoft 365 service connectivity for users in any region. At 1:48 p.m. it added: "We've begun redistributing connection traffic across our broader worldwide infrastructure to help balance the load."

In a further update relayed by USA Today, Microsoft put the same work more bluntly: "We're aggressively pursuing all pathways to reduce impact. We've paused all deployments, we're moving additional traffic off the affected infrastructure, and we're restarting affected servers to return them to service."

The clearest step forward came around 4 p.m. ET. Microsoft said it had validated an alternative service health check method, which had allowed a subset of affected servers to return to service successfully, and that it was now applying the change more broadly. It was also preparing automated recovery systems to continually detect and restart unresponsive servers. Around the same time, Microsoft said some servers had been "successfully returned to service" and that it was working to apply the fix more broadly.

At 4:40 p.m. ET the work was still validation, not declaration. Microsoft said it was "actively restarting and validating the affected servers to return them to service," and added: "We're continuing to work through restarting and validating the affected servers to safely return them to service, and we're exploring opportunities to expedite this process." Even then, its service health page still showed multiple services — including Outlook, Teams, SharePoint, Copilot and Defender — experiencing disruptions.

What Microsoft has not said

Three questions remain open at the close of this edition. Why a number of servers became unavailable at the same time has no published answer yet: the company corrected what the failure was not — a traffic surge — before explaining what it was. How many customers were affected has not been disclosed. And no restoration time was given at any point, which means the companies waiting on the service had no official clock to plan around, only the sequence of updates.

The silence had a second channel, too. USA Today says Microsoft did not immediately respond to its request for additional comment, and BleepingComputer says it contacted Microsoft with questions about the outage and would update its story if it received a response. Beyond the status posts, there was no fuller account on offer.

What it means for the companies that run on it

Read the affected list again and it is, effectively, the corporate operating system: the mailbox, the meeting and chat layer, the file store, the AI assistant and — with Defender XDR on the list — part of the security console itself. When all of that sits with a single provider, an infrastructure failure stops being an IT ticket and becomes a company-wide pause, in the middle of the business day and across every region at once. That the security team's own detection tooling appears on the affected list, on the very afternoon it is most needed, is the detail risk managers will underline.

The detail of the incident, meanwhile, lives where most employees cannot see it: the full advisories sit in the Microsoft 365 admin center, under EX1550543 and MO1550821, visible to each organization's administrators. For everyone else there is a mailbox that will not open. A vendor that has paused all of its own deployments is telling its customers, in effect, that stability comes before every other change — a reasonable priority, and one that also confirms the scale of what broke.

That is the decision this outage puts on the table for IT managers: not whether Microsoft 365 is the right suite — for most companies that question is settled — but how much of the working day should depend on a single cloud with no fallback channel for mail and meetings, and what the continuity plan says when the honest answer is "all of it." Two incidents in one day, with no stated link between them and no full root cause yet, is exactly the kind of evidence that belongs in the next renewal and SLA conversation.

One detail in the 4 p.m. update widens the operational picture. USA Today reports that Microsoft's health status page then listed users as potentially unable to connect to multiple Microsoft 365 services including Outlook, Teams, SharePoint, Copilot, Defender, To Do and Purview. To Do and Purview were not on the main incident list at the top of this story: the first is the task layer many teams run their day from, the second part of the compliance tooling. The footprint of an outage like this is rarely limited to the applications people complain about first.

Recovery, when it came, also arrived service by service rather than all at once. Just before 5 p.m. ET, USA Today reported that Copilot appeared to be back online for the vast majority of users, while Outlook reports were still running at about 49,000. For the manager deciding when to stand down a workaround, that split is the decision that matters: each service has to be judged on its own evidence, because the suite does not come back as a single block — and the security tooling on the health page was still listed as disrupted at that hour.

The information split has a management cost of its own. El País notes that, for the general public, Microsoft refers people to its status page, while the full incident detail remains in the admin center. That leaves each company's administrators as translators between the vendor's record and everyone else's experience: what employees can see is a status page and a mailbox that does not open, and the quality of the internal message depends entirely on how well the IT team narrates a timeline it does not control.

When the email of millions depends on a single cloud, an outage like this is not just another technical incident: it is the working day of half the world put on pause.

Sources

  • El País (Nov 12, 2026): Microsoft confirms a global Microsoft 365 outage — Exchange Online mailboxes inaccessible through several connection methods, with Copilot among the affected services; the company's first account pointed to elevated load on part of its infrastructure, and no restoration time was given.
  • BleepingComputer (Nov 12, 2026), 'Massive Microsoft 365 outage disrupts Outlook, Teams, Copilot worldwide': the MO1550821 advisory covering Exchange Online, Microsoft Teams, SharePoint Online, Microsoft 365 Copilot and Microsoft Defender XDR; Microsoft's correction — the elevated load was not driven by an increase in traffic, but by a number of servers being unexpectedly unavailable; deployments paused, connection traffic redistributed and affected servers restarted.
  • USA Today (Nov 12, 2026), live coverage of the outage: Downdetector user reports for Outlook peaking at around 130,000 near 1:10 p.m. ET, with Microsoft 365 reports around 46,000–47,000.
  • Microsoft 365 Status (Nov 12, 2026): incidents EX1550543 (Exchange Online mailboxes) and MO1550821 (Microsoft 365 services), tracked in the Microsoft 365 admin center.
  • Illustration: The Buyer's Pulse.