Microsoft 365 remains partially disrupted following an outage that began November 12, affecting Exchange Online, Teams, and SharePoint. As of the November 13 midday update, Microsoft reported no restoration time and no evidence of malicious activity, despite servers failing under load Thursday night. Infotech advises CIOs to verify critical workflows and document service impacts for potential SLA claims.
The Microsoft 365 outage that began on November 12 disrupted Exchange Online in the Americas and hit Teams, SharePoint, Copilot and Defender, with servers failing again under load Thursday night and no restoration time given as of the November 13 midday update. A multi-service cloud outage lasting more than a day raises reputational and reliability concerns and could generate SLA claims. No financial figures or evidence of malicious activity are given, and availability was improving, which limits the likely price effect.
- ▼ Outage began November 12 with Exchange Online mailbox access failures in the Americas
- ▼ Servers that had returned to service failed again Thursday night under load; Microsoft added capacity and rolled back a recent network change
- ▲ Availability was improving as of November 13, with core Teams messaging, meetings and direct SharePoint file access largely operational
- ▲ Microsoft reported no evidence of malicious activity