Have Questions? Call ParJenn Technologies (409) 684-2517   |   Customer Portal
microsoft outage
Business Continuity Microsoft

Microsoft Outage? A 5-Point Plan on One Page

One morning the email stops. Nobody can send, nobody can receive, and Teams is spinning. Someone reboots a laptop. Someone else reboots the router. Twenty minutes later somebody checks their phone and finds out it is a Microsoft outage, down for half the country. There is nothing to fix. You wait. A Microsoft outage plan exists so that the waiting is the only part you cannot control.

Most of a small business runs in the cloud now. Email, files, accounting, bookings, payments, and for most offices around here that cloud is Microsoft 365. That is the right way to run it, and I will not pretend otherwise. But it means a handful of companies you have never spoken to can stop your business for a morning, and when they do, the only question that matters is whether you decided in advance what your team would do.

Why a Microsoft outage plan is worth one page

It does not take a hacker for this to happen. In July 2024, a faulty software update from the security company CrowdStrike crashed millions of Windows computers around the world in a few hours. Microsoft estimated it hit 8.5 million devices, grounding flights and stopping work at banks and hospitals. A bad update, not an attack.

Microsoft 365 itself has had days this year where email or Teams stopped working for hours. A Microsoft outage does not care that you are with the biggest provider in the world. It just means you are down at the same time as everyone else who runs on it.

And here is the part that gets missed. Around here, a Microsoft outage is not usually the thing that goes down. The internet line is. When Spectrum has signal trouble on the line, and it does, every cloud service goes with it, Microsoft included. Same downtime from where you sit, different cause, and the plan is the same.

The reason to keep the plan to one page is simple. A long plan gets written once and never read. A one page plan gets taped inside a cabinet door and actually used.

What actually stops during a Microsoft outage

I want to be concrete, because “work stops” is too vague to plan around.

At a body shop, the estimate cannot go out and the parts order cannot be placed, because both live in email. At a dealership, the finance office cannot pull up the deal folder. At a small office, the front desk cannot see the calendar, so they cannot tell the person on the phone whether Tuesday is open. At a nonprofit, the donor list is in a SharePoint folder nobody can reach. During a Microsoft outage, all of that stops at once.

Customers try to reach you and cannot. You cannot reach them either. Staff stand around, then start rebooting things that were never the problem, and somebody eventually loses an hour on the phone with a help desk that can only tell them what they already know.

Being honest, the Microsoft outage itself is usually a couple of hours. The lost morning is mostly the confusion around it. That is the part a plan fixes.

The five things on a Microsoft outage plan

A good plan answers five questions, and every one of them can be answered before anything goes wrong.

Which tools would stop the business? Not every tool. The handful that would halt work if they vanished: email, the payment system, the booking tool, the estimating software. Most of these live in Microsoft 365, so an outage takes them together. Ignore the ones you could live without for a day. Most businesses have three or four that matter and a dozen that do not.

How do people reach each other? A backup way to reach staff and customers that does not depend on the tool that is down. Cell phone numbers. A group text. A different chat app. Write it down, because when Teams is down, the list of everyone’s numbers is also in Teams.

What do you need reachable offline? The customer contact list, key phone numbers, the vendor list, the top few documents. A printout in a folder, or a copy on a phone. Not everything. The essentials.

Who is in charge? One person decides what the team does during a Microsoft outage, and one person, maybe the same one, keeps customers updated. When that is clear in advance, people act. When it is not, they wait to be told.

Where do you check, and who do you call? The Microsoft 365 status page tells you whether it is a wider outage. Bookmark it. Your IT provider is who you call. That is us, for our clients, and the first thing we will tell you is whether it is you or Microsoft.

What to do the moment it hits

In order, because order is what people lose in the moment.

First, check whether it is just you. Look at the status page, or ask whether anyone else is having the problem. If it is a wider Microsoft outage, stop trying to fix it. There is nothing on your end to fix, and I say that from experience. Rebooting the server made no difference the last three times either.

Second, tell your team. What is down, and what to use instead. This stops the hour of rebooting.

Third, switch to your backup way to communicate. Phones, text, the other app.

Fourth, tell customers if it affects them. If you cannot take bookings or payments, say so and tell them when to try again. A customer who is told will wait. A customer who is not told will assume you are closed.

Fifth, write down when it started and what was affected. Two lines. It helps you follow up afterward, and it helps if something needs fixing once things come back.

Things that make a Microsoft outage hurt less

The plan covers the Microsoft outage. A few settings, made in advance, shrink it.

Keep key files available offline. With OneDrive and SharePoint, recent files can sync to the computer so you can still open them when Microsoft 365 is unreachable. This is a setting, not a product, and we turn it on for every client. If you do not know whether yours is on, ask.

Have a second way online. A mobile hotspot from a phone gets a few key people working again when the internet line drops. This is the fix for the Spectrum version of the outage, and it costs nothing you do not already have.

Keep contacts off the cloud. Important phone numbers in your phone’s own contact list, or on paper. It feels old fashioned. It works during every outage, which is the point.

Ask about alerts. We can set up a warning that tells you about a Microsoft outage before your customers do. It is a small thing that changes who finds out first.

There is one thing here people never ask about, so I will add it. An outage is not a backup. During a Microsoft outage your data is still there and comes back when they do. What the plan does not cover is the day your data is actually gone, from a deleted account, a mistake, or ransomware. That is a different plan, and our post on how small business ransomware attacks work explains why the two get confused and why the backup matters more.

Keep it on one page, then test it once

Write down the five things above on a single page. That is your Microsoft outage plan, and it is also your internet-is-down plan, because they are the same page. Put it somewhere you can reach without your main systems, printed or in a separate app. Review it twice a year so the names and numbers stay current, because they will not.

Then, once, on a quiet afternoon, pretend there is a Microsoft outage and walk through it with your team. Who notices first? Who calls it? Can the front desk actually reach the customer list? Does the printed phone list still have the right numbers? It takes half an hour and it finds the gaps that would otherwise cost you a morning. A plan that has never been tried is a guess, and I would rather you find out on a Tuesday afternoon than on the morning it is real.

This is the small business version of what we build out in full under disaster recovery for clients who need more than a page. Most do not. One page, tested once, covers a lot.

Frequently asked questions

Is the cloud always available? No. Cloud services are reliable, but they have outages, and the biggest providers go down too. A Microsoft outage like the CrowdStrike event in 2024 took millions of computers offline in a few hours. Assume one will happen eventually and plan for it.

What should a Microsoft outage plan include? Which tools are critical, a backup way to reach staff and customers, where to find the essentials if the main system is down, who is in charge during the outage, and who to call. One page is enough.

What if the internet goes down, not just one app? Plan for that too. A phone hotspot gets key people back online, and a phone call still works when the systems do not. Keep important numbers somewhere that does not need the internet.

How can my team keep working during a Microsoft outage? Open files already synced to the computer, switch to phone or text to stay in touch, and handle anything urgent on paper until service returns.

How long does a Microsoft outage last? There is no set answer, and I would be guessing if I gave one. Some are fixed in minutes, others take most of a day. That is the reason to plan, since you cannot speed it up from your end.

Whose job is the plan? Yours, with help from your IT provider. We can tell you which of your tools are most at risk, turn on the offline settings, set up the alert, and help you write the page.

If you would rather not start from a blank page, we put together a short first aid kit for exactly this kind of morning, the outage, the locked account, the “something is wrong and nobody knows what.” You can grab the IT first aid guide and use it as the starting draft.

Featured image: Pixabay

Leave a Reply