I'm not pretending. I was literally on a trip with a friend who had a significant number of his customers in M365. He burned over a day, back in January of this year, getting things squared away. And he was saying that wasn't the first time within a month.
He also had recently gotten locked out of Google Workspace for a different customer because of a domain registration issue that put him in a deadlock where he couldn't validate the domain because he was locked out and, if I'm remembering correctly, he needed the Workspace access to validate for the changes he needed to make. It was comical and even though it was a paid for account Google was basically useless / non-responsive.
I've also, unfortunately, had to deal with a lot of M365 integrations and external tooling. The fact that changes made in those environment don't always propagate immediately (and there's not indication in the UI of when it will take place) led us to create explicit documentation about how setup in an M365 environment for our tooling could take up to 24 hours because of the inability to programmatically get status of what configuration was deployed. Mail implementations were bad, but Teams was even worse. Talk about nightmare fuel of renaming things every year, APIs that work consistently about half the time and the inability to know when a configuration change was actually applied has definitely convinced me that Microsoft doesn't care and/or doesn't know how anymore. It's "good enough" for most, but flaming garbage for those who care.
You can go to bat all you want for Microsoft, the public record doesn't lie though. And if fanboy'ism is still a thing with big tech, well... That's just embarrassing. But, hey, maybe they sign your checks?