November 16, 2026
Three-small-bugs-combined-to-kill-Microsoft-365.jpg

A hidden flaw in Microsoft’s cloud portal, down since July, was to blame for one of the biggest outages in the company’s history last week. A preliminary post-incident report (PIR) released by the company describes how the latent error, traffic changes, and reduced server capacity combined to take much of the Microsoft 365 and Exchange infrastructure offline late last week. Microsoft’s report lists the final status of the incident as “a technical issue not related to cyber or AI/agents.”

Microsoft’s preliminary report places the outage between November 12 at 16:20 UTC and November 13 at 16:10 UTC, just under 24 hours in total, and additional monitoring was maintained for all affected systems until November 14.

The outage began on November 12 and quickly spread to businesses and public offices that rely on Microsoft’s cloud and email exchange infrastructure. The outage is covered in Microsoft Incident IDs EX1550543 and MO1550821. You need Microsoft 365 administrator credentials to see the full report on company status pages, but Office Watch has reproduced the preliminary report and the University of Pennsylvania maintains an archive of Microsoft service status updates.

A perfect storm

Microsoft attributes the outage to three factors. A change implemented in Microsoft’s cloud gateway starting in July created a bug where, under certain conditions, CPU and memory resources could be exhausted and become unresponsive. Microsoft maintains that the flaw was never discovered in pre-release testing because the hardware used was less powerful than some systems already deployed in production, where a higher number of CPU cores in newer machines apparently contributed to the crash.

The second factor was server load. Microsoft said that “traffic changes during standard network maintenance and updates exposed a latent bug.” The company maintains two independent gateway systems to access Microsoft 365 for added resiliency. If one system has problems and users cannot get through the front door, the other opens to keep traffic flowing. According to the report, approximately 15 hours before the outage, Teams traffic was diverted from the alternate gateway to the primary one, where access to Exchange Online is maintained. The switchover was a standard failsafe measure, but it left the gateway handling more traffic, with a different mix of requests than before. As requests continued to pile up, the affected servers exhausted their capacity and rejected new connection requests.

Avatar photo
Written by

Jhon Smith

Info Vitalis is a content writer specializing in creating clear, concise, and engaging articles. With experience in health, lifestyle, technology, and current events, Info Vitalis aims to provide readers with useful and easy-to-understand information.

Leave a Reply

Your email address will not be published. Required fields are marked *