M365 Service Degradation (MO1550821) – Ongoing 8+ hours, Microsoft's initial fix failed
retained text
**TL;DR:** Exchange Online is degraded, taking down anything in M365 that talks to it (Teams calendars, Copilot, Purview, Defender portals, To Do, etc.). Core Teams chat/calls and direct SharePoint file access still work. Microsoft's first mitigation didn't take as expected. **Timeline & Current Status:** **Started:** Nov 12, 12:26 PM CST **8:58 PM CST Update:** Microsoft confirmed the change applied to improve serviceability *"is not taking as expected"* and they are identifying alternate workstreams to increase capacity due to *"sustained traffic management imbalances."* Next update at 9:30 PM CST. **Summary of Impact (Anything tied to Exchange/Purview):** **Exchange/Outlook:** Web, MAPI, EAS, and REST connections failing; delayed mail flow. **Teams:** Calls, group chats, and standard channels work. Calendar/scheduling, meeting edits, Live events, and creating/deleting private or shared channels are failing. **Copilot 365:** Chat won't load or can't access mail, calendar, or M365 files. **Security/Compliance:** Defender XDR portal pages won't load; Safe Links failing on URLs in Outlook/Teams; Purview (DLP, sensitivity labels, RBAC, eDiscovery) degraded. *(Note: For Power BI/Fabric PDF export failures, Microsoft notes removing the sensitivity label works as a workaround if your org policy allows it).* **Endpoints & Admin:** M365 Admin Center pages failing; Intune enrollment/check-ins intermittent; Windows 365 Cloud PCs configured with Purview Customer Key cannot connect. **Other Apps:** Planner, To Do, and Universal Print throwing errors. Anyone else still getting hammered with tickets over this, or are things starting to stabilize in your tenant? EDIT (9:36 PM CST): Microsoft just posted a new update on MO1550821 (still showing service degradation across Exchange Online, Teams, SharePoint Online, Defender XDR, and the M365 suite). They say they are investigating sustained traffic management imbalances by reviewing traffic flows and affected infrastructure to optimize routing and verify the reasons for the service failures. Next update is scheduled for 10:30 PM CST. EDIT (10:12 PM CST): Microsoft reports partial recovery across regions where it has adjusted traffic protocols, redistributed traffic, and applied strategic traffic-blocking measures. However, recovery is not yet sustained, and engineers are reviewing additional actions to stabilize overall infrastructure. Next update expected by 11:00 PM CST. EDIT (10:56 PM CST): Microsoft is seeing a surge in outbound call volume from routing services to backend servers caused by traffic rebalancing. Engineers are scaling up virtual machines to add capacity, though machines stuck in a bad state are currently preventing network changes from syncing as expected. Next update by 12:00 AM CST. EDIT (6:59 AM CST): Microsoft reports broader recovery in North America alongside sustained improvements in Europe and encouraging signals in Asia Pacific. Intermittent access issues and delayed email delivery persist while engineers clear mail queues and backlogs (an extended 48-hour email timeout window remains active to protect delayed messages). Microsoft also confirmed no evidence of malicious activity and will publish a Post-Incident Report once mitigated. Next update by 8:00 AM CST.
document fetched 2026-11-14 00:41 · canonical https://reddit.com/r/sysadmin/comments/1xuwz4w/m365_service_degradation_mo1550821_ongoing_8