> We're investigating reports of users experiencing issues accessing Exchange Online mailboxes through multiple connection methods in the Americas. Globally, not just in the Americas. Other Microsoft 365 services are also affected.

> We determined the elevated load isn't driven by an increase in traffic, but by a number of servers being unexpectedly unavailable; straining the remaining infrastructure. > We found a core process on affected servers is becoming overwhelmed, causing capacity loss. > We’re identifying alternate workstreams that can be applied to increase capacity in the face of sustained traffic management imbalances. Hmm maybe they can migrate their infra to a hyperscaler to prevent capacity related outages like this in the future while working on a fix.

> Our investigation indicates the failed health checks may originate from a specific component that's responsible for processing server health. Someone prompted "health check not healthy please fix MAKE NO MISTAKES!!!".

> we're moving additional traffic off the affected infrastructure, and we're restarting affected servers to return them to service > In parallel, we've initiated a restart of all affected servers and are monitoring health as they return to service. > We're also preparing automated recovery systems to continually detect and restart unresponsive servers, to maintain service stability while this change progresses. > We're actively restarting and validating the affected servers to return them to service. > To validate a potential recovery, we're isolating a portion of infrastructure, restarting affected components Jeez, have you tried turning it off and on again?

It seems that not just the engineers but also the people responsible for incident communications were replaced by AI.