The Friday the 13th Microsoft outage was more than a technology failure. It was a global reminder of how quickly an organisation's ability to operate, communicate and maintain stakeholder confidence can unravel when the systems it depends on stop working.
The disruption affected users across 74 countries, lasted almost 24 hours and impacted hundreds of millions of people. Microsoft Outlook, Teams and Copilot were among the services affected, with consequences extending well beyond the inconvenience of a few missed emails.
Courts experienced delays, airlines faced operational challenges, government services struggled to reach the public, and businesses found themselves unable to communicate with employees and customers through their usual channels.
For organisations around the world, the incident exposed an uncomfortable reality: we have built increasingly sophisticated business operations around technology platforms that we don't control. Though there was another important lesson: when the technology fails, communication becomes even more important.
The way organisations respond to disruption can influence stakeholder confidence, customer loyalty and long-term reputation. So while IT teams work to restore services, communicators have a critical role in helping people understand what's happening and what it means for them.
Here are six lessons we’ve got from the incident.
Crisis communication needs to be designed around the audience, not the technical response
One of the most obvious shortcomings in Microsoft's updates was the language being used to explain the outage. Updates referred to improving serviceability, alternate workstreams, traffic management imbalances and the recoverability of frontend servers.
Technically, these descriptions may have been accurate, but accuracy doesn't automatically make communication effective. Most customers weren't interested in the intricacies of Microsoft's infrastructure - they just wanted to know whether their emails were safe, when services would return and what they needed to do in the meantime.
This is a common problem in organisational crisis communication. Technical experts understand the problem, but they aren't necessarily best placed to explain its implications to customers, employees or other stakeholders. This is where strategic communication makes a difference.
Communicators need to be involved early, working alongside technical teams to translate complex information into clear, relevant messages. The objective isn't to simplify the issue to the point of losing accuracy but to make sure people understand what has happened, why it matters to them and what happens next.
A useful approach is to structure messages around three questions:
What? What has happened?
So what? What does this mean for the people affected?
Now what? What should they do, and what can they expect next?
This approach keeps communication focused on the audience rather than the organisation's internal processes.
Credibility matters more than positive messaging
There is considerable pressure on organisations to demonstrate control during a crisis. Leaders want to reassure stakeholders, show that action is being taken and communicate that things are improving; but optimism without evidence can quickly become a reputational liability.
During the Microsoft outage, early updates suggested encouraging recovery progress, with improvements in service availability and email delivery. More than 12 hours later, the language had shifted to describing recovery efforts as achieving marginal success.
The challenge with crisis communication is that situations evolve. Information changes, recovery efforts encounter setbacks and initial assumptions sometimes prove incorrect. Organisations need to communicate that uncertainty without undermining their credibility.
That means distinguishing between confirmed progress, potential solutions and work that is still underway. It also means resisting the temptation to announce good news before the evidence supports it.
Transparency is about being honest about what you know, what you don't know and what you're doing to find out. This requires more than a well-written holding statement. It requires an organisational culture where people can share difficult information without fear of being blamed for delivering bad news.
If internal decision-making is driven by a desire to make everything sound positive, the external communication will eventually reflect that, and stakeholders are generally very good at recognising when they're being managed rather than informed.
Address stakeholder concerns before they become the dominant narrative
When a major service disruption occurs, people don't simply wait for an organisation to explain what has happened - they start forming their own theories.
For a technology company, one of the first questions people might ask during a major outage is whether they've experienced a cyber attack or data breach.Given the number of high-profile security incidents in recent years, this is an understandable concern.
Microsoft addressed the possibility of a cyber attack early in its communications, helping to tackle one of the more significant fears surrounding the incident, which is an important consideration for crisis preparedness.
Scenario planning shouldn't focus exclusively on operational consequences, though. It should also consider the questions, assumptions and fears that different stakeholder groups are likely to have. What will customers be worried about? What will employees want to know? What assumptions might regulators, investors or the media make?
Sometimes, the most important message isn't the technical explanation of what has gone wrong but the information that helps people understand what hasn't happened and what risks have been ruled out. Of course, organisations should never provide reassurance without evidence. If something is still being investigated, say so - but where facts are confirmed, addressing significant stakeholder concerns early can prevent unnecessary speculation and help establish a more informed conversation.
Global organisations need more than a global communication strategy
The Microsoft outage also highlighted the challenges of communicating across different regions and timezones. While the incident was initially reported in the Americas, it was already several hours old when many people in Australia and the Asia-Pacific region woke up to the disruption.
Yet some updates were framed around US business hours, including references to future updates at specific Central Time intervals. For someone sitting in Brisbane, Singapore or London, that isn't particularly helpful.
Global organisations often operate with centralised communication teams and approval processes. This can create consistency, but it can also create delays and messages that don't reflect the needs of local audiences.
A single global update won't necessarily answer the questions being asked in every market. Different regions may experience different operational impacts, have different customer support arrangements and require different information. Effective global crisis communication needs to account for these differences.
That means having regional communication representatives who can support local updates, understanding the information requirements of different markets and making sure communication schedules reflect local working hours. It also means giving regional teams enough authority to respond when central teams aren't available. A global crisis doesn't wait for head office to wake up.
Your supplier's crisis can become your reputational problem
The Microsoft outage is also a reminder that organisations don't operate in isolation. Most businesses rely on an ecosystem of external technology providers, suppliers and service partners. When one of those organisations experiences a failure, the consequences can quickly flow through to everyone depending on them.
From the customer's perspective, it doesn't necessarily matter who caused the problem. If they can't access your service, get an answer to their enquiry or complete a transaction, their experience is with your organisation.
This is particularly important when the disruption affects customer data, essential services or business operations. Organisations need to recognise that third-party incidents are still communication responsibilities.
Waiting for a supplier to provide a complete explanation before communicating with your own stakeholders can leave people feeling ignored and uninformed. Instead, organisations should have holding statements and escalation processes ready for incidents involving external providers.
These should explain what is known, how customers or employees are affected, what the organisation is doing in response and when further information will be provided.
There is also a balance to strike. Being transparent about the source of a problem doesn't mean publicly blaming a supplier or damaging a relationship that is essential to resolving the incident.
The focus should remain on the impact, the response and the actions being taken to restore normal operations. Ultimately, stakeholders are looking for accountability, even when the organisation isn't directly responsible for the original failure.
Business continuity planning must include communication continuity
Perhaps the biggest lesson from the Microsoft outage is the risk of relying too heavily on a single communication platform.
For many organisations, Microsoft is deeply embedded in daily operations. Email, meetings, document management, collaboration and internal communication may all depend on the same technology ecosystem.
When those systems fail, organisations can suddenly lose access to the very channels they rely on to coordinate their response. This is why communication continuity needs to be considered alongside IT disaster recovery and business continuity planning.
Organisations should be able to answer some fairly straightforward questions:
If employees can't access email or Teams, how will you reach them?
If your website is unavailable, where will you publish customer updates?
If your social media accounts are compromised, how will you communicate with the public?
If your primary employee communication platform is offline, where will people find essential information?
The answers might involve SMS, an independent employee communication application, a dedicated staff hotline or a backup website hosted separately from the primary infrastructure.
Organisations need to document who can activate alternative channels, who has access to them and how they will be used. They also need to test those arrangements regularly - a backup channel that nobody knows how to access is not a particularly useful backup. Not to mention if your entire communication ecosystem depends on one technology provider, that dependency needs to be recognised as a business risk, not simply an IT consideration.
Crisis preparedness is ultimately a reputation investment
The Microsoft outage demonstrates how quickly an operational disruption can become a communications and reputation challenge.
Technology failures are inevitable; suppliers will experience outages, systems will become unavailable and organisations will occasionally find themselves dealing with circumstances outside their control. What organisations can control is how prepared they are to respond.
That means having communication plans that extend beyond the immediate incident, understanding stakeholder expectations, establishing alternative channels and ensuring communicators have a seat at the table when decisions are being made. It also means recognising that reputation isn't built or lost in a single incident because trust is accumulated over time through consistent, transparent and thoughtful communication. Every interaction shapes how people perceive an organisation and how much confidence they have in its ability to deliver.
When a crisis occurs, that existing perception becomes particularly important. If stakeholders already trust your organisation, they may be more willing to give you the benefit of the doubt. If you've repeatedly communicated poorly, failed to deliver on promises or left people in the dark, the next incident will only reinforce those perceptions.
The organisations that navigate disruption most effectively aren't necessarily the ones with the most sophisticated technology or the biggest crisis management teams. They're the ones that understand the importance of people, communication and preparation.
The question isn't whether your organisation will experience disruption. It's whether you'll be ready to communicate when it does.
So if you or your organisation need help preparing your crisis communications planning… we can help. Reach out to us here.

