I first found out about today’s massive Microsoft outage from my girlfriend. The multinational bank she works for experienced a 100% outage of its email service.

Meanwhile, my phone didn’t ring once from my own retainer clients. They’re all on Google Workspace. I’m not here to argue that Google is inherently better than Microsoft (They are though.). They’ve had their share of bad days, too, but in this specific instance, my clients were spared.

Still, watching a global giant stumble makes you stop and ask an uncomfortable question: What if it had been Google? What could I actually do if my clients woke up locked out of their email because their cloud provider went dark?

The honest answer is: nothing. Once your cloud provider’s infrastructure goes down, there is nothing any IT consultant can do to turn it back on.

That is precisely why risk mitigation and operations continuity planning matter so much. My job isn’t just fixing things when they break; it’s thinking about the what-ifs long before “it” happens. I obsess over edge cases. What happens if a client loses their primary internet connection? What if rolling brownouts hit the neighborhood? What if a point-of-sale terminal dies, or a cloud invoicing platform goes offline? What if an on-site backup server takes a power surge and literally catches fire?

That last one isn’t hypothetical, it actually happened to one of my clients. They didn’t lose a single day of business because we planned ahead. Way ahead.

A Global Blind Spot Across 74 Countries

We can’t stop every outage, and we certainly can’t spin up a replacement enterprise email server in ten minutes when Microsoft goes down globally. According to CNN, outage reports surged across 74 countries and territories within roughly an hour.

As NPR reported, Microsoft stated that a portion of its infrastructure was experiencing “elevated load,” which likely contributed to the connectivity errors after servers failed “automated health checks.” By early morning, The Guardian noted that the disruption was dragging on because Microsoft’s initial recovery efforts were “not taking as expected”, with The Guardian also reporting severe disruption across Australian businesses, schools, and government agencies.

Microsoft officially stated that the failure was not caused by a cybersecurity breach. Even taking them at their word, incidents like this expose how fragile our infrastructure has become. Between escalating geopolitical conflicts involving Russia, Ukraine, and Iran, and threat actors leveraging AI to discover novel attack vectors.. widespread cloud infrastructure disruptions are only going to become more frequent.

Scammers Love an Outage: Maintain Zero Trust

Whenever a major platform crashes, the vultures start circling immediately. Scammers are already cold-calling small businesses posing as “Microsoft Support,” offering emergency assistance to get their email back online. All they need is remote access to your workstation, your login credentials, or your billing details.

This is where your Zero Trust resolve has to hold firm. You’ve heard me say it a thousand times: do not trust anyone who calls you.

You cannot authenticate an inbound caller. Too many third-party companies holding your basic personal and business data have already been breached, meaning a scammer calling you might already know your name, your domain, and your IT setup. It is virtually impossible to 100% verify that an inbound caller is who they claim to be. Hang up, verify through official channels, and never grant remote access to an unsolicited caller.

Building Real Operational Continuity

Relying on the cloud for email is a no-brainer today. Years ago, I used to build and maintain on-premise email servers for clients. In IT, we used to joke that the worst parts of the job were printers and email servers. Cloud email cured half that headache—now it’s just printers.

But if cloud email is a necessary convenience (and liability shifting), operational continuity is how you survive when it fails:

  • Redundant Connectivity: For critical business operations, I set clients up with dual-ISP failover—pairing Verizon FiOS with cable internet, dedicated 5G cellular failover, or even just an office mobile line with an unlimited hotspot ready to deploy the second a line goes down.
  • The 3-2-1 Backup Rule: We never rely on a single cloud dashboard for critical records. Keeping 3 copies of your data, across 2 different types of media, with 1 copy stored completely off-site/offline ensures that even a literal server fire won’t wipe you out.

Why I Build Local-First Software

At my software division, TechingAPPS, our core philosophy is simple: Zero cloud. Local first. No tracking. No data harvesting.

As we state right on our homepage:

“We build cybersecurity-focused apps for clients that keep your data on your devices, which is where it belonged in the first place. No cloud account you didn’t ask for. No mystery ‘partners.’ No fine print that turns you into the product. Apps that collect your data become targets for hackers, and hackers can’t steal what you don’t have.”

I’ll gladly help clients configure and secure cloud tools when it makes operational sense, but for my own business architecture, I keep things strictly local.

I built Invoices+ from the ground up—not just to go toe-to-toe with QuickBooks Online on features, but because it runs locally on your own hardware. You can run it on your PC without an internet connection at all. Remember those days? When you didn’t have to pay thousands of dollars a year just to rent access to someone else’s computer so you could look at your own customer list?

This isn’t a sales pitch—it’s proof that I put my development where my mouth is. Whether it’s a full accounting suite or a lightweight utility to convert legacy data formats and bridge old shop-floor hardware with modern software, I build tools designed to eliminate single points of failure.

Take Today as a Warning

We are all tied to cloud infrastructure to some degree, and when giants like Microsoft stumble, the ripple effects hit hard.

I received several cold calls today from panicked business owners reaching out to random IT shops begging for help. Telling a prospective client “I can’t fix this for you right now” is never a fun conversation. Yes, we can spin up temporary workarounds or secondary domains, but the real problem most of those callers faced was deeper: their phone systems, their customer lists, their authentication apps, and their core financial records were all chained to that single Microsoft account.

Many businesses simply locked their doors and went home today because they couldn’t function without their inbox.

We can’t prepare for every conceivable disaster, but we must prepare for our cloud providers to go down. Today it was Microsoft. Tomorrow it could be your payment processor, your e-commerce marketplace, or your CRM. If your CRM goes offline tomorrow morning, do you even have a local list of who your customers are?

Don’t wait for the next global outage to find out. Build your fallback plan while the lights are still on.