When email or chat stops working, first find out whether the problem is on the provider's side or yours. Microsoft says to check service health to see whether a problem is a known issue before you call support or spend time troubleshooting. If it is the provider, switch to your backup email, phone and file plan and wait it out.
That is the short answer. The rest of this post is for the owner or office manager who has to keep the phones answered and the clients calm: how to tell the two kinds of outage apart quickly, the fallback plan you can set up soon without an IT department, and when it is worth paying someone to build the plan for you.
Why this is on your mind this week
On November 12, 2026, many Microsoft 365 users could not get to their email. It was not a short blip. At 11:30 UTC on November 13, Microsoft still listed the incident as ongoing, more than 19 hours after the first mailbox errors. One summary puts the whole event at November 12 to 14, with problems reported across Outlook, Teams and Copilot.
In plain words: nobody hacked anyone. Something broke inside Microsoft, and every business that relies on it waited.
In January 2026, a Microsoft 365 outage affected Outlook and other services, with Defender and Purview also down. At the peak of that one, 15,000 reports were filed on Downdetector.
That last number is about very large companies, not a small local office. Splunk's research found downtime costs each Global 2000 organization $300 million a year, or over $900,000 every hour. Your number is smaller. But the shape of the loss is the same: missed calls, slow invoices, clients who could not reach you, and staff sitting idle.
The problem, in an owner's words
Here is how it usually goes in a small office. Email freezes first thing in the morning. Someone restarts their laptop. Someone else says the team chat is down too. The office manager calls the IT person, who is already on the phone with five other clients. Half the team is now trying fixes that cannot work, because the problem is not on their computer at all.
Check your own setup before assuming the lost time is unavoidable, because some of it may be. You cannot stop Microsoft from having a bad day. You can decide ahead of time:
- who checks whether it is the provider or you,
- how clients reach you while email is down,
- where staff find today's files and schedule,
- and who tells the team what to do.
That is an outage plan. It does not need to be long. It needs to exist before the outage, not during it.
Step 1: Tell whether it is Microsoft or just you (5 minutes)
Check Microsoft's own status first
If someone in your office has admin access, open Service health in the Microsoft 365 admin center. Microsoft says known service incidents are announced to customers through Service health in the Microsoft 365 admin center.
If you cannot sign in to the admin center, Microsoft says to use its service status page to check for known issues that prevent you from signing in to your tenant. Bookmark that page on every manager's phone now, while things work. The Microsoft guide to checking service health walks through both.
You do not need to make everyone a full admin to see this. Microsoft says people with [the Service Support admin or Helpdesk admin role](https://learn.microsoft.com/en-us/microsoft-365/enterprise/view-service-health?view=o365-worldwide) can view service health. Give that role to your office manager so they are not waiting on IT to answer one question.
If Microsoft says everything is fine
Then the problem is probably closer to home. Common causes we see:
- One person's password expired or their sign-in prompt is stuck.
- The office internet is down (test by loading any website on a phone over the office network, then over mobile data).
- A third-party tool connected to your email account, such as an email filter, backup app or phone system, is failing.
- Someone changed a setting in your account.
That last point matters for expectations. Microsoft does not count interruptions caused by third-party providers or changes made in your own environment as service incidents. If your email filter vendor breaks your mail flow, Microsoft's status page will stay green, and you need to call that vendor, not Microsoft.
Check what already happened
Microsoft's Issue history tab shows incidents and advisories resolved within the last 7 or 30 days. Note that planned maintenance events are not shown in service health; Microsoft says you can track them by staying up to date with the Message center. Check the Message center regularly for planned maintenance notices, so a quick weekly glance can help you avoid surprises.
Step 2: Build your backup plan this week
This does not call for special software. You need a few decisions written down and tested once.
Backup email: a second way to reach clients
When your email is down, your clients still send you messages. Those messages are usually delayed rather than lost, but you cannot reply. Set up:
- A shared fallback address on a different provider. Think of it as a basic mailbox on a separate service, kept for outages. Put it in your outage plan, not on your website.
- A short auto-message template you can post to your website banner and social profiles: "Our email is delayed due to a provider outage. Call us at (number) for anything urgent."
- A client contact list saved outside your email system. If your client phone numbers live only in your email program, you cannot call anyone when it is down. Export it monthly to a second location.
Backup phones and chat: replacing Teams for a day
If your office phones run through Teams, an outage can take your phone lines with it. Decide now:
- Which cell phone the main line forwards to, and who knows how to turn forwarding on.
- A group text or second chat app the team will use to coordinate while the main chat is down.
- Who posts the "we are working, here is what to do" message to staff, and where.
Test call forwarding once. Many offices discover during an outage that nobody remembers the login for the phone portal.
Backup files: what staff need for one day of work
During an outage, the files in OneDrive and SharePoint may be unreachable. Ask each role: "What do I need to work for one day without Microsoft?" A front desk needs today's schedule and the client phone list. A bookkeeper needs open invoices. An attorney needs the filing calendar.
For real backups, follow the 3-2-1 guideline: 3 copies of important files, 2 types of storage media, and 1 copy off-site. CISA also recommends a backup solution that automatically and continuously backs up critical data and system configurations. Read the CISA small business backup guide for the plain-language version.
A backup you have never restored is a guess. [CISA says to](https://www.cisa.gov/audiences/small-and-medium-businesses/secure-your-business/back-up-business-data) test backups so your team can restore data both fully and partially, and roll back at least seven days. [CISA also says](https://www.cisa.gov/audiences/small-and-medium-businesses/secure-your-business/back-up-business-data) backups should be protected with physical security, encryption and offline copies.
Backup sign-in: so you are never locked out of your own account
This one is less obvious and more important. Picture your one admin account failing to sign in because its sign-in method is caught up in the outage: you would have no way to see service health, reset passwords or change mail settings.
Microsoft recommends two cloud-only emergency access accounts permanently assigned the Global Administrator role. It advises using a different sign-in method for those accounts than for your regular admin, for example a FIDO2 security key if your normal admin uses the Authenticator app. Microsoft says to store emergency access credentials in secure, fireproof safes in separate secure locations and to test regularly, for example every quarter, that the accounts can sign in. The Microsoft emergency access guide covers the details.
The same idea applies to your staff. Microsoft warns that relying on a single access control, such as multifactor authentication, can leave you open to access failures if that control becomes unavailable or misconfigured. It recommends giving each user multiple sign-in methods that use different channels, such as the Authenticator app, an OATH token and SMS. Keep MFA on; CISA says it should be required of all users, starting with privileged, administrative and remote access users. Just do not rely on one way in.
Step 3: Write it down on one page
CISA says to develop an incident response and disaster recovery plan with roles and responsibilities, and to test it often. For a small office, that can be a single page. Here is a checklist you can copy.
| Item | Owner | Done this week? |
|---|---|---|
| Status page bookmarked on managers' phones | Office manager | ☐ |
| Service health role given to office manager | IT / admin | ☐ |
| Fallback email address on a separate provider | Owner | ☐ |
| Client contact list exported outside your email system | Office manager | ☐ |
| Main line forwarding tested to a cell phone | Office manager | ☐ |
| Backup team chat or group text agreed | Owner | ☐ |
| "One day of work" files saved per role | Each team lead | ☐ |
| Backups have an off-site copy and a restore was tested | IT / backup vendor | ☐ |
| Two emergency admin accounts created and tested | IT / admin | ☐ |
| Website banner and client message templates ready | Marketing / owner | ☐ |
Print it. Put a copy somewhere you can reach without signing in to anything.
Hypothetical: a 15-person accounting office in Tustin
Hypothetical: it is mid-morning in tax season and Outlook stops loading. The office manager opens the status page on their phone and sees a known Microsoft incident. They send the pre-written group text: "Microsoft outage, not us. Phones forwarded to the front desk cell. Use the printed client list. Do not restart anything." The website banner goes up. Staff work from the day's files saved to a separate drive. Nobody spends an hour reinstalling Outlook, and clients who call get a person instead of voicemail.
Nothing in that story requires new technology. It requires decisions made in advance.
Pitfalls we see in Orange County offices
- The plan lives in Outlook or SharePoint. If the outage takes down the plan, you do not have a plan.
- One person knows everything. If the owner is the only one with the admin login and they are at a client site across town, the office waits. Spread the roles.
- Phones and email depend on the same vendor. Moving your phone system onto the same platform as your email is convenient until both go down at once. That is a trade-off to make on purpose, not by accident.
- Backups nobody has restored. Test a restore once a quarter.
- Expecting Microsoft to explain fast. For broad-impact incidents, Microsoft delivers a preliminary post-incident review within 48 hours of resolution and a final one within five business days. Useful for your records, but it will not help during the outage itself.
- Assuming it was a cyberattack. Do not let panic push staff into clicking "reset your password" emails that show up during the confusion.
When an outage plan is worth paying someone to build
A lot of the checklist above you can do yourself in an afternoon. It makes sense to bring in help when:
- You handle regulated or deadline-driven work. If you have court dates, patient messages or filing deadlines, you cannot afford to make up the plan during the outage.
- Your phones, email and files all run through Microsoft. Untangling that single point of failure is a design job, not a checkbox.
- Nobody on staff owns IT. If "the IT person" is a nephew or a vendor you call twice a year, nobody is testing backups or emergency accounts.
- You want the boring parts automated. Exporting contact lists, checking service health, and alerting staff when your provider posts an incident can all be set to run automatically. Our AI automation service can take on that kind of work, so the plan keeps running without someone having to remember it.
Our own view: for most offices of 5 to 50 people, the right first step is a short review of what depends on Microsoft and what breaks if it goes away. Our AI and operations consultation is built for that: we map your dependencies, write a short plan with you, and flag which steps to automate. If you are local, see how we work with businesses across Orange County.
What we would do first
If we sat down with your team this week, we would:
- Confirm who can see service health right now, and fix that if the answer is "nobody but IT."
- Find every place your client contact list and schedule live, and make sure a copy also sits outside your email system.
- Test call forwarding and the backup chat with a five-minute drill.
- Check that emergency admin accounts exist, use a different sign-in method, and actually work.
- Do one real file restore from backup and time it.
None of that requires buying anything new. It does require someone to own it.
Next step
Microsoft will have another bad day; what matters is whether your office is ready when it does. If you want a second set of eyes on your plan, or want the monitoring and alerts automated so nobody has to remember, book a Free Automation Audit. We will tell you what to fix first and what you can safely skip.
Sources
- CISA — Back Up Business Data (January 1, 2026)
- CISA — Cyber Essentials (October 22, 2026)
- Microsoft Learn — How to check Microsoft 365 service health (October 30, 2026)
- Microsoft Learn — Service health and continuity - Service Descriptions (July 22, 2026)
- Microsoft Learn — Create a resilient access control management strategy - Microsoft Entra ID (June 15, 2026)
- Microsoft Learn — Manage emergency access admin accounts - Microsoft Entra ID (June 5, 2026)
- Splunk — Beyond the $600 Billion Cost of Downtime: Building a More Resilient Future for Your Business (May 19, 2026)
- The Register — Microsoft 365 outage drags on for nearly 10 hours during bad night for North American infra (January 23, 2026)
- UptimeRobot — Microsoft 365 Outage, November 2026: What Happened (November 13, 2026)
- Wikipedia — 2026 Microsoft outage (November 13, 2026)