Illustration of an office desk where a laptop shows a blue cannot-connect screen while the desk phone beside it lights up with an incoming call

Opinion

Microsoft 365 Outage: Email Went Dark. Did Your Phones?

On Thursday, offices from Capitol Hill to city hall lost their inboxes. Here is what the people who kept working did.

Published: | Last updated:

If you work in an office, you probably remember where you were around lunchtime on Thursday. You hit send, and nothing happened. You tried again. Then somebody down the hall said the words every office knows by heart: "Is your email working?"

It was not just you. It was not just your building. Before the afternoon was over, congressional staff in Washington could not read their mail, a state government was texting its employees to tell them email was unavailable, and a city supervisor in San Francisco told a reporter that most of his work with city staff had moved to phone calls.

Read that last part again. When the email stopped, people picked up the phone.

I have been in technology for 48 years. I built one of the early internet providers in this part of North Carolina, so I have been the person whose servers were down while customers waited. I am not writing this to throw rocks at Microsoft. Everything built by people fails sooner or later, and that includes anything my company runs. I am writing because Thursday was a free lesson, paid for by somebody else, and I would hate for you to waste it.

Local Business VoIP is the small-business site of Carolina Digital Phone, Inc. We have been keeping North Carolina organizations connected since 2000. Here is what happened, what it showed, and what I would do about it this month if I ran your office.

Quick answer

On November 12, 2026, a Microsoft 365 outage cut off Outlook email for hours and put Teams, SharePoint, and Copilot at risk, after a number of Microsoft's servers unexpectedly dropped out of service. Businesses whose phones ran on a separate system could still call and be called. The lesson is not to leave Microsoft. It is to make sure one provider's bad day cannot take away every way your customers reach you.

Microsoft 365
Microsoft's online bundle of work tools, including Outlook email, Teams, SharePoint, OneDrive, and Copilot.
Exchange Online
The Microsoft service that stores and delivers Outlook email. It was at the center of Thursday's trouble.
Single-provider risk
The exposure you carry when one company runs every way your business communicates.
Out-of-band channel
A way to communicate that does not depend on the system that is down. A phone call or a text when email has failed, for example.
Hosted phone system
Business phone service run from a provider's data centers and reached over the internet. Also called hosted VoIP or a cloud phone system.

What happened in the Microsoft 365 outage on November 12, 2026?

A large number of Microsoft 365 customers lost access to their Outlook mailboxes late Thursday morning, and the trouble spread through the afternoon. This is the short version, pieced together from Microsoft's own updates and the day's reporting:

  • Morning. Microsoft reported a Teams problem in North America and later said it had been fixed.
  • Late morning. A second, bigger problem began. FOX 13 Seattle reported that people across the country could not connect to Outlook, and that Microsoft was investigating mailbox access in the Americas.
  • Early afternoon. Fox Business counted more than 130,000 problem reports on Downdetector by 2 p.m. Eastern. Microsoft said Exchange Online, Teams, SharePoint Online, Copilot, and its Defender security service might all be affected.
  • The cause, so far. Microsoft said this was not a flood of traffic. As ABC News reported, servers stopped passing their automated health checks and dropped out, which overloaded the ones that were left. The company suspected the piece of software that judges whether a server is healthy, and said it had found no recent change that lined up with the start of the problem.
  • The response. Microsoft paused all updates, moved traffic away from the trouble, restarted servers, and began rolling out a new way of running those health checks.

I am writing this on Thursday evening. Microsoft was still bringing servers back and had not published a final cause, so some of these details will sharpen in the coming days. You can follow the company's own account on the Microsoft service health page.

Who was affected by the Microsoft outage?

Nearly everyone who runs an office on Microsoft 365 was affected to some degree, from Congress down to the three-person firm on Main Street. A few snapshots from the day show what it looked like on the ground:

  • Capitol Hill. Politico reported that congressional offices went without email for much of the afternoon and that some work was put on hold. In a detail I will not forget, the reporters could not reach the Senate office that handles technology, because of the outage itself.
  • State government. In Massachusetts, the state sent its employees a text message to tell them that email and other Microsoft services were unavailable, according to GBH News.
  • City hall. In San Francisco, a city supervisor told the San Francisco Chronicle that most of his communication with city staff had shifted to phone calls, because nobody could send him anything.
  • Everybody else. One trade publication summed up the mood by reporting that offices in its industry simply went home early.

Notice the pattern in the first three. A state reached its people by text. A city official worked by phone. And the reporters trying to cover the story were stuck because the office they needed could not be reached. Thursday was a live demonstration of one idea: when your main channel fails, your second channel is all you have.

Was this the same as the 2024 "blue screen of death" outage?

