On Thursday, Microsoft 365 went down. Outlook, Teams and Copilot, in more than 70 countries, for most of two days.

Engineers restarted the mail servers. They came back healthy, then fell over as soon as traffic hit them. Some organisations went back to fax machines.

r/sysadmin wrote the movie:

One exec has just landed his helicopter in the wilds of Bolivia, where Johnny Exchange has retreated. We need you, Johnny. “I haven’t touched a computer in 10 years. I’m done with that life.”

— u/Simmery, r/sysadmin

It is a joke. Millions of people now believe it.

The Post That Went Viral

On Friday, a screenshot of an anonymous Blind post from a verified Microsoft employee spread across X. One repost has 4.2 million views.

After waves of layoffs, voluntary exits, and sub-5% hikes, the senior engineers who actually understood how these legacy systems were wired are completely gone. Now, a rollback that used to take 45 minutes drags out for five hours.

— Anonymous Microsoft employee, Blind

The same post said a line almost nobody repeated: “Nobody outside knows the real root cause yet, and I’m not going to guess.”

Then the story grew. A popular retelling turned five hours into “a 12 hour global outage.”

What Actually Broke

  • A network change. Microsoft’s preliminary cause is a problem from an earlier capacity upgrade, exposed by a recent network change. The Verge’s sources point to Azure VNet config.
  • Not the buyout. The 60,000 people offered exits in October leave on December 31. Nobody has left yet.
  • Not AI. That is Microsoft’s position. The final report is due this week.

People suddenly think every problem is vibe coding these days. I think people forget we still have the outages we’ve had for years thanks to configuration changes.

— Tom Warren, The Verge

It is the AI scapegoat in reverse. When companies cut jobs, they blame AI. When things break, the public blames AI and the cuts.

The Part That Rings True

Config changes break every cloud. The real question is why the fix took two days.

  • A former Azure Core engineer saw it in March. Axel Rietschin found up to 173 agents managing each Azure node, and “no one at Microsoft, not a single soul, could articulate why” (Substack). That is Azure, not Exchange, but it is the same problem.
  • The cuts already happened. Headcount fell by 5,000 in a year, and 4,800 more went in July.
  • The rest may have checked out. One r/technology reply on the buyout takers: “They’ve all mentally checked out.”
Still unproven

No named source links staffing to this outage. The Blind post is one anonymous voice, and it admits it does not know the cause. Wait for Microsoft’s report.

Knowledge does not leave in one day. It leaves one cut at a time, and nobody notices until a 45-minute rollback takes five hours.

What To Do About It

You are not leaving Microsoft 365 over this. Run Exchange yourself and you own the 3 AM call.

  • Know who fixes what. Before you cut a senior engineer, write down what only they understand.
  • Practise the rollback. Time it. If it gets slower, ask why.
  • Promote the boring work. If uptime never gets anyone promoted, it stops happening.
  • Have a second channel. Decide how your team talks when email and Teams are both down.

The config change was bad luck. The two days took years to build.

Related Posts