On November 12, 2026, Microsoft experienced a global service outage that affected millions of users around the world. Let’s take a look at what happened.
What was affected?
Microsoft 365 is a cloud-based productivity suite that includes online versions of Word, Excel, PowerPoint, Outlook, and Teams. It also provides online services for email, file storage, collaboration, security, and AI-powered assistance. These and other widely used Microsoft services were impacted when the outage occurred. Additionally, as the incident expanded, users reported problems with SharePoint Online, OneDrive, and Intune. In many cases, people could not access email, schedule meetings, connect to collaboration tools, or use AI-powered features that relied on the affected infrastructure.
What was the cause?
At first, Microsoft began investigating reports of mailbox connectivity issues with Exchange Online. Their engineers initially suspected a higher than normal infrastructure load, but further analysis showed that several backend servers had strangely become unavailable. That left the remaining systems handling more traffic than they were designed to manage, creating service slowdowns and outages across multiple products on their platform.
As the investigation continued, they determined that the incident was not caused by a cyberattack or by AI misalignment, but rather by a hidden bug that was part of a Microsoft 365 fix for network gateway servers that went into effect in July. Under certain network traffic conditions, this bug can cause a problem called “lock contention” where competing tasks are forced to wait for access to shared resources. This can cause delays in responding to connection requests (such as when someone is trying to check their email), which then continue to pile up. The end result is that the server runs out of memory and then stops responding entirely.
So, after months of sitting idle, the bug was triggered when some network traffic for Microsoft Teams was moved from an alternative gateway to the primary gateway shared with Exchange Online. Once servers started going offline, the issue was then made worse when automated systems—in an attempt to balance the load being caused by the outages—spread the network traffic to other healthy servers. This created the exact same conditions to trigger the bug in those servers, which then caused a cascading failure that spread across Microsoft's networking infrastructure.
How was it resolved?
Restoring service was not as simple as restarting a few servers. Engineers first had to develop an update that would return Windows connection handling to its earlier working state from before the bug was introduced. Then they systematically removed servers from the network in large groups, applied the change, restarted them, and then redeployed them gradually. Additionally, they added more fresh, bug-free servers to the network to help chew through the load. They also extended the delivery window for emails to prevent the huge swaths of queued messages from bouncing and thus exacerbating the issue.
By the end of the recovery effort, Microsoft reported that services had been restored and stated that it had addressed the underlying issue. The company also said it would continue reviewing the incident and sharing post-incident findings to reduce the likelihood of similar failures in the future. Of course, this is just one of the many large-scale outages making the news lately, but we’re still waiting for more info surrounding those other incidents before we can talk about them in detail.
Steve Shannon has spent his entire professional career working in tech. He is the IT Director and Lead Developer at PromoCorner, where he joined in 2018. He is, at various times, a programmer, a game designer, a digital artist, and a musician. His monthly blog "Bits & Bytes" explores the ever-evolving realm of technology as it applies to both the promotional products industry and the world at large. You can contact him with questions at steve@getmooresolutions.com.