20 November 2026

Microsoft Identifies Hidden July Software Bug Behind Global Microsoft 365 Outage

Microsoft Identifies Hidden July Software Bug Behind Global Microsoft 365 Outage

Microsoft has identified a previously undetected software defect introduced in July 2026 as a major cause of the global Microsoft 365 disruption that affected businesses and users on November 12 and 13.

According to the company's preliminary investigation, the defect remained unnoticed for more than three months before a combination of increased network traffic and reduced server capacity triggered widespread failures across its networking infrastructure.

The incident disrupted access to several widely used services, including Outlook, Exchange Online and Microsoft Teams, leaving businesses and organisations in multiple countries facing interruptions for nearly 24 hours.

More Than 80% of Affected Servers Became Unresponsive

Microsoft's preliminary post-incident report revealed that over 80% of the affected networking gateway servers became unresponsive within less than two hours after the problem escalated.

The company identified three main factors behind the disruption: a hidden software defect, a change in network traffic following a Microsoft Teams failover and an existing reduction in available server capacity.

The software problem originated from a change deployed in July specifically for Microsoft's Microsoft 365 networking gateway infrastructure. Under certain operating conditions, the defect caused internal processes to compete for system resources, eventually exhausting CPU and memory capacity.

Although the update had been distributed globally without immediate problems, Microsoft's testing procedures did not reproduce the conditions that eventually triggered the failure.

Teams Traffic Shift Increased Pressure on Microsoft's Network

Another important factor involved a network failover approximately 15 hours before the outage.

Microsoft Teams shifted traffic from an alternative networking gateway to the primary gateway, which also supported Exchange Online services. This increased the workload and changed the traffic patterns handled by the infrastructure.

At the same time, an unrelated technical issue had already taken approximately 14% of the affected gateway's server capacity offline.

While neither situation was independently considered sufficient to cause a major disruption, their combined impact exposed the previously hidden software defect.

As servers began failing, Microsoft's automated systems redirected requests towards other available infrastructure. However, the additional traffic placed further pressure on the remaining servers, creating a chain reaction that spread across the network.

Why Microsoft's Recovery Efforts Took Nearly 24 Hours

Restoring the affected infrastructure proved more difficult than initially expected.

Microsoft found that simply restarting the unresponsive servers did not solve the problem because accumulated requests continued to overwhelm them once they returned to operation.

The company also faced difficulties using its usual rollback procedures because the defective software change had been deployed several months earlier rather than immediately before the incident.

Engineers eventually worked on correcting the affected software, restoring server capacity and gradually bringing the infrastructure back online.

The disruption affected businesses and organisations worldwide, including users in the UAE who rely on Microsoft's cloud-based productivity and communication services.

Microsoft Reviews Testing and Infrastructure Safeguards

The incident has highlighted the importance of testing software under different hardware configurations and network conditions.

Microsoft acknowledged that its existing testing processes failed to reproduce the conditions associated with the defect. The issue was more likely to occur on newer, higher-core-count servers, while laboratory testing primarily used less powerful hardware.

The company is reviewing its infrastructure safeguards, traffic management procedures and monitoring systems to reduce the likelihood of similar cascading failures.

Microsoft's preliminary findings also indicate that its normal mechanisms for isolating infrastructure problems across different regions did not prevent the disruption from spreading.

The company is expected to provide further details and corrective measures in its final incident report.

The outage serves as a reminder of how heavily businesses worldwide depend on cloud-based platforms and how a hidden technical weakness can affect essential digital services on a global scale.

END.