Testing Email, Teams, and Copilot Fallbacks Against an M365 Control-Plane Outage

On 15 November 2026 a reported global Microsoft 365 outage affected Outlook, Teams and Copilot. Microsoft linked it to a network upgrade issue and said it would publish a full review. The engineering problem isn't the outage itself — it's that most fallbacks turned out to share an identity provider, a DNS resolver and a tenant policy boundary with the primary path. This short walks through the testable model: - Control plane versus data plane, and why the fault pattern is warm sessions surviving while every cold start fails. Existing sessions buy you roughly one access-token lifetime, not a day. - Email, Teams and Copilot as separate dependency chains. Inbound mail often keeps landing while users cannot read it, and Copilot needs identity, a licence, Graph, the semantic index, permission trimming and tenant policy before it emits a token. - A lab-scoped harness in a disposable tenant with synthetic users: curl's --resolve flag pins one hostname to a blackhole address for a single request, modelling a DNS answer that resolves but never connects, without touching the machine's resolver. - A baseline probe captured before the drill, so you can tell a degraded probe from one that was always slow. Everything here assumes a tenant you own, users you created, and faults injected on your side of the wire. Do not fault-inject against Microsoft endpoints from a production network. Reporting summarised here is headline-level. Root cause, exact duration in UTC, regional scope beyond the reported US and Japan impact, and the causal status of the reported hotel warning-system failure all remain unconfirmed until Microsoft publishes its review. Full write-up: https://hackyjs.com/posts/testing-email-teams-and-copilot-fallbacks-against-an-m365-control-plane-outage

microsoft-365outageresilienceteamscopilot

Read the post →