Eigen RadarAI
Analysis

Microsoft restores 365 services after a network-change outage

Microsoft reported broad recovery after the outage across Outlook, Teams and Copilot, while restoration continued for some customers and regions. The company linked the disruption to a network upgrade issue exposed by a later change. It extended email queuing to 48 hours as delayed messages awaited delivery and promised a fuller incident review.

Artificial Intelligence··Morning
Three engineers in a cloud provider's network operations centre look up at a large video wall, most tiles green and a few still amber, discussing services returning in stages after the outage.

Broad recovery follows the network repair

Microsoft reported broad recovery and more stable service on November 13 after a disruption across its Microsoft 365 cloud applications. Restoration was continuing for some regions and customers. Outlook email, Teams collaboration and the Copilot assistant had been among the affected services. Microsoft attributed the incident to a fault introduced during a previous upgrade of network capacity and exposed by a more recent network change. The company said it had addressed that underlying problem. It also said the disruption was unrelated to cyber activity or artificial-intelligence agents. Those statements formed its initial explanation while a detailed review was still being prepared. Service was returning in stages rather than through a single simultaneous restoration for all users.[1], [2]

Email delivery gets a 48-hour queue

Microsoft extended the time that email could wait for delivery to 48 hours as it worked through accumulated queues. Messages attempted during the interruption could therefore remain in the delivery process for longer. Restoration teams were clearing those backlogs alongside the return of application access. Jonathan Leitschuh, an independent security researcher, said returning subsystems could produce a rush of delayed notifications. An inbox becoming accessible and the delivery of its accumulated messages were separate steps in that recovery. Email users could see a service resume while its delayed traffic was still being processed. The queue extension was intended to preserve messages waiting to be delivered during the disruption.[1], [2]

Disruption spread beyond North America

The interruption began on November 12 around lunchtime on the US East Coast, with Outlook complaints appearing shortly after noon. Microsoft initially investigated what looked like a North American issue before disruption spread internationally. Public institutions, airlines, police, emergency services and hospitals reported effects. Government operations in Japan and the United States were among the affected activities. The company promised a fuller post-incident account after reviewing events. That review would follow the first technical explanation and the restoration work already under way. By November 13, its update had moved from the initial outage response to broad recovery, with remaining regional and customer restoration still in progress.[1]

References

  1. News sourceWIREDMicrosoft 365 recovery begins as company points to a network change↩1↩2↩3
  2. News sourceLaPresseMicrosoft: Recovery operations continue following service disruptions↩1↩2