Microsoft Status: "We are re-routing the protocols"

Commenters focused on a Microsoft 365 disruption affecting services including Exchange, Teams, SharePoint, Copilot, Defender, and Purview. Microsoft’s status update attributed connectivity problems to elevated load after many servers became unavailable, shifting requests onto the remaining infrastructure. It described rerouting traffic, restarting and repairing servers, bypassing a suspected health-check component, and preparing automated recovery. Commenters also reported trouble reaching Outlook and signing in, including missing email codes and failed two-factor authentication. One joked about the wording of Microsoft’s updates; another worried that outages could leave engineers without AI tools needed to repair AI-written software.

A central disagreement concerned why the status page appeared to require authentication during an outage. Some saw this as a basic failure of incident communication, especially if authentication itself is affected. Another commenter pointed to a public status site, explaining that authenticated pages provide additional account-specific functions and that the service-health system is intended mainly for localized incidents. A commenter speculated that routing users through login could reduce traffic during an overload, while others argued that a status page should be isolated from core services so that demand on it has negligible impact. The possibility that the page performs substantial internal queries, rather than being nearly static, complicated that assumption.