Daily Pakistan & World News

Main Tags

Categories

Breaking

Advertisement

Microsoft 365 Outage Ends: Cause Revealed, Apology

Microsoft 365 Outage Ends: Cause Revealed, Apology

Building 92 of the Microsoft campus in Redmond, home of the Microsoft Visitor Center

Photo: Building 92 of Microsoft's Redmond campus (archive photo, 2015). Photo: Jiaqian AirplaneFan, via Wikimedia Commons, CC BY.

Microsoft has said its Microsoft 365 services are broadly recovering after a global outage that left millions of users unable to reach their email, calendars and workplace tools. The company has revealed the cause, apologised to customers and confirmed that full recovery still has no fixed date. The outage began on Thursday, 12 November, hit Outlook and Exchange Online hardest and affected users in more than 70 countries.

By Friday afternoon, Microsoft reported "broad recovery and stability across our services" and said it was "deeply sorry". Email queues were "significantly reduced and approaching normal levels", and services were restored gradually by region, with Asia-Pacific first. But as of Saturday morning, some incidents were still listed as open degradations and the backlog was still clearing.

What broke — and for how long?

The outage began on Thursday, 12 November, at around 11:17am Eastern Time (16:17 UTC), when mailbox failures were first reported. Microsoft tracked the incident under the codes EX1550543 and MO1550821. Outlook and Exchange Online were hit hardest, while Teams calendar and scheduling and Copilot were affected where they depend on Exchange.

How long the outage lasted depends on where you were and how recovery is measured. Some trackers put the disruption at around 12 hours for parts of Asia-Pacific, while global reporting put it at roughly 21 to 26 hours for many users elsewhere. No single global duration is stated as settled, because regional variation makes any one figure misleading.

The scale was enormous. Outlook reports on Downdetector passed 130,000 in the United States alone, and users in more than 70 countries were affected. For businesses on Microsoft 365, it meant a working day lost, meetings missed and messages delayed.

The cause: a network capacity upgrade bug, not a cyberattack

Microsoft has now confirmed the cause: a bug introduced during an earlier network capacity upgrade surfaced after a recent network change. Servers began failing health checks, and a secure-connection process was overwhelmed.

Crucially, Microsoft says the outage was a technical failure, not an attack. The company said the issue was "not related to cyber or AI/agents" and was not a cyberattack, and there is no indication of malicious activity. That rules out the speculation that circulated at the outage's worst.

The explanation will still raise questions inside Microsoft. A bug introduced during a routine capacity upgrade, which only surfaced when a later network change was made, points to a gap in testing and in the safeguards around network changes. The company has promised a full post-incident report, but it has not yet been published.

Microsoft apologises as services recover

Microsoft's apology came on Friday, 13 November, at around 1pm Eastern Time, when the company reported broad recovery and stability. It was aimed at the millions of users and businesses that depend on Microsoft 365, many of whom had been without email for a full working day or more.

Recovery has been gradual and regional. Asia-Pacific was restored first, with other regions following as engineers worked through the backlog of undelivered email. Microsoft said queues were significantly reduced and approaching normal levels — stopping short of declaring the incident over.

What is still not back to normal?

Despite the broad recovery, the incident is not fully closed. As of Saturday morning, the affected incidents were still listed as open service degradations and the email backlog was still clearing. Microsoft extended the email delivery timeout to 48 hours.

Most importantly, Microsoft has given no date for full recovery. In its own words: "We do not have an ETA for full recovery yet." Users should expect some residual delays while the backlog clears, even though the worst of the outage is over.

The full post-incident report, which should explain what went wrong and what Microsoft will change to stop it happening again, has been promised but not yet published. Until it appears, the picture is incomplete: the cause is known, the apology has been made, and services are broadly back, but the final chapter of this outage has not yet been written. Related coverage: US Flights Grounded Nationwide in FAA Ground Stop and EU Forms Ukraine Peace Team, Plans €500bn AI Push. More business news: Business News on The Global Thinker.

Frequently Asked Questions

What caused the Microsoft 365 outage?
Microsoft says a bug from an earlier network upgrade surfaced after a recent network change. Servers failed health checks and a secure-connection process was overwhelmed. It was a technical issue, not a cyberattack, with no indication of malicious activity.

Is Microsoft 365 fully back to normal?
Not yet. Microsoft reported broad recovery on Friday, 13 November, but incidents remain listed as open service degradations, the email backlog is still clearing, and Microsoft says it has no ETA for full recovery.

How many people were affected by the outage?
Users in more than 70 countries were affected, and Outlook reports on Downdetector passed 130,000 in the US alone. The outage lasted more than a day for many users, with recovery varying by region.

Comments