ok, sure Crowd Strike, not MS.
That said, it’s so amateurish I have to question that it could be sabotage. We don’t know it wasn’t.
I’m a software architect and manager responsible for safety critical software systems, I’m well aware of release tools and processes.
"Was it sabotage?" is a perfectly reasonable question to ask. And somebody had better be digging into that question.
We don’t know it wasn’t.
And we don't know that it was. Who would benefit?
Sadly enough, the idea of "innocent until proven guilty" no longer applies to events we continue to see. While I consider sabotage in this case to be unlikely, it is not impossible. Perhaps some booby-trap that went off before it was planned to release?
But again, if you suspect conspiracy, who will benefit? That is where you must direct attention. If there was some kind of conspiracy, then you look for a technical person in a key position who just got a huge "inheritance" and retired. Or who just turned up dead "unexpectedly".
We don't have any such indicators yet.
The people who will lose are the ones at Crowd Strike. That company will be GONE. And the technical staff may be unemployable. The cyber-security industry is kind of a small community. Everybody has a reputation.