I agree that MS was not directly involved in this.
But the fact remains that it was the combination of CrowdStrike running on Windows machines.
IMO the fundamental Windows issue is that, although the original concept in Win-NT was to keep third-party code out of the kernel, it only took a few years for Microsoft to start inserting all sorts of things to run in kernel space; drivers for interactive devices for better performance especially. At that point the gate was open and drivers piled into the kernel whether they needed to be there or not. Any one of them could hang the system, crash the system, BSOD, etc.
So while this current debacle is correctly laid at CrowdStrike's feet, Microsoft needs to take the blame for screwing the kernel, back 25+ years ago, and making the debacle possible. Indeed, inevitable.