Monday 16 November
Global

Your region, kept on this device.

Microsoft 365 recovers after 24-hour outage caused by a bad update

Severity
Low
Sources
1

attributes a roughly 24-hour outage to a faulty update that crashed servers globally, and explicitly rules out a cyberattack or AI as the cause. The article gives no CVE, affected build numbers or technical root-cause detail. Defenders should check Microsoft's service health communications for incident details and confirm that their own dependencies on Microsoft 365 have recovered.

For security analysts · Written by AI from 1 source · Wrong?

What to do

  1. No action needed.

Written by AI from the sources, checked against them

Full story timeline · 1 update

  1. Fri 13 NovemberMicrosoft 365 Crawls Back to Life After a 24-Hour OutageWired (Security)

Who reported · 1 outlet

Wired (Security)

Who and what is in it

Companies

Report a problem