TL;DR: Cloud outages are no longer rare events, and you can’t fix one from your end. A one-page continuity plan keeps your team working and your customers informed while you wait. Cover five things: which tools are critical, a backup way to communicate, what you need available offline, who’s in charge, and where to check status. Keep it somewhere you can reach when your main systems are down.
Most of your business probably runs in the cloud now. Email, files, accounting, bookings, payments. Then one morning a service goes down, nobody can send email or take a payment, and there is nothing your team can do except wait.
That’s the part business owners find hardest to accept. When a major provider has an outage, you have no lever to pull. You can’t escalate it, you can’t work around it, and rebooting laptops won’t help. A cloud outage plan isn’t about fixing the problem. It’s about staying functional until somebody else fixes it.
And these are not once-a-decade events anymore. In the last eighteen months, businesses have lost hours to an AWS failure, two separate Microsoft outages, and a security update that crashed machines worldwide. If your plan for that is “hope it doesn’t happen during a busy week,” you don’t have a plan.
Do Cloud Services Really Go Down That Often?
Yes, and the biggest providers are no exception. Being on a well-known platform buys you strong engineering, not immunity. Every major cloud provider has logged multi-hour failures in the last two years, and the outages that hurt small businesses most are usually the ones that take email and file access with them.
The recent record makes the point. The October 2025 AWS outage generated more than 17 million Downdetector reports and ran past 15 hours, disrupting services across the internet. Days later, a Microsoft failure took down Microsoft 365, Outlook, and Teams along with airline check-in systems and major retailers.
Then it happened again. In January 2026, a Microsoft 365 outage ran close to ten hours, with external email stopped entirely for many customers and 15,000 reports at the peak.
And it doesn’t take a hacker. The July 2024 CrowdStrike incident, where a faulty security update crashed roughly 8.5 million Windows machines in a few hours, cost U.S. Fortune 500 companies an estimated $5.4 billion. That one was a bad file, not an attack.
What Does an Outage Actually Do to a Small Business?
Work stops, and it stops for everyone at once. Your team can’t reach email or files. If your payment or booking system is down, you can’t take money or appointments. Customers try to reach you and can’t, and you can’t reach them either. Meanwhile staff sit waiting for something they have no control over.
The costs aren’t dramatic, which is part of why owners underestimate them. It’s a half day of payroll spent on nothing. It’s the three appointments that didn’t get booked. It’s the client who called twice and then called somebody else.
Then there’s the reputation piece. Customers rarely know or care whose fault it was. They know they couldn’t reach you, and the businesses that come out of an outage looking competent are the ones that communicated during it.
Doesn’t My Microsoft 365 Subscription Cover This?
No. Your subscription includes an uptime target from the provider, not a continuity plan for your company. If Microsoft or Google misses that target, you may qualify for a small service credit against your bill. That credit does not cover lost revenue, missed deadlines, or the hours your team spent unable to work.
This surprises people, and it shouldn’t. You’re buying a service, not an insurance policy. The provider’s obligation ends at their own infrastructure, and everything downstream of that is yours to plan for.
It’s also worth knowing what depends on what. Microsoft 365 runs on Azure. Google Workspace runs on Google’s own cloud. Plenty of the other tools you use are quietly built on AWS. You may be more concentrated on one provider than you realize, which is the kind of thing worth mapping once as part of your broader technology strategy.
What Should a One-Page Continuity Plan Cover?
Five questions, answered in advance and written somewhere you can reach without your main systems. Which tools are critical, how you’ll communicate, what you need available offline, who makes decisions, and where you check status. One page is genuinely enough for most small businesses.
Which tools are critical? List only the services that would stop the business if they went down: email, your payment system, your booking tool, your practice management software. Skip the ones you could live without for a day. Most companies find the real list is four or five items.
How will people stay in touch? Have a backup way to reach staff and customers that doesn’t depend on the tool that’s down. Phone numbers, text messages, or a group chat on a different platform. If your whole team coordinates in Teams and Teams is the outage, you need a second channel that already exists.
What do you need reachable offline? Keep a copy of the essentials somewhere you can open with no internet: your customer contact list, key phone numbers, and the documents you’d need to keep working. A printout in a drawer counts. So does a copy on a phone.
Who’s in charge? Name the person who makes decisions during an outage and the person who updates customers. When that’s decided in advance, people act. When it isn’t, everybody waits to be told.
Where do you check, and who do you call? Know where to see whether it’s a wider outage, which is usually the provider’s status page, and who to call for help. For most businesses that’s their IT provider.
What to Do the Moment an Outage Hits
- Check whether it’s just you. Look at the provider’s status page or ask whether anyone else has the same problem. If it’s widespread, stop troubleshooting. There’s nothing on your end to fix.
- Tell your team. Say what’s down and what to use instead, so nobody burns an hour rebuilding a laptop that was never the problem.
- Switch to your backup channel. Move to phone, text, or your secondary app so the team can still coordinate.
- Tell customers if it affects them. If you can’t take bookings or payments, say so and tell them when to try again. Silence costs more than the outage does.
- Write down when it started and what’s affected. Two lines is enough. It helps you follow up afterward and spot anything that needs attention once service returns.
That third step is the one people skip, and it’s the one that separates a chaotic afternoon from a manageable one.
Small Changes That Make Outages Hurt Less
- Keep key files available offline. OneDrive and SharePoint can sync recent files to the device so they still open when the service is down. Most businesses have this half-configured and never test it.
- Have a backup way to get online. A phone hotspot can get a few critical people working again if your internet drops rather than your cloud service.
- Bookmark your status pages. Microsoft 365, your accounting platform, your payment processor. It’s the fastest way to tell whether the problem is them or you.
- Keep contacts off the cloud. Important numbers should exist somewhere that doesn’t need the internet, whether that’s a printout or your phone’s own contact list.
- Ask about outage alerts. Many IT providers can warn you about a service disruption before your customers do.
None of these are expensive. They’re the kind of thing that gets set up once and then quietly earns its keep, which is also true of proper backup and recovery, the other half of staying operational when something breaks.
Write the Page This Week
Three things to take away. Cloud outages are now a normal operating condition, not a rare disaster. Your subscription buys uptime targets, not continuity. And the businesses that handle outages well are the ones that decided who does what before it happened.
Set aside twenty minutes. List your critical tools, pick a backup way to communicate, note who’s in charge, and print it. Review it once or twice a year so the names and numbers stay current. That’s the whole exercise.
If you’d like help figuring out which of your tools are most exposed, or getting offline file access set up properly, schedule an intro call with our team. It’s a short conversation and it usually surfaces one or two things worth fixing.
Frequently Asked Questions
Isn’t the cloud always available?
No. Cloud services are reliable, but they still fail, and the largest providers have all had multi-hour outages in the past two years. It’s safer to assume an outage will happen eventually and decide in advance how your business will operate during one.
What should a small business continuity plan include?
Five basics: which tools are critical, a backup way to reach staff and customers, where to find essential information when the main system is down, who makes decisions during the outage, and who to call for help. One page covers it for most small businesses.
What if the internet itself goes down, not just one app?
Plan for that separately. A phone hotspot can get key people back online, and phone calls still work when your systems don’t. Keep important numbers somewhere that doesn’t require the internet, since a contact list living only in the cloud is unreachable exactly when you need it.
How can my team keep working if Microsoft 365 is down?
It depends on the work, but the usual options are files already synced to a device, switching to phone or text to coordinate, and handling anything urgent on paper until service returns. The offline file sync is worth confirming ahead of time rather than discovering during an outage.
How long do outages usually last?
There’s no reliable answer. Some resolve in minutes and some run most of a day, with recent major incidents lasting from several hours to more than fifteen. That uncertainty is exactly why the plan matters, because you can’t count on a quick fix and you can’t speed it up from your end.
Want a Second Set of Eyes on This?
A continuity plan is one of those things that’s easy to write and easy to write badly, usually by listing every tool instead of the few that matter. Reach out for a straightforward conversation and we’ll help you sort the critical from the merely annoying. Our technology consulting work often starts with this exact question.