Read enough of Microsoft's incident updates from November 12 to 14 and you'll notice the same sentence, over and over:
More info under EX1550543 and MO1550821 in the Microsoft 365 admin center, as well as status.cloud.microsoft if the admin center is not available to you.
That last clause is the story. Microsoft normally tells IT admins what is wrong through Service Health in the Microsoft 365 admin center. During this outage, admins might not be able to open it. So Microsoft pointed them to a separate public page and to its @MSFT365Status account on X. The public page even explained itself: it was posted there because administrators "may be unable to access the admin center to get Service health information".
The company that makes Outlook and Teams needed a place to talk about the outage that didn't depend on Outlook, Teams, or the admin console. Your organization does too.
What happened
Microsoft first acknowledged problems on Thursday, November 12, with users in the Americas unable to reach Exchange Online mailboxes. Minutes later it warned the disruption could affect Microsoft 365 connectivity in any region. By the time it was over, Downdetector had logged reports from more than 70 countries and territories, with a peak of nearly 200,000 user reports.
Microsoft said the incident came from an issue during an earlier network capacity upgrade that surfaced after a recent network change, that it was not a cyberattack, and that a post-incident report will follow. On Saturday, November 14, it said service was fully restored. Reuters described an outage that lasted over 24 hours and reached government agencies from Australia to the United States.
This post isn't about who was at fault. It's about what happened to everyone's communication while it was going on.
The tool you use to talk about outages was the outage
When email is the thing that's down, you lose the channel you would normally use to say so.
- The BBC reported that schools in the UK asked parents to phone instead of email. At Westminster Magistrates' Court, a staff member told the BBC the prosecution hadn't been able to send papers through.
- Reuters reported delays at trading firms, some companies hindered from publishing earnings, and airlines warning customers of communication lags.
- Even once Outlook came back, Microsoft warned of delayed email delivery. A message sent during the outage can arrive late, stamped with the time it was delivered, not the time it was sent.
Every organization hit by this had the same problem on a smaller scale. Staff needed to know what was down and what to use instead. Customers needed to know whether to wait for a reply. And the usual ways of telling them ran through the platform that had failed.
Three dependencies to check before the next one
An outage at a vendor you rely on, or at your own platform, is the same test. Ask where each of these lives.
Where your status page lives
If your status page is hosted inside the system it reports on, it fails with that system. If you reach it through a login that runs on the same identity provider, it fails for the people who need to publish. Matt Berry's outage communication guide puts the second risk bluntly: if your website login runs through Microsoft sign-in, you'll be locked out right when you need it.
A StatusDashboard status dashboard runs on its own infrastructure, separate from your product, your email, and Microsoft 365. If your organization uses SSO for the admin console, keep a designated administrator on break glass access, a native email-and-password path that works even when your identity provider doesn't.
How your team reaches each other
If your war room is a Teams channel or an email thread, you have no war room when they fail. NinjaOne's guidance for Microsoft 365 outages recommends an alternate channel for staff announcements, such as SMS alerts, another chat platform, or a status page, so you aren't dependent on the affected service. One HR expert told Human Resources Director to pick a single fallback channel, announce it, and post updates at regular times even when there is nothing new to report.
For internal audiences, a status dashboard can be restricted to your office or VPN with an IP allowlist, on plans that include it. That keeps it reachable without depending on the system that's down. If you lock it behind SSO instead, check that the sign-in doesn't run through the provider having the bad day.
How your customers hear from you
Email lands in a mailbox you don't control. If a customer's mailbox is on the platform that's down, your message waits in a queue with everyone else's. Customers need a place to check and more than one way to be told.
A status dashboard is the place to check. Subscriber notifications cover the rest: depending on your plan, visitors can subscribe by email, SMS, WhatsApp, Slack, Microsoft Teams, Google Chat, or webhook. Pick the channels your customers use, and don't rely on a single one. A Microsoft Teams subscription shares a failure domain with Microsoft, so treat it as one channel among several, not the safety net. See Notifications for how delivery works.
Silence invites improvisation
When the official channel goes quiet, people build their own. Security expert Ken Munro told the BBC that when email is down, many people move to WhatsApp and other platforms, which puts sensitive data at risk. He called outages like this "a prime time for scammers," and warned that fake support messages could be used to extract passwords or install malware.
A known, official URL helps with both problems. People who are told in advance where updates will appear can check there instead of trusting a message that arrives out of nowhere. For customers, that URL is your status dashboard. Put it on your website, in your support signature, and in your help center before you need it.
A checklist you can finish this week
- ✓ Your status page is hosted outside your product and outside your email and chat platforms
- ✓ At least two people can publish updates with credentials that don't depend on the platform most likely to fail
- ✓ Customers can subscribe on more than one channel, not only email
- ✓ Your contact list for staff and key customers lives outside Microsoft 365 or whatever your primary suite is. A list you can't open isn't a call list
- ✓ You've picked a fallback channel for staff and told everyone what it is
- ✓ You have a first-update template ready, and an agreed cadence (every 30 to 60 minutes is common) for follow-ups
- ✓ The status URL is linked from your site, your help center, and your support signature
Practical rule: If the thing that broke is also the thing you'd use to tell people it broke, you don't have a communication plan yet. You have a dependency.
What a vendor-outage update looks like
If your own email is down, say so in plain language and say what to do instead. A customer-facing update could read:
Email is down for our team because of a Microsoft 365 outage. Replies to support emails will be delayed. Phone and chat are working. Our product isn't affected. Next update by 3:30 PM ET.
It names what's affected, what isn't, what customers should do, and when you'll speak again. That's the standard in The 5 Cs of Effective Outage Communication, and it applies whether the failure is yours or a vendor's. For the day-to-day habits behind it, see Best Practices for Managing a Status Page.
The bottom line
Microsoft's outage was unusual for its size, but the pattern isn't. Vendors fail. Cloud regions fail. Identity providers fail. The question is whether you can still tell people what's going on.
A status page that lives somewhere else is how you answer that question. It's the one place that stays up when your email, your chat, and your own tools don't. If you already monitor your systems, that doesn't replace it. See Status page vs monitoring for the difference.
Start your free trial and publish your first status dashboard in minutes. The next outage is coming. You just don't know the date.