No, it was a different kind of failure, even though the pictures in your memory may run together. In July 2024, a security company called CrowdStrike sent out a faulty update that crashed Windows computers around the world. Microsoft later estimated that about 8.5 million machines were hit. Screens turned blue, flights were grounded, and CNBC reported that Microsoft had also been dealing with a separate cloud outage around the same time.

On Thursday there were no blue screens. Your computer worked fine. It just had nothing to talk to. The 2024 event broke the machines on people's desks. The 2026 event broke a service those machines depend on.

Different causes, same lesson. In both cases, thousands of organizations discovered on the same morning that something they had never thought about was holding up everything else. I wrote about a cousin of this problem last week in if the White House can be hijacked, your business network can too. Size does not protect anyone. Planning does.

What is single-provider risk, and why did Thursday expose it?

Single-provider risk is what you carry when one company runs every way your business communicates. Thursday exposed it because, for many offices, email, chat, video meetings, shared files, and the AI assistant all come from the same place, so they all wobbled together.

There is nothing foolish about buying a bundle. It is cheaper, it is simpler, and most days it works beautifully. I use bundled tools myself. The trouble comes when the bundle quietly swallows your last independent channel. Here is how an outage like Thursday's lands on a typical small office:

If your office suite has an outage, what still works?
Channel During an outage like Thursday's Why
Outlook email Down or unreliable It was the service at the center of the outage.
Teams chat and meetings At risk Microsoft listed Teams among the services that might be affected.
Shared files in SharePoint At risk Same platform, same day.
Phones that run inside Teams At risk Your phone system shares a provider with everything else that is struggling.
Phones on a separate hosted phone system Working Different company, different data centers, different day.
Business texting from your office number Working It rides on the phone platform, not the email platform.
Personal cell phones Working, but off the books Customers get private numbers and the office loses the record.

That last row matters more than it looks. When the official tools fail, your people will improvise with whatever is in their pocket. If the only backup is personal cell phones, your customers end up with private numbers and your business ends up with no record of what was said. I covered the fix for that in business calls on mobile without your personal number and in business texting from a work number.

Should your business phones run inside Microsoft Teams?

They can, but I would think hard before putting your phones in the same basket as your email, your chat, and your files. Microsoft sells calling plans that turn Teams into an office phone system, and for some organizations that is a reasonable choice. The price of that convenience is that on a day like Thursday, your backup channel belongs to the same provider as the channel that just failed.

To be fair, I have not seen reports that Teams phone calls stopped on Thursday, and I am not claiming they did. Microsoft listed Teams among the services users might be unable to reach, and that is all I know tonight. My point is about how you set things up, not about one afternoon. The phone is the tool people reach for when everything else is broken. It should be the last thing to share a single point of failure, not the first.

There is a middle road. If your people like working in Teams, your phone numbers and call routing can live on an independent phone platform that connects to it. On a normal day nobody notices the difference. On a bad day, your main number still answers, your greeting still plays, and calls still ring the business phone app on your staff's cell phones. I compared the tradeoffs of leaning on one provider in single carrier versus multi-carrier.

What should a small business do before the next outage?

Before the next outage, make sure you have one working channel that does not depend on your email provider, and make sure your people know to use it. None of this is expensive. Most of it is an hour's work.

  1. Keep your main number on its own platform. Your phone service should come from a different company, on different equipment, than your email. Then one bad afternoon cannot take both.
  2. Turn on texting from your business number. Massachusetts reached its workforce by text on Thursday. You can do the same for staff and customers, from the number they already know.
  3. Get your contact list out of your inbox. If the only copy of your customers' and employees' phone numbers lives in Outlook, you lost it on Thursday too. Keep a copy in your phone system, on paper, or both.
  4. Record an outage greeting today. Something like: "Our email is down right now. Please stay on the line or text this number and we will take care of you." Save it so you can switch it on in a minute when you need it.
  5. Bookmark the status pages on your cell phone. Know where your email provider and your phone provider post trouble, and look there before you spend an hour restarting your router.
  6. Practice once. Pick a slow afternoon, pretend email is gone for two hours, and see what breaks. I laid out a full drill for power and internet failures in hosted VoIP vs. on-premise PBX for business continuity.

A simple test: if your email went down right now, could a customer still reach a live person at your business within two minutes? If you are not sure, that is your project for this month.

Ready.gov has a sound general framework for business continuity planning if you want to go further than phones. And if missed calls are already costing you on ordinary days, start with how to reduce missed business calls.

Could your phone provider go down too?

Yes, and any provider who tells you otherwise is selling something. Carolina Digital Phone can have a bad day. So can every carrier in the country. What you want to know is how a provider is built for that day and how they treat you when it comes.

