Microsoft Outage: 130,000 Outlook Reports and a Cloud Puzzle

DownDetector logged 130,000 Outlook reports as a global Microsoft outage hit Teams, SharePoint and Defender. Experts point to failed health checks, not hackers.

Wire notes

  • DownDetector logged about 130,000 Outlook outage reports by early Thursday afternoon US Eastern time
  • Microsoft listed Outlook, Teams, SharePoint Online, Copilot 365, Planner, Exchange Online and Defender as potentially impacted
  • Microsoft stated: "There's no indication this is a cyber attack"
  • The failure followed an August code update that disrupted Outlook and Exchange Online for several days
  • Some recovered servers "can become unresponsive again once they receive traffic", Microsoft said
Microsoft has suffered a global outage. A tech expert explains what went wrong
PhotoMicrosoft has suffered a global outage. A tech expert explains what went wrong — markusspiske / pixabay

Some 130,000 people reported problems accessing Microsoft Outlook on DownDetector as of early Thursday afternoon US Eastern time, as a global outage brought the company's email, cloud storage and collaboration tools to a standstill.

Microsoft confirmed the failure in a statement on X, saying it was "aggressively pursuing all pathways to reduce impact" and "restarting affected servers to return them to service".

Mahmoud Elkhodr, Senior Lecturer in Information and Communication Technologies at CQUniversity Australia, argues the incident exposes a structural risk: services that look separate fail together when they share infrastructure.

Which services went down?

Microsoft's own list of "potentially impacted" services is long. It covers email, document sharing, meetings and task management:

  • Outlook and Microsoft Exchange Online
  • Microsoft Teams
  • SharePoint Online
  • Microsoft Copilot 365
  • Microsoft Planner
  • Microsoft Defender, a cloud-based cybersecurity service

The real-world damage spread far beyond missed emails. According to reports cited by Elkhodr, family violence workers lost access to client databases. Schools could not deliver online lessons to remote students. Psychologists could not run telehealth consultations. Businesses could not process orders. Job hunters missed scheduled interviews. Some government service centres closed.

The disruption also crossed corporate boundaries. OpenAI and Anthropic reported problems with the tools that connect their AI services to Microsoft 365, showing how a fault in one part of the digital ecosystem can impair services operated by other companies.

This is the third significant Microsoft disruption this year, following a multi-hour Outlook and Teams outage in January and an August code update that disrupted Outlook and Exchange Online for several days.

What went wrong?

As of early Friday afternoon Sydney time, Microsoft had not named a root cause, and its account shifted over time. The company first reported elevated load across multiple regions. It then clarified the load was not driven by more traffic, but by a large number of servers becoming unexpectedly unavailable.

Attention moved to the automated "health checks" (the mechanism that judges whether a server is fit to carry traffic) and to the component that processes them. Microsoft described a core process on the affected servers as becoming "overwhelmed". The company paused software deployments and configuration changes while reviewing recent changes, but found none that correlated with the start of the disruption.

Was it a cyberattack?

Microsoft said: "There's no indication this is a cyber attack."

Elkhodr walks through the evidence. A distributed denial-of-service attack (a flood of external requests that crowds out legitimate users) implies rising traffic. Microsoft's own statement that overall traffic had not increased contradicts that pattern. No malicious activity has been disclosed, and no group has claimed responsibility.

The mundane explanation fits better, he writes. Health checks exist to protect a service by withdrawing servers that appear unwell. When the machinery making that judgement is itself at fault, healthy capacity gets removed, and the remaining servers absorb work they were never sized for. Outages of this scale are more often self-inflicted than attacker-driven, as the August email disruption caused by a code update illustrates. Until a post-incident review appears, that remains an inference from Microsoft's updates rather than a settled account.

Recovery is incomplete. Microsoft says some affected servers are working again, but they "can become unresponsive again once they receive traffic".

How should organisations prepare?

Elkhodr's prescription treats digital outages like natural disasters. Individuals should store essential information, such as contacts and medical prescriptions, offline. Organisations that rely on a single provider such as Microsoft or Google must build backup plans and, crucially, test them, the way they run fire drills and communities rehearse bushfire evacuations.

As cars, homes, workplaces, transport and healthcare connect further, and AI adoption widens, the consequences of digital disruption will grow. Building resilience, he concludes, must be part of how that future gets planned.

via digitalinformationworld.com (Source)

Filed under

Share this article:

More from Elena Vasquez

Elena Vasquez

Show full bio

Senior reporter covering technology and product news in marketing, advertising, marketing technology, media, SEO and search at Marketing Herald.

289 articles

More on the wire

« Previous article