When the World Goes Offline, What's Your Plan?

By: Jennifer Gilligan, IntegraMSP President

Microsoft, the FAA, and a turbulent week in AI delivered a reminder that business resilience isn't optional.

Well, that was quite a week for technology.

Microsoft 365 experienced a widespread outage, disrupting email, collaboration, and productivity for businesses around the world. The FAA experienced a technical failure that temporarily grounded flights nationwide. Meanwhile, NVIDIA and the broader AI industry reminded investors just how quickly enthusiasm can turn into uncertainty.

Different industries. Different problems. One common thread.

We have built an extraordinary amount of our daily lives and business operations around technology working exactly as expected. Until it doesn't.

And when it doesn't? Things get interesting. Fast.

As someone who spends her days helping businesses manage technology, I can tell you that outages aren't particularly surprising. Systems fail. Networks go down. Cloud providers experience disruptions. Even the largest technology companies in the world aren't immune.

What concerns me more is how many organizations still operate as though none of that will happen to them.

Your backup plan cannot be "wait until it's fixed."

Think about what happens when your primary communications platform goes offline.

How does your team communicate? How do you notify clients? Can employees access critical information? Who decides whether to activate an alternative process?

And perhaps most importantly, does everyone know the answers before something goes wrong?

If your entire continuity strategy depends on a single provider remaining operational, you don't really have a continuity strategy. You have a dependency.

Cloud technology is incredibly valuable, but outsourcing infrastructure doesn't mean you've outsourced responsibility for keeping your business running.

The same principle applies to AI. We're racing to adopt tools that promise incredible efficiency and productivity, but how many organizations are considering what happens when those tools become unavailable, unreliable, or fundamentally change?

Innovation without operational planning creates a different kind of risk.

Preparation doesn't have to be complicated.

Not every business needs a hundred-page disaster recovery manual collecting dust somewhere. But every business should be able to answer a few basic questions:

  • What can't we operate without? Identify the systems, applications, and people critical to daily operations.
  • What's our alternative? Establish approved communication channels, backup access, and documented procedures.
  • Who's responsible? Assign decision-making authority and establish how employees and customers will be informed.
  • Have we tested it? A plan nobody has practiced is a theory, not a strategy.
  • Can we access the plan when our systems are down? Because storing your entire outage response plan inside the very platform that just failed is a particularly unfortunate bit of irony.

And remember, a backup system should still meet your security requirements. An outage isn't an excuse to start sending confidential client information through personal accounts or downloading random applications.

Resilience is about more than recovery.

There's an important distinction between recovering from an outage and continuing to operate through one.

Recovery gets your systems working again.

Continuity keeps your business functioning while you're waiting.

Both matter.

The events of last week weren't evidence that technology is failing us. They were reminders that technology is complicated, interconnected, and occasionally unpredictable.

The organizations that handle disruptions best aren't necessarily the ones with the biggest IT budgets. They're the ones that have thought through the uncomfortable scenarios before those scenarios become reality.

You cannot prevent every outage. You can prevent an outage from becoming complete organizational chaos.

And if last week taught us anything, it's that the best time to figure out what you'll do when the world catches fire is well before you smell smoke.

Jennifer Gilligan
President, IntegraMSP

 

Business Continuity FAQ: What Can Your Business Do Right Now?

1. What is business continuity planning, and why does my business need it?

Business continuity planning is about keeping essential business operations running when something unexpected happens. That might be a Microsoft 365 outage, an internet failure, a cyberattack, a power outage, or even a disruption involving a critical vendor.

A disaster recovery plan focuses primarily on restoring systems and data. A business continuity plan addresses the bigger question: How do we keep serving customers and operating while those systems are unavailable?

Start here:

  • Identify your five most critical business functions. Think customer communications, billing, payroll, scheduling, and access to essential records.
  • Determine which technology systems each function depends on.
  • Ask how long each function could reasonably be unavailable before the business experiences serious consequences.
  • Identify which functions must continue immediately and which can temporarily wait.

This is the foundation of a business impact analysis, and it doesn't have to be complicated to be useful.

2. What should employees do if Microsoft 365, Teams, or company email goes down?

If your company's primary communication systems fail, employees shouldn't have to improvise how to reach each other.

