The Microsoft outage exposed a bigger digital workplace problem

Christian Davies, Head of IT & InfoSec, Haiilo
When Microsoft 365 went down last week, the immediate problem was obvious, and all-consuming: people couldn't access the tools they use to work.
But for IT teams, there is a more useful question than simply “what caused the outage?”:
What happens when the entire employee experience depends on the same ecosystem?
Because resilience isn't only about whether your infrastructure comes back online.
It's also about whether you can still reach employees, give them trusted information and tell them what to do when a critical part of that infrastructure is down.
One ecosystem can create one very large blast radius
Most Microsoft environments don't rely on one Microsoft product.
They rely on an interconnected stack:
- SharePoint for content and organizational knowledge
- Teams for collaboration
- Outlook for communication
- Copilot for accessing and working with information
- other Microsoft services sitting underneath or alongside them
That's normally a strength. But tightly connected systems also create dependencies.
During the recent incident, problems weren't confined to a single employee application. Outlook sure, but also Teams, SharePoint, Copilot and other Microsoft services.
That matters when Microsoft isn't just where employees work, but also where you plan to tell employees that Microsoft isn't working.
Your primary communication channel can suddenly be part of the incident you're trying to communicate about.
That's a business continuity problem, not just a productivity problem.
Your crisis comms plan needs to include SaaS failure
IT teams spend every effort designing resilience into infrastructure. The employee communication layer deserves the same thinking.
Ask a simple question:
If Microsoft became unavailable right now, how would we tell every employee what had happened and what they should do next?
If the answer is "Teams", "Outlook" or "our SharePoint intranet", you have a dependency problem.
But the answer isn't abandoning Microsoft or pointlessly duplicating your entire stack. It's designing a communication path that doesn't share every dependency with the systems it needs to report on.
For critical communication, that means thinking explicitly about:
- Channel independence
Can urgent messages reach people outside Microsoft 365? - Audience data.
Can you identify and target the affected employees if your normal directory-connected workflow is degraded? - Mobile access
Can employees receive information without needing their corporate desktop environment? - Publishing ownership
Who is authorized to issue an incident update, and can they do it without IT intervention? - Fallback procedures
Is there an agreed secondary route for business-critical communication? - Testing
Have you actually tested that route during a Microsoft 365 failure scenario?
It's effectively failover thinking applied to employee communication.
The outage also exposed a knowledge dependency
There is another issue that IT teams need to consider – and fast. Because AI is quickly becoming part of that same dependency chain.
Employees expect Copilot to provide answers using organizational information. But Copilot still depends on the information, permissions and services available to it.
That changes the architecture of the digital workplace.
A disruption isn't just:
Service unavailable = employee can't open application
It also becomes:
Service unavailable = information unavailable = AI unavailable = employee can't get answers
And even when everything is available, AI doesn't remove the underlying requirement for current, authoritative and governed knowledge. Missing, duplicated, outdated or contradictory information remains a knowledge problem rather than an AI problem.
💡 See also: How to Avoid the Looming AI Knowledge Crisis
For IT, resilience therefore needs to cover both access to systems and access to trusted organizational knowledge.
Don't rip out Microsoft. Reduce the dependency.
This is where the distinction matters.
Microsoft 365 remains an extremely powerful foundation for productivity, collaboration, content, security and AI. The argument isn't that organizations should replace it.
The lesson from an outage like this is simpler:
Avoid making one technology ecosystem your only route to employees.
Haiilo , for example, sits across Microsoft 365 and the wider workplace technology stack, connecting communication, knowledge, tools and AI in one employee experience.
That means organizations can think about the employee layer separately from the applications underneath it.
Not another replacement productivity suite. Not a parallel version of Microsoft. A layer designed around how employees receive information, access trusted knowledge and navigate the systems they already use.
That's consistent with Haiilo's broader approach: make Microsoft 365 work better rather than attempting to replace it.
💡 See also: How to Make Microsoft a Better Intranet
Five questions IT should ask before the next outage
You don't need another 40-page resilience framework.
Start here:
- If Microsoft 365 is unavailable, can we still reach every employee?
- Do critical comms have a channel that doesn't share the same failure domain?
- Can employees still access essential company information and instructions?
- Are critical knowledge sources clearly owned, current and authoritative?
- Have we tested all of this in a real outage scenario?
If any answer is "not sure", the outage has already given you your next resilience exercise – because no platform is going to achieve 100% availability forever.
The important question is what happens to your employees when yours doesn't.
Interested in how Haiilo can keep your employee experience resilient for you and your employees? Book a call with one of our experts.
.png)
Here's what everyone should know before using M365 as their intranet...
Find
your
flow
Bring communication, knowledge, and tools into one calm place — and help your people find their flow.


