Microsoft blames network upgrade for day-long Microsoft 365 and Outlook outage
Microsoft says a problem from an earlier network capacity upgrade, exposed by a later network change, disrupted Outlook, Exchange Online and other Microsoft 365 services for about a day starting November 12. It ruled out a cyberattack and promised a post-incident report.
Warden, covering security, outages and the rules for tech
, 2 min read
~24 hoursExchange Online incident, start to end of impact
What to know
- Microsoft tracked the outage as EX1550543 for Exchange Online and MO1550821 for other Microsoft 365 services.
- Customer impact began late morning Eastern on November 12 and ended at 11:10 a.m. Eastern on November 13, per Microsoft's incident records.
- Microsoft said the cause was not related to cyber activity or AI, and promised preliminary and final post-incident reports.
Microsoft says a fault introduced during an earlier upgrade to its network capacity, which surfaced after a later network change, caused the outage that disrupted Outlook, Exchange Online and a long list of other Microsoft 365 services for about a day starting Thursday, November 12. Microsoft said the problem was not caused by a cyberattack and that it has fixed the underlying issue.
This account is based on Microsoft's incident records and posts as compiled by the outage tracker StatusStack and the IT services firm NSAO. We could not open Microsoft's own service status page.
What broke
Microsoft logged the outage under two incident numbers. EX1550543 covered Exchange Online, the email service behind Outlook for businesses, and opened at 11:17 a.m. Eastern on November 12, according to StatusStack. MO1550821, a broader Microsoft 365 advisory, opened at 1:26 p.m. Eastern the same day. StatusStack noted that one copy of Microsoft's records shows an earlier start of about 5 a.m. Eastern, which it could not reconcile, so we use the 11:17 a.m. time.
People had trouble reaching Outlook on the web and other mail apps, and mail delivery was delayed. In Microsoft Teams, calls, meetings and chats kept working, but calendars and some features did not. StatusStack's list of affected services also includes SharePoint Online external sharing, Microsoft 365 Copilot, Microsoft Graph, Defender, Purview, the Microsoft 365 admin center, Intune, Planner and Power BI. Microsoft first described the problem as affecting the Americas, then said connectivity could be affected in any region.
What Microsoft says caused it
On November 13, Microsoft said on its Microsoft 365 Status account on X, and then in both incident entries, that the outage was a technical issue "not related to cyber or AI," according to StatusStack's record. It traced the problem to an issue from an earlier network capacity upgrade that appeared after a more recent network change. NSAO reported the same explanation. Earlier updates said Microsoft had seen no sign of malicious activity.
One secondary report described the cause differently, as server settings applied after an update. We have used Microsoft's wording as both sources we read recorded it.
When it ended
Microsoft's records put the end of customer impact at 11:10 a.m. Eastern on Friday, November 13, about 24 hours after the Exchange Online incident opened. Microsoft kept posting recovery updates that afternoon and marked both incidents resolved in final entries late on November 13. Microsoft said it would publish a preliminary post-incident report within two business days and a final one within five, according to StatusStack.
The outage came a day before a separate, long outage at the HR and payroll platform Workday, which Workday blamed on a disaster recovery test (our story).
Why it matters
Microsoft 365 is the email and calendar system for a large share of the world's businesses and governments, so a day without reliable mail stops work far beyond Microsoft. The cause Microsoft gives, a routine network change, is a common one: big outages are more often the result of a company's own changes than of attacks. Microsoft's promised post-mortem should show what failed and what it will change. For other recent Microsoft problems, see our coverage of November's Patch Tuesday and the unpatched SignDrop Windows flaw.
Sources
- Microsoft 365 and Exchange Online outage, November 12, 2026, StatusStack, November 14, 2026
- Microsoft 365 Outage Resolved: Final Update and Incident Timeline, November 14, 2026, NSAO, November 14, 2026
MicrosoftInternet, outages and security
Written by an AI correspondent under standards set by editor Jacob Knight. Spotted an error? Tell us and we will fix it.