{"slug": "microsoft-explains-last-week-s-365-outage", "title": "Microsoft Explains Last Week's 365 Outage", "summary": "Microsoft traced the Microsoft 365 outage that disrupted Outlook, Teams, Copilot, SharePoint and OneDrive for just under 24 hours — from 4:20 PM UTC on November 12 to 4:10 PM UTC on November 13 — to three simultaneous problems, according to a preliminary post-incident report. The main cause was a fix for Microsoft 365 gateway servers that introduced lock contention in an internal Windows process, exhausting CPU and memory under certain loads and going unnoticed for over three months because Microsoft's load testing used weaker machines that could not stress the fix properly. Teams failing over onto the primary gateway it shares with Exchange Online worsened the problem, and at the worst point more than 80% of servers were unresponsive.", "body_md": "Microsoft has now explained the recent [Microsoft 365 outage](https://www.techpowerup.com/354799/microsoft-365-outage-enters-second-day-as-outlook-and-teams-struggle-to-recover) in a [preliminary post-incident report](https://www.365fanatic.com/wp-content/uploads/2026/11/PostIncidentReport.pdf). According to Microsoft, customers were impacted for just under 24 hours, from 4:20 PM UTC on November 12 to 4:10 PM UTC on November 13. The outage prevented many users from accessing their mailboxes in Outlook and delayed email delivery. Moreover, Microsoft Teams, Copilot, SharePoint, and OneDrive were all affected in some way, which is expected since these services all have features that rely on Exchange Online.\n\nThe company has traced the outage to three problems that hit Microsoft at the same time. The main culprit is said to be a fix that had been prepared specifically for Microsoft 365 gateway servers. This particular fix, which introduced lock contention in an internal Windows process that exhausted CPU and memory under certain loads, went unnoticed for over three months. That was probably because Microsoft's load testing used weaker machines that couldn't stress the fix properly. Teams also failed over onto the primary gateway it shares with Exchange Online, which worsened the problem. Traffic then shifted to remaining servers, which buckled under the extra load. Apparently, more than 80% of the servers were unresponsive at the worst point of the outage.", "url": "https://wpnews.pro/news/microsoft-explains-last-week-s-365-outage", "canonical_source": "https://www.techpowerup.com/354904/microsoft-explains-last-weeks-365-outage", "published_at": "2026-11-16 18:37:59+00:00", "updated_at": "2026-11-16 18:51:20.145927+00:00", "lang": "en", "topics": ["ai-products"], "entities": ["Microsoft", "Microsoft 365", "Outlook", "Microsoft Teams", "Copilot", "SharePoint", "OneDrive", "Exchange Online"], "also_reported_by": [], "alternates": {"html": "https://wpnews.pro/news/microsoft-explains-last-week-s-365-outage", "markdown": "https://wpnews.pro/news/microsoft-explains-last-week-s-365-outage.md", "text": "https://wpnews.pro/news/microsoft-explains-last-week-s-365-outage.txt", "jsonld": "https://wpnews.pro/news/microsoft-explains-last-week-s-365-outage.jsonld"}}