Microsoft’s cloud overload snarls Outlook, Teams and Copilot worldwide, leaving governments and businesses scrambling as the tech giant races to restore service.
Late Thursday night a massive surge in traffic overwhelmed Microsoft’s cloud infrastructure, causing a sudden and widespread failure of the company’s flagship email platform, Outlook. The disruption quickly propagated to other components of the Microsoft 365 suite, including Teams and the AI assistant Copilot.
By the early hours of Friday, users in 74 countries and territories reported being unable to send or receive messages, access shared files, or join video conferences.
The outage struck a diverse set of customers, from small enterprises to national governments, affecting daily operations that rely on real-time digital communication.
Within an hour the problem had spread across continents, touching the Americas, Europe, parts of Asia and Africa. In New Zealand, the foreign ministry confirmed that its embassies worldwide could not receive mail, while police forces in the United Kingdom urged citizens to call emergency numbers instead of using online reporting tools.
Geographic reach and scale of the failure
According to the online outage tracker Downdetector, the first spikes in user complaints appeared around 17:20 GMT on Thursday, initially centered in North America and Europe. Within sixty minutes the map of affected locations expanded to include Asia-Pacific regions such as Hong Kong and Australia, as well as several African nations. The platform’s status page later confirmed that the elevated load was not confined to a single data centre; multiple regions experienced “elevated load across multiple regions,” a phrasing that indicates simultaneous pressure on the backbone of Microsoft’s cloud.
Peak reports in the United States reached more than 130,000 users simultaneously unable to access Outlook, while European monitoring sites logged thousands of concurrent failures. The sheer breadth of the incident, spanning 74 distinct jurisdictions, suggests a systemic bottleneck rather than a localized hardware fault.
Services knocked offline and the real-world fallout
The outage was not limited to the web interface of Outlook. Both the desktop client and mobile applications displayed a “Failed to fetch” error, and in some cases a blank screen with a Spanish prompt to “comprobar la conexión” (check the connection). Exchange Online, the underlying mail server technology, was unable to process inbound or outbound traffic, causing inboxes to appear empty and preventing any email delivery.
Beyond email, the failure rippled through the wider Microsoft ecosystem. Microsoft Teams meetings could not be joined, and the platform’s chat function stalled. Users reported issues with SharePoint Online, OneDrive, and various productivity tools such as Planner, To Do, and Intune. The AI-driven Copilot 365 assistant, which relies on real-time data from the same cloud backbone, also became inaccessible.
Public sector services felt the impact acutely. In the United Kingdom, police departments advised the public to call 101 or 999 for reporting crimes, while hospitals and general practices reported disrupted internal communications. The National Pharmacy Association warned that prescription processing could be delayed, and NHS England instructed staff to revert to paper-based records where electronic messaging failed.
Microsoft’s response and path to recovery
Within hours of the incident, Microsoft posted updates on its official X (formerly Twitter) account, stating that the company was “aggressively pursuing all pathways to reduce impact.” The firm confirmed that no malicious activity had been detected, ruling out a cyber-attack as the cause. Executive Vice President Charles Lamanna emphasized that the issue stemmed from “servers becoming unexpectedly unavailable,” prompting a large-scale restart of affected machines.
The company halted new deployments, shifted traffic to alternative routing pathways, and began restarting servers to bring them back online. By late Friday evening, the status page indicated that a portion of the affected servers had returned to service and were remaining stable. Microsoft also extended the email timeout window to 48 hours, allowing delayed messages to queue and eventually be delivered once the backlog cleared.
While many users reported partial improvements in mailbox access, Microsoft warned that “some users may continue to experience intermittent issues.” The firm pledged to publish a comprehensive post-mortem once full mitigation was achieved, outlining root-cause analysis and future defensive measures.
For organizations still grappling with the outage, the practical advice has been to rely on backup communication channels (phone calls, fax, or alternative email providers) until the cloud infrastructure stabilises. The incident serves as a stark reminder of the dependencies modern workplaces have on a handful of cloud services and the cascading effects when those services falter.
