From 12 to 14 November 2026, Outlook and other Microsoft 365 services were disrupted worldwide. The consequences went beyond the office: in a hotel swimming pool in Brühl, an automatic system dosed too much chlorine into the pool. The alarm email of the safety system did not arrive because of the outage, and the fault went unnoticed. According to media reports, 15 bathers were injured.¹
The case shows a common pattern: the system is monitored, but the only alarm path depends on a single provider.
Why fault messages by email alone are not enough
- If the email provider fails, all alarms fail at the same time, without anyone noticing.
- An email does not wake anyone at night.
- The sender usually cannot see whether an alarm email has arrived.
After the outage, Bitkom president Ralf Wintergerst warned: “Anyone who becomes one-sidedly dependent on central digital technologies risks production losses and competitive disadvantages in an emergency.”²
Checklist: is your alerting fail-safe?
- Which path does the alarm take out of the system? Does it run via the same mail server as your office email?
- Is there a second, independent path, for example SMS or a call via another provider?
- Does the alarm reach the on-call team at night too, i.e. by call or SMS instead of email only?
- Does it reach more than one person?
- Is it tested regularly whether an alarm really arrives?
- Does anyone notice if the system stops reporting altogether?
How to set up a second alarm path
The simplest solution supplements the existing alarm email instead of replacing it: the system also reports to an independent service that alerts by SMS and call. With TeamMessage, a second recipient address or an interface call is all it takes. More about the second alarm path →
Sources
- heise online, 14.11.2026: Microsoft-Cloud-Ausfall führte zu 15 Verletzten im Phantasialand; Schwarzwälder Bote, 16.11.2026, S. 7
- Schwarzwälder Bote, 16.11.2026, S. 7 (dpa), quote translated
Published: 17.11.2026