Microsoft 365 went down worldwide: the single-vendor lesson for your business

Direct answer

On November 12, 2026, Microsoft 365 suffered a worldwide outage that started in Exchange Online, the email service behind Outlook for most organizations. Mailboxes stopped opening at around 16:17 UTC, and the fault spread to Outlook, Teams, SharePoint, Copilot and Microsoft Defender, among other services. Downdetector logged more than 120,000 Outlook problem reports at the peak, from 74 countries, and the outage was Microsoft's largest in 12 months according to the platform's data. Microsoft declared the service restored in the early hours of Saturday, November 14, about 24 hours after it began. The company traced the fault to a problem that surfaced during a network capacity upgrade and ruled out a cyberattack.

What went down, and in what order

The cause, according to Microsoft

What to do in your business this week

Note: this article summarizes Microsoft 365's public status updates (incidents MO1550821 and EX1550543), Downdetector data, and coverage by BusinessDay, Wire, Acorn Technology, KeyXplore and 4MIPS on November 13 and 14, 2026. Report figures come from Downdetector. The cause is Microsoft's published explanation; the detailed post-incident report is still pending.

Want AI that works for your business?

Message us on WhatsApp and let's talk about automation and AI agents for your business.

WhatsApp inicIA

Related articles

Frequently asked questions

What went down in Microsoft 365 on November 12, 2026?

The fault started in Exchange Online, the email service behind Outlook, and spread to Outlook, Teams, SharePoint, Microsoft 365 Copilot, Defender and other services that depend on email and calendars. Teams calls mostly kept working.

Was it a cyberattack?

Microsoft said it found no evidence of malicious activity, and executive Charles Lamanna ruled out a cyberattack. The company traced the fault to a problem that surfaced during a network capacity upgrade.

How long did the outage last?

Mailboxes began failing on Thursday, November 12, at around 16:17 UTC, and Microsoft declared the service restored in the early hours of Saturday, November 14, about 24 hours later, with the delayed email backlog processed.

What do I do if my business depends on Microsoft 365?

Map which parts of your operation depend on that vendor, define a backup channel for email and customers, write a one-page plan for the next outage, and set retry limits on AI agents that read email and calendars through connectors.