These are the questions I would ask any phone company, including mine:

  • Where is your equipment? We run our platform from data centers in downtown Greensboro, Research Triangle Park, and Dallas, so losing one site does not take down your service. I explained how that works in geo-redundant VoIP service.
  • What happens to my calls if my office is offline? They should follow rules you set ahead of time: ring mobile apps, ring another location, or go to voicemail that arrives by text or email.
  • How will I find out about a problem? You should hear from a channel that is not part of the problem.
  • Who answers when I call for help? A person who knows your account, or a ticket number?

Notice that the answer is not to find the one provider who never fails. That provider does not exist. The answer is to stop stacking everything on one. Your email and your phones should not be able to fail for the same reason on the same afternoon. I went deeper on building for bad days in telecom resilience and on what to do in the moment in when your business phone breaks.

Why does a local provider matter on a day like Thursday?

A local provider matters on a day like Thursday because you can reach them. Thousands of organizations spent the afternoon refreshing a status page and waiting. Nobody at a company that size is going to call your office to tell you what to do next, and that is not a criticism. It is just what happens when a provider has hundreds of millions of users.

We are a small company on purpose. Voice, business messaging, and AI receptionist service are all we do, and when a customer calls us on a bad day they talk to someone in North Carolina who knows their setup. That is what I mean when I talk about doing business with people you know, like, and trust. You can read more about why businesses choose Carolina Digital Phone, the history of the company, and what it means to treat your phone provider as a trusted communications partner. The parent site also has an overview of how we approach business continuity.

Microsoft will fix this, publish a report, and be better for it. The real question is whether you will be. On Thursday the email went dark and the people who kept working were the ones who could still pick up a phone. Make sure that is you next time.

Frequently asked questions about the Microsoft 365 outage and business phones

What happened in the Microsoft 365 outage on November 12, 2026?

On Thursday, November 12, 2026, many Microsoft 365 customers lost access to Outlook email, and Microsoft warned that Teams, SharePoint Online, Copilot, and other services could be affected. Microsoft said a number of its servers became unexpectedly unavailable, which overloaded the ones still running. News reports described offices without email for much of the afternoon.

What caused the Microsoft 365 outage?

Microsoft said the strain did not come from extra traffic. A number of servers stopped passing automated health checks and dropped out of service, which put too much load on the rest. As of Thursday evening the company suspected a component that processes server health and had not published a final root cause.

Was the November 2026 Microsoft outage a cyberattack?

Nothing Microsoft published on Thursday described it as an attack. The company's updates pointed to servers failing health checks inside its own infrastructure. Wait for Microsoft's final incident report before drawing conclusions.

Was this the same as the blue screen outage in 2024?

No. The July 2024 blue screen event was caused by a faulty update from the security company CrowdStrike that crashed about 8.5 million Windows computers. The November 2026 outage was a problem inside Microsoft's own cloud services. Computers kept running, but email and other online tools could not connect.

Did phones stop working during the Microsoft 365 outage?

Ordinary business phone service was not part of the outage. Businesses with a phone system separate from Microsoft 365 could still make and take calls. Microsoft did list Teams among the services users might be unable to reach, so organizations that use Teams as their phone system had more at risk.

Should my business phone system run inside Microsoft Teams?

It can, and many organizations like the convenience. The tradeoff is that email, chat, meetings, files, and phones then depend on one provider on the same day. Keeping your phone numbers and call routing on a separate phone platform gives you a working channel when the other one is down.

What is single-provider risk?

Single-provider risk is the exposure you take on when one company runs every way your business communicates. If that provider has a bad afternoon, email, chat, meetings, and phones can all fail together. Spreading critical channels across independent providers means one outage does not silence you.

How can a small business stay reachable when email is down?

Keep your main phone number on a platform that does not depend on your email provider, turn on business texting from that number, and keep a contact list for staff and key customers somewhere other than your inbox. Decide ahead of time what greeting callers will hear and who answers.

Can a hosted phone provider have an outage too?

Yes. Any provider can, including ours. Ask where their equipment is located, what happens if one site fails, how you would be notified, and whether you can reach a person when it matters. Then make sure your phones and your email do not share the same single point of failure.

How do I check whether Microsoft 365 is down?

Microsoft posts incidents on its service health status page and on its Microsoft 365 Status account on X. Administrators see more detail in the Microsoft 365 admin center. Bookmark the status page on your phone, because you may not be able to reach it through tools that are part of the outage.

Could your customers have reached you on Thursday?

If you are not sure, call us. A local engineer in Greensboro will look at how your phones, texting, and email depend on each other and tell you plainly where you are exposed. No charge and no pressure. If your setup is already sound, we will say so.

Prefer a quick callback from a local onboarding engineer? Leave your number at HostedBusinessTelephone.com, or get a short evaluation of your phone needs at LocalVoIPProvider.com. Already a customer? The Digital Voice Plus app keeps your business line on your cell phone.