Episode 196: What the Microsoft Outage teaches us about crisis communications
LESS CHATTER, MORE MATTER PODCAST | 19 NOVEMBER 2026
When Microsoft Outlook, Teams and Copilot crashed on Friday 13 November 2026, hundreds of millions of users across 74 countries were left dealing with disrupted services. For some, it meant an unexpected break from emails. For others, including critical services and businesses, the consequences were far more serious.
However... beyond the technology failure, the outage provided a timely case study in crisis communication.
In this episode of the Less Chatter, More Matter podcast, we're delivering six important lessons communicators can take from Microsoft's response, including why technical jargon has no place in customer updates, why announcing progress too early can damage credibility, and why addressing people's biggest fears should be an early priority.
We give you the rundown on what to do and what NOT to do in times of crisis, alongside how this has become the perfect case study in all of the above. The big takeaway however remains that: your communication channels might fail, but your responsibility to communicate doesn't.
Listen now and take six practical lessons back to your crisis communication planning... or, just ask us to help you prepare for it here.
Links mentioned in this episode:
-
Mel: [00:00:00] Friday the 13th has always been a little spooky, so it was quite the coincidence that last Friday, 13th of November, happened to also be the day when Microsoft Outlook, Teams, and Copilot crashed spectacularly into the virtual sea.
There were disruptions in 74 countries, with the outage lasting almost 24 hours and hundreds of millions of users impacted worldwide. We're not just talking about office workers like me not being able to send emails. The New South Wales Bail Court, for example, was delayed with bail applications pending.
The Philippines Supreme Court and airlines like Alaska Air were also impacted. For some, it was a welcome break from work, as we saw from the celebratory memes. For others, it was extremely annoying, especially for critical services and small businesses. And across it all, there are some very clear lessons to be learned for professional communicators.
What are they? Well, stay tuned, because that's what today's episode is all about[00:01:00]
Hello, friend, and welcome to this week's episode of Less Chatter, More Matter, the communications podcast. I'm recording this le- episode on the lands of the Yuggera and Turrbal people here in Meanjin, Brisbane. And if we haven't met before, my name's Mel. And on today's episode, we're looking at a very recent case study on what to do and what not to do in a crisis, particularly one that impacts communication channels.
So, let's get into it. And the first one is ditch the jargon or just get the comms people to actually write the messages. Leave the tech bros out of it. Microsoft was putting on fairly regular updates, but the language was so technical and so convoluted that the average user was not going to be able to understand it.
And it wasn't just technical jargon either. There was a lot of corporate buzzwords as well. So here's an example I saw. This is from a Microsoft update. "We've monitored the status of the [00:02:00] changes applied to improve serviceability and confirmed that the change is not taking as expected." So I'll just pause there, because in shorthand, that means the changes that we put through haven't worked.
"We're identifying alternate workstreams that can be applied to increase capacity in the face of sustained traffic management imbalances." I have no idea what that actually means. Here's another. "As part of our ongoing efforts to advance the recoverability of our front-end servers, we're evaluating traffic controls that can be applied to increase capacity and stability.
This includes traffic optimisation actions such as traffic throttling, protocol adjustments, and failover routing intended to improve stability in active regions." What does that even mean? To the average user, that is so useless, and why is it of interest to them at all? This is a related lesson here, that companies like Microsoft, in crises like these, need to be thinking about what their users are concerned about.
So for example, they should've been answering questions like, "Will I have to rewrite my emails, or will they [00:03:00] eventually go through? When will I know if my emails are back online? What will I see when that happens?" Microsoft did actually put out a message about what they called the extended 48-hour email timeout window, but if you don't know what that is, you wouldn't know that it simply meant your emails still exist, and they will arrive eventually.
So top lessons and tips here are, number one, get the comms people in the room quickly and let them craft the messages. Number two, if you are not bringing them in or you just don't have comms people, then avoid the jargon and corporate speak. Use the language that makes sense to your customers. Number three, answer their questions up front in plain language, and also try and use a structure like what, so what, now what to shape your messages so they're actually coherent and easy to follow. The second one that I want to talk about as one of the lessons learned is don't announce progress if you haven't made any.
That just gives people false hope. It is a fine line between being positive and optimistic and then simply [00:04:00] not being open and honest. And the reality is that in crisis situations like these, and any crisis really, the situation can change really quickly and everything you said earlier then becomes rendered obsolete.
The case in point with Microsoft. In one of its earlier statements, it said the company was seeing encouraging recovery progress with service availability and email delivery performance improving across a growing portion of affected Microsoft 365 infrastructure. In plain English, I'm pretty sure that means they were seeing some signs of services and emails coming back online; But more than 12 hours later, Microsoft was using the words marginal success.
Every time you put out a positive, optimistic update without the data to back it up and then it's proven wrong, you chip more away from your brand's credibility, and it makes every subsequent update even harder for people to believe. So the tips here are, be realistic about your progress. You can actually use this as an opportunity to give a peek behind the scenes [00:05:00] and talk about the different potential, uh, scenarios that you're exploring.
And also don't be too positive too soon if you can't back it up. Sometimes this might come from a culture of where people are fearful of sharing bad news with their bosses, but that's a whole other issue. So that's number two, don't announce progress too quickly if you can't back it up. Number three, rule out the scariest potential scenario if you can, and do it early.
So this one is something Microsoft actually did do right. Upfront, very early on, they addressed the biggest fear, which would be a cyber attack, and which thankfully proved to not be the case. Now, human brains are wired to detect potential threats. It's just how we work. We also have availability and recency biases taking place.
So meaning, whatever is fresh in our minds becomes the thing we focus on or we make a link to. So for example, let's say you're looking at buying a car and you're interested in the new Toyota RAV4. Suddenly, you start seeing Toyotas [00:06:00] everywhere on the road when you're out and about. They were always there, but your availability bias has kicked in, so now you've started noticing them.
So in a case like this, and given so many recent examples of data breaches and cyber attacks, it's obvious that people will wonder right away if it's a cyber incident. Once you've got the worst fears addressed, then people's brains can calm down and be less threat alert, and it means you can then start talking about the real issues and what people can expect, what it means for them, and so on.
So the tips here are, in the scenario planning you would have done as part of your crisis readiness, I hope, you should be considering what the biggest fears will be for people, not just the biggest risks to your business, and how you will address those. And if you haven't already got those planned, then get them done now.
This should be a big wake-up call. So number four is update for the different time zones that you operate in. For geographically dispersed companies and customers, you can't expect one message [00:07:00] globally to do the trick. What is relevant for people in North America likely won't be relevant for people in the Asia-Pacific, for example.
So in this case, the outage was initially reported in the Americas, but it was in the very early hours of the morning here in Australia. So when we woke up, the crisis was already a few hours old, but all the updates were timed and framed for US business hours. So for example, "We'll update again at 11:00 AM CT time," which means nothing to anyone else in the rest of the world.
I even noticed in some news clippings that US media networks were reporting on the outage as a USA outage, not a worldwide outage. Now, that aside, it's an important lesson. You need to have localised comms for different regions. It shows that you see your customers and their different needs, but it also means they'll get more relevant information and be a little less annoyed with you, hopefully.
So the tips here are global organisations need to have updates for each region as they start their day. If you can't do that [00:08:00] centrally, then right now in your crisis planning, set up a network of comms people around the world who can assist you when you need it. And also make sure those comms are relevant for different regions in terms of the information you share, the contact details, and the timing of the update. Now, the fifth lesson here is that someone else's crisis can become yours.
We have seen this plenty of times with organisations who use third-party platforms, and those platforms are then hacked, but it's your business's customers' data that's been stolen. In many crises, we need to communicate about an issue or a failure we didn't actually cause, and we can't wait for the other party to contact our employees and our customers and our stakeholders.
That's our job. We have to be proactive. Because honestly, they don't care about the third party, especially if they didn't even know it existed to begin with. They care about their data, which they gave you, the service they expect of you, and what you're going to do about it. Now, in this Microsoft incident, for example, New York [00:09:00] City Emergency Management had to warn residents of delays when contacting city agencies by email or using online city services.
So they did the contacting, and again, wasn't their fault, but they had to. Many businesses around the globe couldn't process customer requests or directly reach their employees, and that damages their reputation as they become seen as difficult to work with or unresponsive. So when putting out messages about third-party issues, you do need to strike a balance so that you're being clear about what happened, but don't throw the other party under the bus because you still need to work with them, and you need their cooperation to sort it out, especially in the crisis recovery phase.
So your messages need to be transparent about the cause of the issue, but also talk to what you and the other party are tr- doing to try and fix it. So my top tips here are have holding statements ready for when a third party fails, whether that's a hacking or their service just crashes and burns spectacularly, and [00:10:00] know who is going to tell your customers and staff and how.
But that brings us to the next tip or the next lesson out of this scenario, and that is have your backup channels. This is crisis comms 101. You need to have backup channels set up and ready to activate when you need them. It's something I've advised companies on for many, many years. So for example, let's say the server your website is hosted on goes kaput or your website is hacked.
Do you have a backup site sitting somewhere that you can activate, even if it's just to use it for basic written updates to people? What if a nefarious actor manages to hack your social media channels? How will you address that? In the case of the Microsoft outage, if you couldn't reach your staff via email or Teams, what other options did you have?
Did you have a system somewhere where you could text them? Do you have a one eight hundred number that's a staff hotline where you can host recorded messages? Do you have an employee app that you can tap into? [00:11:00] For those organisations who hadn't th- thought through an event like this, they would have really struggled last Friday to reach their people and their customers effectively.
So my top tips here are recognise that single vendor dependence is a communication risk, not just an IT risk. Microsoft is the great example of this. Entire businesses have built their entire tech stacks on one vendor's platform, and this is what happens when that vendor fails. And also, have your backup channels set up and documented in your crisis communication plans.
And more importantly, make sure you are running scenarios and testing those plans regularly so people are actually educated in how they work. And the biggest thing here is remember that trust erodes over time. Microsoft has had major outages previously this year, and this just continues to damage their reputation, so that crisis recovery piece is going to be super, super important for them. So it's now time for our episode [00:12:00] recap, but before we do that, I just want to do a little bit of a shout-out to everybody who has so far left a review or rated the show on your podcast app of choice.
It really does mean the world to me, and if you haven't yet and you really are enjoying the show, please just pop in, do a five-star review, leave a few words if you can. I would really love that. So today's episode, we talked all about what happened last Friday the 13th and the Microsoft outage, and the lessons as communicators we can learn.
And the first is ditch the jargon and the corporate speak. Get comms people in the room, get them to draft the messages. The tech bros can provide all of the, I guess, accuracy checking, but the language they use is not the language your audience uses. Answer your customers' questions up front or your, or your audience's questions up front in plain language, and try using a structure like what, so what, and now what to shape your messages.
The second lesson was don't announce progress if you haven't made any. Be [00:13:00] realistic about your progress. Make sure you've got data to back it up, and remember you can mention different potential scenarios that you're actually exploring. The third lesson was rule out the scariest potential scenario if you can and do it early to allay people's fears, and then focus on the other issues.
Number four was make sure that you are updating for different time zones and different regions around the world. Global organisations need to have updates for each region as they start their day, and if you can't do that centrally, then find other ways to do it. Number five, someone else's crisis can become yours, so have those holding statements ready for when a third-party platform fails, whether it's been hacked or their service just crashes and burns, and know who is going to tell who about what's happened and how they're going to do that.
And number six, have your backup channels. Make sure you're recognising single vendor dependence as a communication risk, not just an [00:14:00] IT risk, and have those backup channels set up and documented in your crisis communication plans. All right, team. Hopefully that was helpful for you and you've all taken away a few things that you can take back to your businesses and start implementing into your crisis comms plans today.
As per usual, if there's anything you'd like us to cover on the show, do let us know. We've only got a few left for this season, but I'm all open to ideas for next year as well. So in the meantime, keep doing amazing things and bye for now.

