Why today's Microsoft outage doesn't change a darn thing
Some people say I’m cynical, and what you’re about to read will do nothing to dissuade them of that.
You may have noticed that on Friday 13 November, Microsoft’s 356 family of services had a bad day. You know it’s significant when it’s the first item on the radio news in the morning and your retired mother asks you about it on the phone.
Of course, some people have used this as an excuse to saddle up their favourite hobby horse: the cloud is bad, it’s just someone else’s computer, we’re all at the mercy of global mega corporations and we should go back to running our own email on open source software using servers we can put our hands on.
I beg to differ.
For sure, Friday was a “digital snow day” (1) for much of the world, but unlike the outages we had in the “good old days” when we ran this stuff in house, much of the world was affected. Did customers get cross with us for not being able to uphold our commitments for a day? Well, maybe, but since a majority of them were unable to email us or call us on Teams, how would we know?
No doubt the team at Microsoft are working hard to try and avoid this happening again, but the pragmatist in me says that it’s convenient if the inevitable occasional outage affects lots of people and organisations, not just a couple.
Personally, of course, I use Fastmail, but even they are prone to interoperability problems which are not their fault (2) - unfortunately, non-technical users don’t want to hear that, they just want their email to work.
Happy Friday the 13th!
Footnotes
(1) Not my phrase, but rather neat so I borrowed it. Thanks C.
(2) Yes I’m aware the article is about Mythic Beasts, but I’ve had to chase up Fastmail support about incorrect blocking from Microsoft before, and the response I got could be summarized as “not much we can do mate”.