Cloud Computing and Data Centers

Preliminary report reveals details of Microsoft 365 outage caused by hidden bug and traffic changes

Microsoft issued a preliminary report explaining the causes of the Microsoft 365 and Exchange service outage, which resulted from the interaction of a hidden bug in the cloud computing gateway with traffic changes and a lack of operational capacity.

2026-11-16
3 min read
10 views
certi.news
Preliminary report reveals details of Microsoft 365 outage caused by hidden bug and traffic changes

Microsoft has released a preliminary incident report (PIR) revealing the causes that led to one of the largest outages in the history of its cloud services, which affected a large portion of the Microsoft 365 infrastructure and Exchange email services last November. The disruption lasted for nearly 24 hours, and the company confirmed in its report that the issue was purely technical and not related to cyberattacks or artificial intelligence tools.

Factors that combined to cause the outage

Microsoft attributed this widespread outage to the intersection of three main factors that resulted in the exhaustion of cloud gateway server resources and their freezing:

  • Hidden software glitch: A change was deployed to the company's cloud computing gateway in July, resulting in a latent bug that causes CPU and memory resources to be depleted under certain conditions. This flaw was not discovered during pre-launch testing due to differences in the hardware power used.
  • Traffic shifts: Standard maintenance work led to the redirection of Teams application traffic to the primary gateway that processes Exchange Online requests, placing an additional burden and a new mix of requests that led to the rejection of new connections.
  • Lack of operational capacity: The gateway server fleet was operating at 14 percent less capacity than optimal conditions, and the lost safety margins would have been sufficient to absorb the demand had the other factors not overlapped.

What delayed the recovery?

Engineers faced difficulty in restarting the affected gateway servers, as restarting them faced massive queues of pending requests, which reactivated resource exhaustion as soon as they returned to service. Furthermore, software rollbacks of the old update were not effective due to the embedded bug, necessitating gradual interventions to apply targeted fixes, expand operational capacity, and adjust delivery queues for delayed emails.

What does this mean for users?

This malfunction caused widespread paralysis for businesses and organizations reliant on Microsoft's cloud services, highlighting the fragility of complex infrastructures when multiple operational factors intersect with latent software bugs. The company intends to publish its comprehensive final report to clarify the reasons for the failure of regional isolation systems and additional corrective measures to prevent the crisis from recurring.

News source
c
Author

certi.news

In the same category

You may also like

View all news