Share๐•inWA

Microsoft 365 Outage: The July Bug That Broke Outlook

TechorCoffee
TechorCoffee
Contributing Writer

Published (Updated )

Microsoft 365 Outage: The July Bug That Broke Outlook

Microsoft 365 Outage: The July Bug That Broke Outlook

Quick answer

What happened on November 12

It started as a bad morning for millions of workers. On Thursday, November 12, 2026, Outlook stopped working for users around the world. Emails would not send, inboxes would not load, and calendars were unreachable. Microsoft first flagged the problem at 11:24 pm IST on November 12, but by then the outage was already spreading fast. Within hours it had reached more than 70 countries, and Downdetector recorded between 120,000 and 130,000 reports at the peak. The outage lasted more than 24 hours for many users. Outlook was hit hardest, but it was far from the only service affected:

The three factors that combined

Microsoft's explanation, shared on November 16 by Charles Lamanna, executive vice president for Copilot, Agents and Platform, in a post on X, is that no single failure caused the outage. Three separate factors combined at the worst possible moment.

FactorWhat happenedWhy it mattered
A latent software defectA fix for Microsoft 365 networking gateway servers introduced lock contention in an internal processServers became overwhelmed and unresponsive under certain load
A Teams failoverAbout 15 hours before the outage, Teams moved from its alternative gateway to the primary gatewayThe primary gateway, which also supports Exchange Online, took on extra load
Lost gateway capacityNearly 14% of gateway server capacity was already out of serviceThe system had far less headroom than usual when the defect struck
Any one of these on its own might have been manageable. Together, they were enough to bring down one of the world's biggest cloud platforms.
Lamanna also apologised for the disruption, acknowledging how much the outage had cost users and businesses. Microsoft tracked the incident under the IDs MO1550821 and EX1550543.

The July bug at the heart of it

The most striking part of the explanation is how long the defect had been in place. The faulty code came from a fix prepared specifically for Microsoft 365 networking gateway servers, and it began rolling out in July 2026. It then ran in production around the world for more than three months without causing any visible impact. Nothing went wrong in July, August, September or October. The defect was latent โ€” present in the code, but only triggered under particular conditions. The problem was lock contention inside an internal process. In simple terms:

Why testing missed the bug

One of the first questions after any outage like this is why testing did not catch the problem. Microsoft's answer is revealing: the load testing focused on weaker hardware, while the defect is worse on newer machines with more cores. That sounds counterintuitive. Faster hardware should handle more load, not less. But lock contention behaves differently:

Why Outlook stayed down longest

Not every Microsoft 365 service recovered at the same speed, and the reason comes down to failover โ€” the ability to switch to a backup when the main system fails. Teams, OneDrive, SharePoint and the Office apps were able to fail over away from the faulty gateway. Once they moved, they recovered sooner, and many users saw those services come back while Outlook was still down. Exchange Online could not make the same switch. It had no failover path off the affected gateway, so Outlook stayed tied to servers that were unresponsive. That is why email was the last thing to return for many users, and why the outage felt, for most people, like an Outlook outage above all else. At the worst point, more than 80% of the networking gateway servers were unresponsive. With that much of the gateway fleet down, and Exchange Online unable to move elsewhere, there was no quick workaround. The only real fix was to remove the faulty code.

How Microsoft fixed it

Once engineers identified the defect, the fix itself was straightforward: revert the code path to the previously known good state. In other words, undo the July change and go back to the version that had worked before. Getting there took time. According to Microsoft's account:

What the outage means for businesses

For the companies that rely on Microsoft 365, the November 12 outage was a reminder of how much depends on a single platform. When Outlook, Teams, OneDrive and SharePoint all go down together, there is often no easy fallback. A few practical lessons stand out:

What users should do now

For most users, there is nothing to fix. The services are back, and no action is needed on individual accounts. But a few checks are worth doing after any outage of this size:

What to watch next

The story is not quite finished. Microsoft's full Post-Incident Review was due later in the week of November 16, and that document should answer the questions Lamanna's post left open:

The bottom line

Microsoft's explanation of the November 12 outage is unusually specific, and unusually honest about how long the problem had been hiding. A software defect introduced in July ran silently for more than three months, then combined with a Teams failover and a 14% capacity shortfall to knock out more than 80% of the networking gateway servers. Outlook stayed down longest because Exchange Online, unlike Teams and OneDrive, could not fail over to a healthy gateway. The fix was a revert to known-good code, but it took about 30 hours to identify and apply, and 15 more hours to roll out. The full Post-Incident Review should fill in the remaining details. Until then, the message for users is simple: this was not an attack, it was a chain of failures โ€” and the chain started with a fix that nobody knew was broken.

FAQs

What caused the Microsoft 365 outage on November 12, 2026?

Microsoft says three factors combined: a latent software defect from July 2026 that caused lock contention in its networking gateway servers, a Teams failover onto the same primary gateway about 15 hours earlier, and nearly 14% of gateway capacity already being out of service.

When did the Microsoft 365 outage happen and how long did it last?

The outage began on Thursday, November 12, 2026, with Microsoft first flagging it at 11:24 pm IST that day. It lasted more than 24 hours for many users, and the fix took about 30 hours to identify and apply, plus around 15 more hours to roll out.

Why was Outlook down longer than Teams and OneDrive?

Teams, OneDrive, SharePoint and Office apps could fail over away from the faulty networking gateway and recovered sooner. Exchange Online could not switch gateways, so Outlook stayed down until the faulty code was reverted.

Was the Microsoft 365 outage a cyberattack?

No. Microsoft has said there was no malicious activity involved and the outage was not a cyberattack. The cause was a software defect combined with a failover and a capacity shortfall.

What was the July bug behind the outage?

The defect came from a fix prepared for Microsoft 365 networking gateway servers, first deployed in July 2026. It caused lock contention in an internal process, making servers unresponsive under certain loads. Load testing missed it because tests focused on weaker hardware, while the defect is worse on newer machines with more cores.

How many people were affected by the outage?

The outage spread to more than 70 countries, with 120,000 to 130,000 reports at the peak on Downdetector. It affected Outlook, Exchange Online, Teams, OneDrive, SharePoint, Office apps, Copilot and other services, including government offices, courts and hospitals.

Was this article helpful?

TechorCoffee

Written By

TechorCoffee

Contributing Writer

TechorCoffee is a technology reporter and software creator writing reviews and tutorials for TechOrCoffee.

Comments (0)

Sort by:

Leave a Comment

Loading comments...

Read Next