Microsoft Says a July Bug Caused a Nearly 24-Hour Microsoft 365 Outage
A latent software defect, a Teams failover and reduced gateway capacity combined to knock Outlook, Exchange Online and other Microsoft 365 services offline from 18:20 CAT on 12 November until 18:10 the next day.
REDMOND, United States – Microsoft said a software bug introduced in July, combined with a surge in traffic after a Teams failover and reduced server capacity, caused a nearly 24-hour Microsoft 365 outage. The disruption began at 18:20, Africa/Gaborone time, on 12 November and ended at 18:10 the following day, when Microsoft said active customer impact had stopped.
Highlights
- The outage ran from 18:20 CAT on 12 November to 18:10 CAT on 13 November.
- Microsoft said more than 80% of its networking gateway servers became unresponsive.
- A July software bug was triggered after a Teams failover and reduced capacity.
- Exchange Online could not fail over, leaving many users unable to reach mailboxes.
- Charles Lamanna said Microsoft was “deeply sorry” for the impact on customers’ operations.
The outage hit Outlook, Exchange Online, Teams, Copilot and other Microsoft 365 services used by businesses, governments, schools and health providers. Users could not open mailboxes and message delivery was delayed. Microsoft later described a cascading failure that, at its lowest point, left more than 80% of its Microsoft 365 networking gateway servers unresponsive.
In a preliminary post-incident report in the Microsoft 365 Admin Center, summarised on 16 November, the company said three problems combined. A previously undetected software bug had been introduced in July in an update written for Microsoft 365 networking gateway servers. The update had run worldwide for more than three months without obvious harm. Microsoft said its usual load tests missed the defect because laboratory traffic and hardware did not match production, where the problem was worse on machines with more cores.
About 15 hours before the outage, Microsoft Teams automatically failed over onto the networking gateway that also serves Exchange Online, increasing the load and changing traffic patterns. Microsoft said that kind of failover is a normal resilience step. Almost 14% of the gateway’s server capacity was already offline because of an unrelated issue from the previous day. Microsoft said the service still had enough spare capacity for that reduction on its own, but the extra load plus the missing capacity triggered the July bug.
“In less than two hours, the previously unknown defect was encountered across our fleet and rendered them unresponsive. At its lowest, more than 80% of servers were unresponsive,” Microsoft said in the preliminary report.
Safeguards meant to stop a failure spreading between regions did not contain it, the company said, and the disruption became global. Teams, OneDrive and SharePoint could move to alternative infrastructure and recover earlier. Exchange Online could not make the same switch, so many customers stayed locked out of email. Restarting affected servers was slow to help, because they were quickly overwhelmed again by queued traffic.
“Taken together, the increased load and the reduced server capacity, caused the network gateway to encounter the latent bug from July. This caused requests to build up until servers ultimately stopped responding. This occurred during the peak window of traffic in the United States,” wrote Charles Lamanna, Microsoft’s executive vice president of Copilot, Agents and Platform, in a 16 November update.
“Recovery took longer than usual because as servers returned to service, they were immediately overwhelmed by waiting traffic and became unresponsive again,” he said.
What it means for operations
For companies that run mail, meetings and files on Microsoft 365, this was a core communications failure lasting almost a full working day into a second. Incident response that depends on Outlook or Teams will stall if those same services are down. Cached Outlook data, a second email or messaging channel, and a status-page watch that does not rely on the affected tenant are the practical checks. Microsoft said it has since added capacity, improved monitoring and put in safeguards to stop traffic redirection triggering a similar cascade. It also said a final post-incident report was still to come.
“We are deeply sorry for the impact to all our customers and recognize the impact that this has on their normal business & operations,” Lamanna said.
Microsoft said the incident was a technical failure, not a cyberattack and not caused by AI agents. On 13 November the company said the problem had been “introduced by an issue during an earlier network capacity upgrade that surfaced following a recent network change.”
The outage is a separate event from earlier Outlook search failures that disrupted enterprise mail workflows. What to watch next is the final post-incident report, and whether Microsoft’s new safeguards hold at the next peak. Officials later said a week of separate US outages, including this one, was not a coordinated cyberattack.
More from this series
- US officials say a week of outages was not a coordinated cyberattack
- FAA halted US departures for just over four hours after a network flood
- JPMorgan Chase software bug delayed payments across several US banks
- United Airlines resolved a system outage that delayed departing flights
- Microsoft said a July bug caused a nearly 24-hour Microsoft 365 outage
- Apple blamed an internal update for outages as officials ruled out a cyberattack
Sources
- BleepingComputer, 16 November 2026: Microsoft says months-old bug caused global Microsoft 365 outage
- ABC News, 16 November 2026: Microsoft identifies issues leading to global Outlook outage
- IT Pro, 16 November 2026: Microsoft 365 outage: Company exec lifts lid on the cascading failure that caused lengthy disruption
- BBC News, 13 November 2026: Microsoft says it is ‘deeply sorry’ for global outage after almost 24 hours of disruption
Written by
Tumisang Bogwasi
Tumisang Bogwasi, Founder & CEO of Brimco. 2X Award-Winning Entrepreneur. It all started with a popsicle stand.
