While I think it's a bit premature to jump to "AI is at fault", and I will emphasize that I appreciate Microsoft's transparency in their status updates, these updates do have much more of a "we don't know what's going on" feel than any other major outage I can think of.

It's been hours, and the status updates still feel like there is an undertone of frantic panic (understood if you can't determine the root cause). When I think of past major outages, they may have been down for hours but usually folks knew what the root cause was relatively early, even if remediation took some time.

I wouldn't be surprised if AI coding and release pressure was a primary cause, so I really hope the future post-mortem is made publicly available.

I think this has to do more with their calculating SLAs for uptime than anything else. Once they have a root cause and start deploying a fix they can "stop the clock" on the outage, even if they don't get to your tenant right away.

Imagine the amount of money they're losing right now in credits that will have to be applied once this finally gets resolved.

> I wouldn't be surprised if AI coding and release pressure was a primary cause, so I really hope the future post-mortem is made publicly available.

If nothing else, increased change volume will mean the number of candidate diffs ballooned, possible to a level where non-AI review is impossible on incident-level timescales.

Coupled with each change also being AI-documented and the relevant teams having less hands-on understanding of their own changes, so going to the pushing team and asking "Tell me about _____" isn't an option.

AI is at fault for what seem like some of the most vaguely worded outage stuff I have seen.

The email outage gives me time to order popcorn off Amazon for the inevitable postmortem in a few days. I hope it's a good one!

You can be surprised because it (apparently) had nothing to do with AI or release pressure. It was a combination effect of two separate network changes.