Microsoft 365 Outage Fixed After 24 Hours, Global Capacity Upgrade Blamed

Microsoft confirmed on Saturday, November 14, 2026, that the global Microsoft 365 outage is over, with services fully restored after more than 24 hours offline. In its final update on the incident, the company said it had "completed our efforts to address the underlying issue of the incident and restored service to the remaining impacted customers and regions." The Microsoft 365 outage, which began on Thursday, had knocked out Outlook, Teams and Copilot for users in at least 74 countries — and Microsoft now blames a network capacity upgrade, not a cyberattack.

US News Pulse first reported the outage on Thursday, when reports of failed inboxes surged just after noon Eastern time and peaked at nearly 130,000 on Downdetector. On Friday, the failure stretched into a second day. The restoration closes one of the longest Microsoft 365 disruptions in years — the third major failure of the service in 2026.

Key Points

• Microsoft confirmed on Saturday, November 14, 2026, that the global Microsoft 365 outage is fully fixed after more than 24 hours.
• Outlook, Teams, Copilot, SharePoint, Defender and Planner were affected, with Exchange Online mailboxes hit hardest, in at least 74 countries.
• Downdetector reports for Outlook peaked at nearly 130,000 shortly after 1 p.m. ET on Thursday, November 12.
• Microsoft blamed an earlier network capacity upgrade, not a cyberattack or an AI fault, and said it was "deeply sorry".
• The incident is tracked as MO1550821 and EX1550543, and Microsoft promised a full post-incident report.

Microsoft 365 Outage Fixed: What Happened

The end came quietly, in a short message from Microsoft's service-health account. On Saturday, the @MSFT365Status account posted its final update on incident MO1550821, saying the company had completed its work on the underlying problem and restored service to the remaining customers and regions still affected. For millions of users, that was the first official word that the long weekend of failed inboxes was over.

The fix followed a slow, staged recovery. Through Friday and into Saturday, Microsoft engineers brought servers back online in stages, redirecting traffic and restarting affected systems. By Saturday, Downdetector complaints had fallen to a trickle, inboxes began syncing again, and Microsoft's status page showed the incident closed.

How the Outage Began on Thursday

The failure struck mid-workday on Thursday, November 12, 2026. Reports surged just after noon ET, peaking at about 130,000 Outlook problem reports shortly after 1 p.m. ET. Microsoft 365 reports topped 46,000 and Teams reports reached about 3,000. Within about an hour, reports were coming from 74 countries and territories.

Microsoft logged the Exchange Online incident, EX1550543, at 16:17 UTC on Thursday, and the wider Microsoft 365 advisory, MO1550821, about two hours later. On Friday, the outage entered its second day, with Microsoft reporting only "early stabilization and capacity improvements" and no time for full recovery. Microsoft extended the email timeout to 48 hours, giving delayed messages two days to arrive instead of bouncing back.

What Caused the Failure: A Network Capacity Upgrade

Microsoft has now given a clearer cause than it offered in the first hours of the outage. A spokesperson said the incident was introduced by an issue during an earlier network capacity upgrade, which surfaced after a recent network change. Servers unexpectedly became unavailable, straining the infrastructure that remained.

Importantly, the company is clear about what did not cause the failure. It was not a cyberattack, and it was not a fault in Microsoft's artificial intelligence systems. Executive vice president Charles Lamanna confirmed there was no security breach, and Microsoft said it is "not aware of any malicious activity." The cause was internal: a routine upgrade that went wrong. Microsoft said it was "deeply sorry" and promised a full post-incident report.

Reactions: Relief, and Questions for Microsoft

For the businesses, hospitals, courts and airlines caught in the outage, the fix brings relief — and a bill to count. During the disruption, offices were pushed back onto phones, paper records and fax machines. Workhorse Group had already rescheduled its third-quarter results to November 16, citing the disruption.

The failure also broke connectors used by OpenAI and Anthropic, a reminder of how deeply Microsoft's cloud is woven into other companies' products. The timing could hardly have been worse for Microsoft's reputation: this is the third major Microsoft 365 disruption this year, after multi-hour outages in January and a code-update failure in August. Each time, the company has promised to learn — and each time, customers have asked why the world's largest workplace cloud keeps going dark.

Why It Matters

Email remains the backbone of offices, schools and government agencies, and Outlook is the inbox most American workplaces run on. When it fails for more than a day, the cost is thousands of small delays: a contract unsigned, a medical result unread, a job application unanswered, a court filing late.

With users in 74 countries affected, this was not a regional glitch but a failure of the central infrastructure Microsoft sells as always available. The outage arrived in the same week as a separate Workday outage that locked employees out of payroll and HR systems, a reminder that the tools offices depend on most are also the ones with the fewest backups.

What Happens Next

Microsoft will keep monitoring the service closely in the days after the fix, watching for renewed instability as full traffic returns. Users should check their inboxes directly, and anyone waiting on an important message should confirm it arrived — some messages may still be working through the backlog.

Businesses that depend on Exchange Online connectors, including AI tools, should verify those links work again before relying on them. The fuller account will come in Microsoft's post-incident report, which should explain why the network capacity upgrade failed and how the company will stop it happening a fourth time.

Frequently Asked Questions

Is Microsoft 365 back to normal?
Yes. Microsoft confirmed on Saturday, November 14, 2026, that the global outage is over and services are fully restored after more than 24 hours, in its final update on incident MO1550821.

What caused the Microsoft 365 outage?
Microsoft blamed an earlier network capacity upgrade, not a cyberattack or an AI fault. A spokesperson said an issue during the upgrade surfaced after a recent network change, leaving servers unexpectedly unavailable.

Which services were affected?
Outlook, Teams, Copilot, SharePoint, Defender and Planner were affected, with Exchange Online mailboxes hit hardest. Users in at least 74 countries reported problems.

Will my delayed emails arrive?
Microsoft extended the email timeout to 48 hours during the outage, so delayed mail should still arrive rather than bounce back, though some messages may still be working through the backlog.

What are EX1550543 and MO1550821?
EX1550543 covers the Exchange Online mailbox failure, logged at 16:17 UTC on Thursday, November 12, and MO1550821 covers the wider Microsoft 365 disruption logged about two hours later.