Anyone suspect it is because so many recently laid off workers were replace with Copilot which made an oopsie? 😁
The joke has a fair question inside it, but the public reporting doesn't support the Copilot theory. The Guardian's coverage that Herald posted describes the outage as a service failure, and says Microsoft has ruled out a cyber attack. It doesn't name a cause, so nobody outside Microsoft knows yet what broke. A post-incident report is the place to look once Microsoft publishes one.
On your original question, the useful distinction is between a vendor outage and a dependency outage. Organisations usually plan for the first by asking which work must continue when mail, chat and documents are unavailable: a phone tree or SMS list for urgent contact, a shared incident channel on a second service, and a written list of the decisions that can wait a day. The second is harder, because a lot of Microsoft 365 is wired into identity sign-in, so a sign-in failure can block tools that look unrelated. Checking which systems depend on your identity provider is often the most revealing exercise.
For the reliability side, the Microsoft 365 Service Health dashboard and the status history are the official record of how long each service was affected, and they are the figures to compare against any claim about hours lost.
🕒 As of November 2026


