
Microsoft links global Outlook outage to network upgrade flaw
The failure disrupted email and collaboration worldwide as shared cloud infrastructure made one network problem affect multiple services.
Overview
Millions of people briefly lost access to Outlook and other tools during a global outage that lasted nearly a day. Teams, , , and other services were also affected, disrupting email, meetings, file access and business tasks worldwide. Microsoft said the cause was a technical failure, not a cyberattack or an AI problem.
The problem began with an earlier network capacity upgrade and appeared after a newer network change. Some systems failed , shifting work to other systems and making them harder to repair. Microsoft restored services by region, but some users still had delays or occasional access problems. The outage showed how one change in shared cloud systems can affect many products. Microsoft apologized and promised a review and fixes.
Timeline
Microsoft apologized and continued its incident review after the global outage
Microsoft apologized for the disruption and said recovery actions would continue until remaining customers and regions were restored. The technical explanation and promised review underscored how a network change can propagate through and interrupt several workplace products at once.
Microsoft restored services gradually while Exchange Online continued to degrade for some users
The company reported broader improvement in North America, sustained improvement across much of Europe and encouraging recovery signals in Asia Pacific. Some users still faced intermittent access problems or delayed email delivery, and remained among the affected services during the staged recovery.
Microsoft addressed the underlying issue and began restoring customers and regions
Microsoft said it had fixed the underlying problem and applied mitigations that restored service health and functionality in parts of the affected infrastructure. Recovery was not simultaneous, with improvements appearing first in some regions and services while others remained unstable.
Elevated infrastructure load slowed Microsoft’s restoration efforts
Microsoft used a measured process to identify, repair and restart affected infrastructure instead of returning all systems to service at once. Failed , delayed email queues and the scale of returning demand made sustained recovery difficult.
Microsoft linked the outage to a network change that exposed an earlier capacity-upgrade problem
Microsoft said an issue introduced during an earlier surfaced after a more recent network change. The interaction caused affected infrastructure to fail and become unavailable to services that depended on it.
Microsoft said the outage was a technical failure, not a cyberattack or AI failure
Microsoft stated that the incident was not related to or . The clarification separated the outage from security compromise or an autonomous-system failure while the company continued investigating its infrastructure.
Organizations lost access to core email and collaboration tools
The incident disrupted workplace email, meetings, collaboration and other business workflows that depend on Microsoft 365. Reports described problems with Outlook access, delayed email delivery, Teams functions and Copilot responses.
The outage affected Outlook, Teams, Copilot and other Microsoft 365 services
Microsoft said the disruption affected Outlook and , with related connectivity problems reported across Teams, Copilot, SharePoint, OneDrive, OneNote, To Do and other Microsoft 365 services.
Microsoft confirmed a broad platform incident affecting multiple regions
Microsoft acknowledged that users could not connect to several Microsoft 365 services rather than facing isolated account or device problems. Early reports indicated that the incident affected users in North America, Europe, Asia Pacific and other regions.
Users worldwide reported that Outlook and Microsoft 365 services were inaccessible
The disruption began around 1 p.m. Eastern time and quickly generated tens of thousands of outage reports. Users reported problems accessing , and related workplace services across multiple regions.