Microsoft 365 Outage Lasted Over a Day After Network Upgrade Broke Routing

Microsoft restored Microsoft 365 on 14 November after a network upgrade flaw downed Outlook, Teams and Copilot for more than a day, generating 7.4 million outage reports.

Wire notes

  • Microsoft 365 outage began 11:17 a.m. ET on 12 November and service was restored 14 November.
  • Downdetector logged more than 7.4 million outage reports worldwide.
  • Root cause: a network capacity upgrade exposed by a later network change; fix applied to an authentication and routing component.
  • NHS switched to backups; Air India, IndiGo and Akasa Air reported email problems; a Taiwanese firm used fax to confirm trades.
  • Microsoft found no evidence of malicious activity and ruled out AI as the cause; incident tracked as MO1550821.
Microsoft 365 outage explained: a network upgrade broke Outlook and Teams
PhotoMicrosoft 365 outage explained: a network upgrade broke Outlook and Teams — Albert Stoynov / unsplash

By Tom Whitfield

Microsoft restored Microsoft 365 service on Saturday, 14 November, ending an outage of more than a day that took down Outlook, Teams, Copilot and other services used by companies, hospitals, airlines and government agencies worldwide.

The failure began with Exchange Online at roughly 11:17 a.m. ET on Thursday, 12 November — 8:17 p.m. in the UAE. Within about two hours it spread across the Microsoft 365 stack. Outlook and Exchange were hit first. Teams calendars and meeting scheduling, Copilot, SharePoint and Intune followed, though some features kept working throughout the disruption.

What caused the outage?

Microsoft's explanation shifted as events unfolded. The company first blamed unusually heavy traffic. Its engineers then discovered that several backend servers had gone offline unexpectedly, leaving the remaining servers to handle more load than they could manage. Restarting the failed servers did not help: they stopped responding again as soon as traffic returned.

Microsoft eventually traced the root cause to an earlier network capacity upgrade, which a subsequent network change had exposed. Engineers deployed a fix for an authentication and routing component, then brought traffic back gradually while delayed emails were delivered.

Microsoft says it found no evidence of malicious activity and has ruled out AI as the cause. That will reassure customers worried about a cyberattack. Still, a routine infrastructure change triggering a global failure lasting more than a day is a sobering explanation in itself.

The incident shows how many organisations now depend on a single vendor's network for email, scheduling and collaboration — with few real alternatives when that network fails.

How far did the damage spread?

The effects reached well beyond office inboxes:

  • Britain's NHS switched to backup systems.
  • Air India, IndiGo and Akasa Air in India reported problems with email support.
  • Financial firms were hit.
  • One Taiwanese company went back to fax machines to confirm trades.

Downdetector logged more than 7.4 million outage reports worldwide. That figure counts reports rather than individual users, but it still indicates how widespread the disruption became. In plain terms: millions of reported incidents across healthcare, aviation, finance and government.

What happens next?

IT administrators can follow further updates under incident MO1550821 in the Microsoft 365 admin center. The bigger question is what Microsoft does next.

Enterprise customers will want a full post-incident report. Some may look closely at their service-level agreements. Many will also be asking whether one network change should ever be able to cause this much damage.

via absolutegeeks.com (Source)

Filed under

Share this article:

More from Tom Whitfield

Tom Whitfield

Show full bio

Staff writer covering companies, deals and strategy in marketing, advertising, marketing technology, media, SEO and search at Marketing Herald.

360 articles

More on the wire

« Previous articleNext article »