Microsoft "Not quite" 365
It’s hard not to feel sorry for the folks responsible for the 27-plus-hour outage of Microsoft 365. It would have been a tough few days, and I’m sure the post-mortem won’t be pretty.
Having had to use Microsoft’s cloud suite in previous jobs, I’ve since worked at companies that are all in on Google and Slack, and the difference is night and day. The Microsoft approach is so antiquated in so many ways. From a guilt-inducing automatic “Away” status in Microsoft Teams (which encourages inexperienced managers to optimise for performative presenteeism) to cloud-based documents that somehow have to work with the legacy of Windows and Office (which bizarrely means you can’t use Windows-restricted characters in filenames when operating in the cloud or on a Mac), the whole thing feels stuck in the past and full of paper cuts.
I know first-hand from my wife how useless Microsoft Copilot is, so it’s not as if it’s a leader in AI either. I doubt any of this had much to do with the outage, but it’s an interesting observation that companies that run on Microsoft are now in my experience likely to be laggards in technology uptake, which was certainly not the case 20 years ago.