So when it goes right it's 100% AI and when it goes wrong it's 0% AI? Lmao
Got off a call with the an MS team lead who was on the bridge for this incident on what exactly happened in the outage:View quoted post on X
1. This was a "latent bug" - a commit going in ~4 months ago to a Windows build, that only activated much later. Super hard to spot
2. Zero AI, this code was human written + committed
3. Machines got saturated and unreachable at a result
4. So many other things went wrong during this outage: a series of unlucky events
5. It was a dev who found the root cause, poking around and seeing a dump that reminded them of an error seen here. AI diagnostic tools were used and helped progress with the outage
A detailed, public postmortem is on its way. MS wants to make sure they have everything patched globally before the postmortem. I'll add my two cents when it's out, and those details will be VERY educational