BTC $64,278.32 -1.58%
ETH $1,795.72 -1.40%
BNB $588.22 -1.21%
XRP $0.9432 -2.23%
SOL $70.79 -1.24%
TRX $0.3022 -1.72%
DOGE $0.0581 -0.72%
ADA $0.1512 -1.20%
BCH $204.88 -1.50%
LINK $9.07 -1.52%
HYPE $66.69 -1.56%
AAVE $108.64 +2.44%
SUI $0.7158 -1.18%
XLM $0.1369 -1.29%
ZEC $885.30 -2.48%
AAPL $358.25 +0.35%
AMZN $265.14 +0.58%
GOOGL $294.52 +0.58%
MSFT $527.23 +1.20%
META $636.40 -0.08%
NVDA $159.78 -0.67%
TSLA $385.06 -0.58%
SNDK $830.91 -2.72%
INTC $56.82 -1.93%
SPCX $139.72 +1.67%
MU $738.31 -2.54%
AMD $508.73 -2.70%
BTC $64,278.32 -1.58%
ETH $1,795.72 -1.40%
BNB $588.22 -1.21%
XRP $0.9432 -2.23%
SOL $70.79 -1.24%
TRX $0.3022 -1.72%
DOGE $0.0581 -0.72%
ADA $0.1512 -1.20%
BCH $204.88 -1.50%
LINK $9.07 -1.52%
HYPE $66.69 -1.56%
AAVE $108.64 +2.44%
SUI $0.7158 -1.18%
XLM $0.1369 -1.29%
ZEC $885.30 -2.48%
AAPL $358.25 +0.35%
AMZN $265.14 +0.58%
GOOGL $294.52 +0.58%
MSFT $527.23 +1.20%
META $636.40 -0.08%
NVDA $159.78 -0.67%
TSLA $385.06 -0.58%
SNDK $830.91 -2.72%
INTC $56.82 -1.93%
SPCX $139.72 +1.67%
MU $738.31 -2.54%
AMD $508.73 -2.70%
first_img

Microsoft: The Microsoft 365 outage was caused by three factors

2026-11-16 15:12:18

Microsoft Copilot, Agents, and Platform Executive Vice President Charles Lamanna explained the preliminary cause of the Microsoft 365 outage on November 12 and stated that more complete details can be found in the Microsoft 365 Admin Center. Lamanna expressed the company's deep apologies for the impact the outage had on the normal business and operations of all customers. He mentioned that the outage that day was caused by three factors, which led to a global disruption of the network gateway affecting multiple Microsoft 365 services.

Lamanna stated that the first factor was a latent defect that caused the servers to overload and become unresponsive under specific load conditions due to internal process lock contention, rendering the machines unavailable. This defect originated from a fix prepared specifically for the Microsoft 365 network gateway servers, and both the defect and the fix are not applicable to broader Windows deployments. The related behavioral change began deployment in July of this year, was securely deployed, and completed global coverage within weeks, during which no issues were observed; this change had been deployed globally for over three months without causing any impact.

Lamanna also mentioned that the second factor was an increase in load, which raised the likelihood of the network gateway encountering the aforementioned contention. Microsoft 365 maintains two independent and heterogeneous network gateway systems to isolate and ensure high availability, allowing multiple services to failover between the two systems during an outage; such failovers are part of normal operations and standard resilience measures. The third factor was that nearly 14% of the network gateway server capacity went offline almost simultaneously due to an unrelated issue from the previous day, which was planned to be restored through routine maintenance and health processes; the service had sufficient capacity margin, and the isolated capacity drop did not cause any impact. Lamanna stated that the combination of increased load and decreased server capacity triggered the latent defect introduced in July.

Interpretation
app_icon
ChainCatcher Building the Web3 world with innovations.