{"id":106033,"date":"2026-11-15T05:00:28","date_gmt":"2026-11-15T10:00:28","guid":{"rendered":"https:\/\/quotulatiousness.ca\/blog\/?p=106033"},"modified":"2026-11-14T12:43:59","modified_gmt":"2026-11-14T17:43:59","slug":"microsofts-m365-outage","status":"publish","type":"post","link":"https:\/\/quotulatiousness.ca\/blog\/microsofts-m365-outage\/","title":{"rendered":"Microsoft’s M365 outage"},"content":{"rendered":"

Millions of people have now experienced the joy of an empty inbox, thanks to the extended outage on one of Microsoft’s most important business software offerings. Many people are saying that Microsoft, having gotten rid of a lot of its veteran engineering staff over the last few years, may not be capable of fixing the problem. On X, John Ringo<\/a> offers his thoughts:<\/p>\n

\"\"<\/a><\/p>\n

CAN Microsoft recover?<\/strong><\/p>\n

(This was a reply to something. I decided it was better as a post.)<\/p>\n

Oh, I agree. They’ve been getting rid of the nerds that built the system and have this little undocumented bit of knowledge in their heads for years. That is a huge issue and definitely contributing to the downtime.<\/p>\n

But they (and AWS and others) have also built a system that is so complex and interwoven, the real issue is: <\/p>\n

If it crashes this hard can they bring it back up as it was at all?<\/p>\n

We get into discussions of telos<\/em> and kosmos<\/em>. It’s distinctly possible if you brought back EVERYONE who built it that they still couldn’t fix Humpty-Dumpty. <\/p>\n

We’ll see by Monday.<\/p>\n

Telos<\/em> and kosmos<\/em>. <\/p>\n

Telos<\/em> is a simple simple system. Every point in the system is understood and is comprehensible by a single person. (A single server. A large but not enormous set of servers.)<\/p>\n

Then there are simple complex systems. A system where every individual part of the system can be comprehended but it’s impossible to comprehend how all the parts interact.<\/p>\n

That is what Microsoft and AWS and other cloud providers have created. A system where you can maybe understand why this bit isn’t working but not why\/how its interacting to cause all these other bits to not work.<\/p>\n

It’s too complex.<\/p>\n

It’s one of the reasons that the people saying “Nobody is going to migrate off the cloud. Nobody wants to run their own servers. No IT guy wants to run email. These guys are literally the experts.” are all wrong.<\/p>\n

When a single company, from a two man shop to fortune 500, uses its own server system, the entire system can be understood. It is telos<\/em>. Every bit can be comprehended. It may be badly documented. There may be this little “thing” that only Joe Neckbeard knows and if you fire him you may have an outage.<\/p>\n

But it’s NOT so big nobody can really rebuild it in a serious meltdown.<\/p>\n

Rebuilding this ecosystem is so complex that it’s like nuking Manhattan and expecting every single piece to go back just like magic.<\/p>\n

It won’t. And those missing pieces are Gladys’ payroll spreadsheet that she inherited from Gloria who inherited it from Sandra who inherited it from Carol who got some nerd who left in 1996 to do it for her.<\/p>\n

The question becomes, what to do if it’s not back by Monday?<\/p><\/blockquote>\n","protected":false},"excerpt":{"rendered":"

Millions of people have now experienced the joy of an empty inbox, thanks to the extended outage on one of Microsoft’s most important business software offerings. Many people are saying that Microsoft, having gotten rid of a lot of its veteran engineering staff over the last few years, may not be capable of fixing the […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_hide_featured_image":false,"_jetpack_featured_image_duplicate_dismissed":0,"_jetpack_feature_clip_id":0,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_post_was_ever_published":false},"categories":[831,15,13],"tags":[156,711,58,94,92],"class_list":["post-106033","post","type-post","status-publish","format-standard","hentry","category-business","category-technology","category-usa","tag-fail","tag-infrastructure","tag-internet","tag-microsoft","tag-software"],"jetpack_shortlink":"https:\/\/wp.me\/p2hpV6-rAd","jetpack_sharing_enabled":true,"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/quotulatiousness.ca\/blog\/wp-json\/wp\/v2\/posts\/106033","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/quotulatiousness.ca\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/quotulatiousness.ca\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/quotulatiousness.ca\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/quotulatiousness.ca\/blog\/wp-json\/wp\/v2\/comments?post=106033"}],"version-history":[{"count":3,"href":"https:\/\/quotulatiousness.ca\/blog\/wp-json\/wp\/v2\/posts\/106033\/revisions"}],"predecessor-version":[{"id":106055,"href":"https:\/\/quotulatiousness.ca\/blog\/wp-json\/wp\/v2\/posts\/106033\/revisions\/106055"}],"wp:attachment":[{"href":"https:\/\/quotulatiousness.ca\/blog\/wp-json\/wp\/v2\/media?parent=106033"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/quotulatiousness.ca\/blog\/wp-json\/wp\/v2\/categories?post=106033"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/quotulatiousness.ca\/blog\/wp-json\/wp\/v2\/tags?post=106033"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}