When Microsoft 365 Goes Down, There Is Nothing for You to Fix

Almost everything your business runs on now lives somewhere else. Email, documents, accounting, scheduling, payments. It is a good arrangement most of the time, and it comes with one uncomfortable property: when a provider has a bad day, you have no lever to pull.

This does not require an attacker. In July 2024 a faulty update from the security vendor CrowdStrike took down Windows machines worldwide inside a few hours. Microsoft estimated 8.5 million devices were affected. Flights were grounded, hospitals diverted, banks stopped processing. No breach, no ransomware, just a bad file shipped to production.

Microsoft 365 has had its own days where Teams or Exchange stopped working for hours at a stretch. So has every major provider. Your internet circuit has the same property, and when it goes, everything hosted goes with it.

The specific shape of the problem

When a critical service drops, staff cannot reach email or files, so the work stops. If payments or bookings run through it, revenue stops with it. Customers try to reach you and cannot, and you have no way to reach them either. People end up waiting for an all-clear that arrives on someone else’s schedule.

You also cannot accelerate it. When a hyperscale provider has an incident, your only real options are to confirm it is them and wait, which is genuinely uncomfortable for owners used to being able to do something about a problem.

So the planning is not about restoring service. It is about staying functional and keeping customers informed during a window you do not control.

Five questions a plan answers

Which tools are actually critical? Name the small handful whose absence halts the business. Email, the payment system, the booking tool, whatever applies. Deliberately exclude the things you could live without for a day, because a list of everything is a list of nothing.

How will people reach each other? You need a channel that does not depend on the system that is down. If Teams is your only internal communication and Teams is the outage, you have no plan. Mobile numbers, a group chat on an unrelated app, or plain text messages all work.

What has to be reachable offline? Customer contact lists, key vendor numbers, and the documents you would need to keep operating. A printed copy or a synced file on a phone is entirely adequate.

Who decides? Name the person who makes calls during an outage and the person who updates customers. When that is settled beforehand, people act. When it is not, everyone waits to be told.

Where do you look, and who do you call? Know the provider’s status page, and know which number reaches your IT provider.

The first fifteen minutes

Confirm the scope before anything else. Pull up the vendor’s status page, or find out whether anyone outside your building is affected. Establishing that the fault is upstream is the most valuable thing you can do early, because it stops your team from burning an hour rebooting equipment that was never involved.

Tell your staff what is down and what to use instead. Move to the backup communication channel. If customers are affected, say so plainly and tell them when to try again, because silence during an outage does more reputational damage than the outage itself.

Note the start time and what is affected. Two lines is enough, and it makes the follow-up afterward far more useful.

Things that reduce the pain in advance

Files synced for offline access are the highest-value item here. OneDrive and SharePoint can keep recent documents on the device itself, so people can still open and edit what they were working on while the service is unreachable. Raise it with whoever manages your environment.

A mobile hotspot gets a few key people working when the circuit rather than the cloud is the problem. Bookmarked status pages tell you within seconds whether it is them or you. Contact lists kept off the internet cover a total outage. And many providers can configure alerting that warns you about a degradation before your customers start calling.

Keep it to one page

This should be a single page, stored somewhere reachable without your primary systems, printed or in an unrelated app. Critical tools, backup communication channel, where the essentials live, who is in charge, who to call. Revisit it every six months, because staff turnover is what turns a good plan into a list of disconnected numbers.

Putting it together

MVP Network Consulting builds this with businesses across Buffalo and Western New York, including the configuration work behind it: offline file sync, outage alerting, and a realistic view of which of your tools carries the most risk. If your team’s current plan is to wait and hope, an afternoon fixes that. Get in touch.