Affiliate links on Android Authority may earn us a commission. Learn more.
Last week’s Microsoft 365 outage did more than keep people out of their inboxes. In Germany it played a part in a chemical incident that sent hotel guests to the hospital.
German public broadcaster WDR reported that on Friday, November 13, a fault in the automatic chlorine dosing system at Hotel Ling Bao pushed far too much chlorine into the hotel’s pool. The hotel belongs to the Phantasialand theme park in Brühl, near Cologne.
Its maintenance safety system detected the problem and sent an alarm, but the alarm went out by email. Because Microsoft’s Outlook and Exchange Online services were down at the time, the message never reached staff. Nobody knew anything was wrong until guests in the pool area started having trouble breathing.
Around 40 emergency responders were reportedly sent to the hotel. Fifteen people needed triage, most of them for irritation of the airways. Four were taken to the hospital, down from an initially reported five, and one person stayed in for observation. Firefighters closed the pool and tested the water. The water was then replaced, and the pool was later cleared to reopen. Phantasialand told WDR that the Outlook outage was why the chlorine warning emails never arrived.
The outage began on Thursday, November 12, with users in every region losing access to their Exchange Online mailboxes. The failure also broke features that depend on email in Teams, Copilot, Defender, Purview, Planner, Intune, and other Microsoft 365 services. Downdetector logged more than 100,000 reports within an hour of Microsoft acknowledging the problem. ABC News later put the global total at more than 7.4 million reports.
Here are some of the other real-world disruptions reported while the outage lasted:
On Thursday night, Microsoft EVP Charles Lamanna said the company regretted the disruption. On Friday, Microsoft apologized and named a preliminary cause. It said the incident “was introduced by an issue during an earlier network capacity upgrade that surfaced following a recent network change.” The company also described it as a technical issue unrelated to “cyber or AI / agents” and said it was “deeply sorry” for the disruption.
The company’s most recent update came on Saturday, November 14, in a post from its Microsoft 365 Status account on X. In it, Microsoft said it had “completed our efforts to address the underlying issue of the incident” and “restored service to the remaining impacted customers and regions.” The company has said it will publish a full post-incident report once its review is complete.






