Microsoft on the other hand, has proven that it will never be reliable.
You can argue that this is a result of something outside of their control, and you would not be wrong, but if the point here is about centralization rather than simply a particular company's operational procedures, then direct strikes on datacenters should be part of that conversation.
I was an Amazon red badge in the EC2 org, fwiw, and do think AWS has excellent operational culture, far beyond what I saw while working in the M365 org, and beyond what I've seen at other tech companies and hedge funds where I've worked. But that doesn't obviate issues with centralization.
If Bank of America's central datacenter (cloud or on-prem) gets hit by a cluster bomb, taking out banking for ~half the US, you can be damn sure that very smart people are going to be working 24/7 until it's resolved.
If you have all your savings stored with a local credit union, say Seattle Credit Union which has 50,000 customers, and they get hit with a ransomware attack... well, good luck. You (probably) won't lose any actual money thanks to FDIC rules, but it might be weeks or months before their services are back online.
Similar to self-hosting vs cloud, you get a bit of a paradox where it's overall better for society if there's no interdependencies so a SPoF outage doesn't impact everyone, but things are much worse for an individual in the event a localized outage does occur due to economies of scale, or lack thereof in this case.
Its pros/cons are known and gaps can be addressed with 3p software. You just keep on old outdated, but proven version of software and keep the perimeter locked tightly.
its the azure cloud that is the wildcard.
Don't forget that MS has the advantage of non-English languages support that many alternatives lack.
I feel like it is very unknown, there is no documentation and everyone relies on comments on random forums that are now 21 years old which tells to set undocumented registry keys to undocumented values.
It's not just Europe! :(