Microsoft confirmed a worldwide outage that has crippled Teams, Outlook, Copilot, Exchange Online, SharePoint and Microsoft Defender XDR across 74 countries, affecting tens of thousands of users and prompting an eight-hour recovery effort.

The incident marks at least the fifth major Microsoft 365 outage in 2026, highlighting a recurring reliability challenge for the cloud-software giant.

What Caused the Outage and How Microsoft Responded

Microsoft attributed the disruption to "a large number of servers being unexpectedly unavailable." In a follow-up post on X, the company said its infrastructure was "experiencing elevated load across multiple regions." To mitigate the problem, Microsoft paused all deployments, redistributed traffic across its global network and began manually restarting servers. The manual restarts progressed slower than expected, which caused the recovery timeline to slip repeatedly.

After more than eight hours, Microsoft admitted that its fix was "not taking as expected." Earlier, the firm had reported "positive results" from recovery efforts, only to later retract that assessment.

Scale of the Outage: Complaints and Affected Services

Outlook complaints peaked at nearly 140,000 reports around 18:00 GMT on Thursday, according to the BBC. That volume represents more than 2,000 times the normal level of complaints. ABC News reported that nearly 130,000 users also filed reports on Downdetector around 1 p.m. Eastern Time.

The outage touched a wide range of Microsoft 365 services, including Exchange Online, Microsoft Teams, SharePoint Online, Microsoft Copilot 365, Microsoft Defender XDR, Microsoft Planner, Microsoft To Do and Microsoft Intune. Personal Microsoft accounts remained largely unaffected; enterprise and work accounts bore the worst impact.

Geographic Reach and Sector Impact

The disruption cascaded quickly across sectors and countries. In Australia, Service NSW urged customers to delay visits and complete transactions online, while the Northern Territory government reported complete service loss. Hospitals experienced clerical issues but kept patient care intact, with some facilities reverting to paper prescriptions as a temporary workaround.

Schools reported students unable to access lessons through Teams and staff losing email access. In India, more than one lakh (100,000) incidents appeared on Downdetector. Users in the Netherlands, Poland, France, Sweden and Latin America also reported failures.

Business Consequences of a Multi-Service Failure

More than 430 million people use Microsoft 365 apps globally. Over 90 % of Fortune 500 companies rely on Copilot, and between three and four million companies run their operations on the platform. Because the outage hit email, video conferencing, file sharing, security tools and AI assistants simultaneously, affected businesses effectively lost an entire working day.

Cybersecurity expert Troy Hunt warned that the impact extends far beyond Microsoft's direct users. Microsoft forms a massive part of the internet backbone, so the disruption affected account verification, purchase confirmations, appointment communications and third-party services.

Paul Spain of New Zealand-based Gorilla Technology said that if the outage is not a cyber-attack, it reflects "incredible incompetence" that will cost millions in economic losses. Microsoft has stated the outage is unlikely to result from malicious activity.

Recent Outage History in 2026

Microsoft's outage record in 2026 shows a pattern of recurring failures:

  • January: a 10-hour outage disrupted Exchange Online, Teams and Outlook due to elevated service load during maintenance.
  • July: a network failure in the West US region knocked out Azure and Microsoft 365 services.
  • August: Exchange Online problems spread to Teams, SharePoint and Defender.
  • September: US and UK users faced five hours of intermittent failures with SSO errors.

Each incident follows a similar sequence: Microsoft identifies the problem, announces positive recovery signals, then extends the timeline after fixes take longer than expected.

What This Means for Enterprise Customers

Enterprises that depend on Microsoft infrastructure for daily operations now face heightened scrutiny of reliability and contingency planning. The repeated outages raise questions about the robustness of Microsoft's redundancy measures and the transparency of its communication during incidents.

Customers are advised to review their business-continuity plans, consider alternative communication channels and monitor Microsoft's service health dashboards for real-time updates.

What Comes Next

Microsoft has not announced a specific timeline for a post-mortem report. The company typically publishes a detailed analysis after major incidents, outlining root causes and corrective actions. Stakeholders should watch for that report, as well as any updates to Microsoft's service-level agreements and future infrastructure upgrades.

In the meantime, users can track ongoing status via the Microsoft 365 Service Health portal and the official Microsoft X account, which continues to post incremental updates.