What users reported and how big the disruption was
Microsoft confirmed that its servers were starting to come back online after a worldwide disruption left close to 130,000 people unable to reach parts of its 365 software package, among them Outlook and Teams. The monitoring site Down Detector recorded a sharp rise in complaints, with users flagging trouble opening Word, Excel, PowerPoint, Outlook and Teams, plus business tools including SharePoint and OneDrive. The Copilot AI assistant was hit as well.[S1]
Complaint volumes have eased from that high point, yet plenty of users still described being unable to send or receive mail, or struggling to load their inboxes at all. Outlets in several countries reported the same disruption reaching their audiences, including coverage of the impact in New Zealand and descriptions of the email service going down across the United States.[S1][S2][S3][S6]
The reach of the failure extended beyond Microsoft. Reporting indicated that users of Amazon Web Services and Google services were also logging problems at the same time, while other coverage described the outage as crippling everyday business communication for the organisations that depend on the affected tools.[S5][S8]
Microsoft's account of the cause and its response
In a message on X, Microsoft said it was looking into accounts of people unable to reach Exchange Online mailboxes through various connection methods. The company later said part of its infrastructure was under elevated load, which it believed was probably behind the connectivity failures, and traced the pressure to a set of servers that had become unexpectedly unavailable after failing during automated checks.[S1]
Microsoft reported that as of 9pm UTC on Thursday it had verified a different health-check approach on a portion of the impacted servers, allowing those machines to come back online, and that this fix was being extended to more systems. The firm was additionally developing an automated process to detect and reboot servers that become unresponsive. An examination of recent changes suggested configuration updates might have played a role, but Microsoft said the cause was still being looked into.[S1]
An earlier alert on Microsoft's status site said the company was pursuing every avenue to limit the damage and restarting affected servers to bring them back. Microsoft added that it had halted all deployments and configuration changes as a precaution while it checked recent changes for any link to the incident, and explained that the elevated load came not from a general surge in traffic but from the large number of servers suddenly out of action, pushing demand onto the remaining infrastructure.[S1]
The company had earlier reported that problems with Teams in North America were successfully restored, even though some users kept reporting connectivity trouble. Separate outlets also documented the disruption to Outlook, Teams and Copilot, and the scale of the impact on users in the United States.[S1][S4][S7]






