← Back to Field Notes
Technology & InfrastructureInland Sea Works2 min read

When Microsoft 365 Goes Down, What's Your Plan B?

A Microsoft 365 outage in late August is a prompt to ask what your business does when email and collaboration tools go down.

Microsoft 365 had a rough stretch of outages this month, and the one that hit around August 24 knocked out access for a meaningful chunk of users before it was resolved, according to reporting tracked by Tom’s Guide and IT Pro. It’s a good moment to ask a question most businesses never think about until it’s too late: what happens when your email and collaboration platform simply isn’t there?

This isn’t really about Microsoft’s reliability. Microsoft 365 is, on the whole, extremely reliable, and moving away from it isn’t the lesson here. The lesson is that “extremely reliable” isn’t the same as “never down,” and even a few hours of downtime can stall a business that has no fallback for anything.

The businesses that weather this well have already answered a few questions. How do we reach clients if email is down? Is there a phone tree, a shared document outside the platform, or even just a habit of exchanging personal contact info with key vendors and clients? Can staff still access files they need if SharePoint or OneDrive is unreachable?

None of this requires expensive redundancy. It requires deciding, in advance, what the fallback communication method is, and making sure the people who’d need to use it know what it is.

General IT Tip: Write Down Your “If Email Is Down” Plan, Even If It’s Simple

This doesn’t need to be an elaborate disaster recovery document. A single page that says who to call, what number to text, and where critical files live outside your primary platform is enough to turn a stressful outage into a manageable one. The value isn’t in the plan’s complexity, it’s in having decided this before the outage, not during it.

What This Means for You

  1. If you don’t have a documented fallback communication method for a Microsoft 365 outage, that’s worth fixing before the next one, not during it.
  2. Make sure a small number of critical files or contacts are reachable somewhere outside your primary cloud platform.
  3. Reliability incidents like this are a good, low-stakes prompt to test your fallback plan even when nothing’s actually broken.

Sources: