Yesterday, something remarkably simple became remarkably difficult for organisations around the world: sending an email.
A major Microsoft 365 outage that began on 12 November affected Outlook, Teams, Copilot and other connected services across multiple regions. At the peak, almost 130000 Outlook problems were reported through Downdetector, alongside tens of thousands of Microsoft 365 reports. Microsoft responded by redirecting traffic, restarting infrastructure and rolling back changes as it worked to restore services.
The disruption stretched into a second day. Governments, businesses and healthcare organisations experienced problems accessing email and other services. Even integrations from AI providers such as OpenAI and Anthropic were affected because they depended on Microsoft infrastructure.
There is an important detail here. Microsoft said it had no evidence that the incident resulted from malicious activity. Reports based on Microsoft’s incident information pointed instead to infrastructure capacity problems and an overloaded process responsible for establishing secure connections, while engineers also rolled back a recent network configuration change.
That distinction matters. Because sometimes we learn more about cybersecurity and resilience from something that is not a cyberattack. The outage exposed something that normally remains almost invisible: the extraordinary concentration of our digital working lives.
Think about a typical working day. Email runs through Outlook. Meetings happen in Teams. Documents live in SharePoint or OneDrive. An increasing number of employees interact with Copilot. Identity, collaboration, communication and increasingly AI can all exist within the same ecosystem. When everything works, this integration is enormously convenient.
When part of that ecosystem fails, however, we suddenly discover all the invisible dependencies we have created. That is the bigger lesson from this outage.
For years, digital transformation has largely been presented as a story about efficiency. Move infrastructure to the cloud. Connect systems. Automate processes. Integrate communication. Add AI. Each step makes sense individually. Together, however, they can create concentration risk. An organisation may have hundreds of applications, thousands of devices and multiple communication channels while still depending on a surprisingly small number of underlying technology providers. Diversity at the interface does not necessarily mean diversity underneath.
AI makes this question even more interesting. We are currently racing to put AI assistants into almost every professional workflow. They can search our documents, summarise meetings, process email, prepare presentations and answer questions using organisational knowledge. But those capabilities do not exist in isolation. An AI assistant depends on identity services, cloud infrastructure, APIs, enterprise data, communication platforms and access controls. When one important layer disappears, capabilities elsewhere can disappear with it. During this outage, problems with Microsoft infrastructure were even felt in integrations offered by OpenAI and Anthropic.
The lesson, therefore, is not that we should stop using Microsoft 365, move everything out of the cloud or avoid AI. That would be the wrong conclusion. The lesson is that digital maturity cannot be measured only by how much technology we have adopted. It must also be measured by how well we can function when that technology is temporarily unavailable.
Cybersecurity professionals have used the concept of resilience for years. We create backups because storage can fail. We introduce redundancy because infrastructure can fail. We prepare incident-response plans because security controls can fail. Perhaps we need to apply the same thinking more broadly to the digital workplace.
If email disappears tomorrow morning, what happens? Can colleagues still communicate? Can students contact their lecturers? Can customers reach the organisation? Do employees know where they should look for status information if the system normally used to distribute that information is itself unavailable? And perhaps most importantly: have we ever actually tested any of this?
Those questions are particularly relevant for education.
Universities and colleges are becoming deeply digital organisations. Learning platforms, authentication, communication, documents, assessment, AI assistants and administrative processes increasingly depend on interconnected cloud services.
We teach students and employees how to use these systems, but digital literacy should perhaps include something else: understanding dependency.
Future professionals need to recognise that digital infrastructure is infrastructure. It can fail. Providers can experience outages. Connections can disappear. Automated processes can stop. AI assistants can suddenly become unavailable. Knowing what to do next is also a digital skill.
There is a parallel here with cybersecurity awareness. We have spent years teaching people what to do when they receive a suspicious email. Perhaps resilience education should also teach people what to do when there is no email at all.
None of this makes cloud computing, Microsoft 365 or AI a bad idea. The productivity and collaboration benefits are enormous. But mature technology adoption requires us to acknowledge the trade-off between integration and dependency. The more tightly connected our digital environments become, the more deliberately we must think about continuity.
Yesterday’s outage will eventually become another entry in a service-history log. Systems will recover, inboxes will fill again, Teams meetings will resume and most people will quickly forget about it. Organisations should not. Because the most valuable question after an outage is not simply:
“When will the service be back?”
It is:
“What did we discover we can no longer do without it?”
That is where the real conversation begins.