Create a communications backup plan before an outage:

  1. Select a secondary communication method that doesn't depend on the same services or identity systems as your primary platform.
  2. Have IT approve and secure it before employees need it.
  3. Establish an emergency contact directory with current phone numbers for employees, leadership, key vendors, and critical customers.
  4. Assign someone to communicate outage updates internally and someone to handle customer-facing communications.
  5. Test the alternative communication process with your team.

Your backup method might involve a separate messaging platform, phone calls, or text notifications, depending on your security and compliance requirements.

Important: An emergency doesn't eliminate your responsibility to protect company and customer information. Personal email accounts, unauthorized file-sharing applications, and unsecured messaging tools can create additional problems.

3. What systems should a small business prioritize in its continuity plan?

Not every system needs the same level of protection or recovery priority.

Start by identifying which systems directly affect your ability to generate revenue, serve customers, meet legal obligations, and communicate.

For many small and mid-sized businesses, the priorities include:

  • Email and communications: How will employees and customers stay informed?
  • Internet and network connectivity: Is there a secondary connection or alternate work location?
  • Critical business applications: Can essential work continue if your CRM, accounting platform, or industry-specific software becomes unavailable?
  • Data and document access: Are critical files backed up independently, and can authorized employees retrieve them?
  • Financial operations: Can you process payroll, payments, and invoices during an interruption?
  • Phones and customer service: Can incoming calls be redirected if your primary phone system fails?

For each critical system, document its owner, business impact, dependencies, recovery priority, and available alternatives.

Don't assume a cloud provider's uptime commitment guarantees your business won't experience downtime.

4. Aren't cloud backups and Microsoft 365 enough to protect my business?

Not necessarily.

Cloud services provide significant reliability benefits, but using the cloud doesn't automatically mean your organization has a complete backup or continuity strategy.

There are important differences between availability, data protection, and business continuity.

For example, Microsoft 365 may retain or protect certain information through native capabilities, but those features aren't necessarily equivalent to an independent backup solution designed around your company's recovery requirements.

Ask your IT provider these questions:

  • Are our Microsoft 365 emails, OneDrive files, and SharePoint data independently backed up?
  • How frequently are those backups performed?
  • How long is the data retained?
  • What happens if the primary Microsoft 365 environment is inaccessible?
  • Can we restore individual files, mailboxes, or entire datasets?
  • When was the last successful restore test?

Also, remember that having a backup copy of your data doesn't automatically mean employees can continue working during an outage. Data recovery and operational continuity require different planning.

5. How often should a business test its continuity plan?

At minimum, conduct a structured review and practical exercise twice per year. Businesses with more complex operations, regulatory requirements, or significant operational risks may need more frequent testing.

You don't necessarily need to shut down your systems to test your readiness.

Try this 30-minute tabletop exercise:

  1. Gather your leadership team and key operational employees.
  2. Present a scenario: "It's 9:00 AM on Monday. Email, Teams, and our primary cloud platform are unavailable for the next eight hours."
  3. Ask each department how it would communicate, access critical information, and continue essential operations.
  4. Identify decisions that nobody knows who is authorized to make.
  5. Document gaps, assign owners, and establish deadlines for fixing them.

Then repeat the exercise after improvements have been made.

The goal isn't to prove your organization has a perfect plan. It's to discover weaknesses while the stakes are still low.

6. What's the first thing a business owner should do this week?

You don't need to solve every continuity problem overnight. Start with a simple, actionable assessment.

Your five-step business continuity starter plan:

  1. Identify: Write down the five systems or business functions you absolutely cannot operate without.
  2. Prioritize: Determine how long each could be unavailable before creating unacceptable business consequences.
  3. Prepare: Document an approved alternative process for each critical function, including the people responsible for activating it.
  4. Communicate: Make sure employees know where to find emergency procedures, who makes decisions, and how they will receive updates.
  5. Test: Schedule a short exercise to verify that the plan works in practice.

Keep an accessible copy of your emergency procedures somewhere that doesn't rely exclusively on the systems you're preparing to lose. Protect sensitive information in those copies.

And don't forget to revisit the plan when you add new applications, vendors, employees, or business locations.

The bottom line: A continuity plan doesn't have to be complicated to make a meaningful difference. It does have to be documented, understood, and tested.

Technology outages are inevitable. Turning one into a full-blown business crisis doesn't have to be.