Updated ETGet the DI Daily by Email

Technology news for e-commerce professionals, with our take on why it matters.

Developing story: The Microsoft 365 outage and the AI tools that depend on it

Microsoft traces global Microsoft 365 outage to a gateway bug dormant since July

Microsoft traces global Microsoft 365 outage to a gateway bug dormant since July
Image: ITdaily

At the low point more than 80% of gateway servers stopped responding, and Exchange Online had no second gateway to fall back on.

Source: ITdaily

Microsoft has shared a first analysis of the global Microsoft 365 outage that, according to ITdaily, left Outlook, Teams and Copilot unavailable or only partly available for almost 24 hours on November 12 and 13. The outage began at 17:17 CET on November 12 with Exchange Online, and Copilot Chat, Intune and Purview were also affected, ITdaily reported. Charles Lamanna, executive vice president Copilot, Agents & Platform at Microsoft, summarized the cause on X and apologized.

According to Lamanna, three factors coincided. A change to Microsoft's network gateway servers, rolled out in phases from July and running worldwide for more than three months, carried a latent lock contention fault that standard load tests missed because the test lab uses different traffic and hardware. About 15 hours before the outage, Teams moved from the alternative gateway to the primary one, which also serves Exchange Online, while almost 14% of the gateway's capacity was out of service from a separate problem the day before.

The fault spread across the whole server fleet in less than two hours, and at the low point more than 80% of servers stopped responding, ITdaily reported. Partition boundaries meant to stop such a chain reaction failed because of another problem the analysis does not describe. Teams, OneDrive, SharePoint and the Office apps recovered sooner by switching gateways, but Exchange Online cannot switch. A rollback did not help, so engineers built an update reverting the code path. Microsoft promised a full incident report by the end of the week.

Read the full article at ITdaily

Our take

Many commerce teams run support inboxes, supplier email and Copilot workflows on Microsoft 365, and this account shows one gateway fault can take them down together, with Exchange Online having no failover.

  • Ask Microsoft and your agent vendors how their tools behave when Microsoft 365 is unavailable.
  • Read the full incident report for what caused the partition failure, which the first analysis leaves unexplained.
  • Keep a fallback channel for customer and supplier contact.

Was our take useful?

Key takeaways

  1. The outage lasted almost 24 hours on November 12 and 13, ITdaily reported
  2. Microsoft says a gateway bug shipped from July surfaced under extra Teams load
  3. More than 80% of gateway servers stopped responding at the low point

More on this topic

Illustration for The Microsoft 365 outage and the AI tools that depend on it
Illustration: Digital Influence

Developing story8 postsUpdated Nov 18

The Microsoft 365 outage and the AI tools that depend on it

Microsoft 365 services including Outlook, Teams and Copilot have been disrupted since November 12, 2026.