Workers traded jokes about an unexpected break from their inboxes as a broad Microsoft 365 outage disrupted Outlook, Teams, Copilot and related services across businesses and public institutions. The disruption began on Thursday, Nov. 12, and continued into Friday as users in the United States, Europe and Asia reported trouble accessing email, calendars, workplace messaging and connected tools. M. Eastern time, while thousands more users reported problems with Teams, Copilot and other Microsoft 365 services.
Microsoft initially described elevated load across multiple regions and said unexpectedly unavailable servers were straining the remaining infrastructure. Its status updates said affected machines were failing automated health checks, while a process responsible for establishing secure connections became overwhelmed. The company later identified the preliminary cause as an issue introduced during an earlier network-capacity upgrade that surfaced after a recent network change. Microsoft said it had found no evidence that malicious activity or artificial-intelligence systems caused the incident.
Microsoft said access began improving by Friday morning, with Asia-Pacific services among the first areas to normalize, but warned that intermittent problems and delayed mail could continue. Engineers extended the period in which delayed messages would keep attempting delivery to 48 hours and monitored growing email queues before declaring the incident resolved.
The outage reached beyond individual inboxes. Britain’s National Health Service said some services were affected but told patients to attend appointments, while a hospital group serving southwest London and Surrey warned that calls could face long waits. Air India temporarily rerouted email traffic and said flight operations were unaffected. Richemont’s earnings announcement was slightly delayed, and Workhorse Group moved its third-quarter results release from Nov. 12 to Nov. 16, citing disruption from the outage.
Microsoft apologized to customers and partners and said the underlying issue had been addressed, with remaining regions restored by Saturday. The company said it would complete a post-incident review and publish a fuller explanation. The episode also prompted scrutiny of how heavily companies and public services rely on a small number of cloud and workplace platforms, while the outage’s reported scope renewed attention to offline procedures, backup communications and recovery planning.
