Microsoft 365 outage: what it teaches us about email resilience

19/11/26 Wavenet
Microsoft 365 outage: what it teaches us about email resilience

When a core cloud platform is disrupted, customers still expect answers, suppliers still need decisions and employees still need a reliable way to communicate. The Microsoft 365 outage on 12 and 13 November was a timely reminder that availability and resilience aren't the same thing. 

On the afternoon of Thursday 12 November, Microsoft 365 suffered a disruption that hit Exchange Online hardest, with knock-on effects in Teams, SharePoint and Copilot. Users struggled to access mailboxes and send or receive email, and Microsoft’s preliminary post-incident report puts the disruption at almost 24 hours, running into Friday 13 November.

For many organisations, the technical details were less important than the operational reality. A customer waiting for an answer didn’t see a service-health dashboard. A supplier awaiting approval didn’t know which part of the infrastructure had failed. They simply knew they hadn’t heard back.

That’s why this incident matters beyond the outage itself. It raises a bigger question for every organisation. If a critical platform becomes unavailable, can your business keep communicating?

When cloud services stop, business expectations don't

Email remains central to the formal side of business. Contracts, approvals, customer responses, supplier instructions, notifications and confirmations all depend on it. When access is interrupted, the effect quickly reaches beyond the inbox.

Work stalls, decisions wait, support teams take more calls and commercial opportunities sit in outboxes. People may try to move conversations onto other channels, but those alternatives don’t always provide the access, control or established processes that business email supports.

That turns an IT incident into a business continuity issue, measured in delayed responses, uncertainty and a reduced ability to keep serving customers.

Reliability isn't the same as resilience

Microsoft 365 is a highly reliable platform. Its everyday reliability is also one reason organisations can become comfortable depending on it. When a service works almost all the time, preparing for the exceptional day can slip down the priority list.

Resilience starts from a different assumption: even reliable services can be disrupted, so the organisation should understand its dependencies and prepare an alternative route for its most important activities.

The wider lesson also reflects UK government guidance on operational resilience. The Government has highlighted the risk created by significant reliance on specific suppliers, describing these dependencies as potential “single points of failure”. This doesn’t mean replacing a strategic platform or treating every supplier as a risk to be removed. It means understanding where a provider represents a critical operational dependency and having a plan for how the business will respond if that service becomes temporarily unavailable. 

Single-vendor dependency is a business decision

For email, architecture can determine the outcome of an outage. If mail routing, mailbox access, authentication and security all depend on the same unavailable platform, employees may have no practical fallback when that platform is disrupted.

Microsoft’s own post-incident report shows why this matters. According to Microsoft MVP Tony Redmond’s analysis, mailbox data held up during the November outage. The weak point was the infrastructure that accepts and routes connections, which is exactly the part of the journey an independent mail path is designed to work around.

Some organisations add protection through APIs that inspect messages and support post-delivery action. Those capabilities can strengthen security, but API-based protection alone doesn’t create an independent path for sending and receiving email when Exchange Online cannot be reached.

Email continuity requires a prepared alternative. That includes a separate mail path, a supported way for users to access email, suitable authentication arrangements and an agreed process for activation and recovery. These foundations need to be designed, configured and tested before an outage, rather than assembled during one.

What independent email continuity can change

With an appropriate gateway deployment and continuity service in place, administrators can activate an alternative email route for all users or a defined group. Employees can continue sending, receiving, reading and replying through supported applications while relevant security and content controls remain in place.

Once the primary platform recovers, the organisation can follow its agreed recovery process, restore and test normal delivery, end the continuity event and reconcile messages according to the applications and configuration in use.

Technology is only one part of this response. Employees need to know where to go, administrators need clear responsibilities and authentication must stay available. The business also needs to understand which communications are most critical and how continuity fits into its wider incident plan.

Resilience comes from the combination of technology, preparation, access and rehearsed responsibilities that keeps the business moving. You can’t switch it on during a crisis.

Questions every organisation should ask now

The best time to review continuity is while the lessons from an outage are still clear. Business and technology leaders should be able to answer the following questions:

  • Where do our email MX records point? Do they provide an independent mail path, or does the entire environment depend on the primary platform?
  • How would employees access email during an outage? Is there a supported, configured method that doesn’t rely on the unavailable service?
  • Can users authenticate independently? An alternative email service is only useful if people can sign in when the primary identity route is affected.
  • Who activates continuity and who communicates the decision? Responsibilities should be documented and understood before an incident.
  • Have we tested the process? Configuration, user access and recovery steps should be validated under realistic conditions.
  • How does email continuity connect to the wider business-continuity plan? Priority teams, customer communications and critical processes should be considered together.

Build the alternative before you need it

November’s outage didn’t change the importance of Microsoft 365. They highlighted the risk of allowing one platform to become the only route through which the business can communicate.

A resilient approach keeps the primary platform at the centre of day-to-day work while preparing an independent option for disruption. It combines the right architecture with practical preparation, clear ownership and tested access.

We can help you review your current email environment, understand where single-vendor dependencies exist and explore an email continuity approach powered by Mimecast. We can’t promise disruption will never happen, but we can make sure your people know what to do, and have somewhere to go, when it does.

Book an email continuity discussion to map your email dependencies, identify priority users and agree a controlled test plan.