In June 2017, following the WannaCry cyberattack that disrupted hospitals and healthcare services across England's NHS, Dr. Joe McDonald wrote an article for Digital Health asking a fairly simple question: where was our Bat Signal?
Joe's point wasn't just about the technology that had failed. It was about how healthcare organizations communicated when the systems they relied upon suddenly weren't available. Who did we contact, how did we reach one another, and did we actually have a plan that worked when our usual communications didn't?
Almost a decade later, the Microsoft 365 outage that began on Thursday, November 12, and ran into Friday, November 13, 2026, brought those questions back into focus.
I happened to be at a healthcare digital leadership conference on the Friday, surrounded by senior digital leaders from across Yorkshire, the Humber and the North of England. As the disruption unfolded, it was interesting to see how quickly conversations shifted. Suddenly, there was a rather noticeable increase in interest in what I do for a living.
Discussions that might ordinarily have centered on AI, digital transformation or the latest technology developments turned toward something more fundamental: how do we communicate when the platforms we've become so dependent upon aren't working?
I spent much of the day discussing what alternatives existed, what could continue operating independently and the role that established voice infrastructure still plays. Later that Friday evening, I found myself having a similar conversation with Paul Ginn, Senior Director, Product & Solutions Marketing at Mitel. We were approaching the issue from different perspectives, mine from the operational realities of healthcare and Paul's from the wider communications industry, but kept returning to the same point. We've made enormous progress in how we connect people, but have we given enough thought to what happens when those connections aren't available?
When everything is connected, everything can be affected
Over the past decade, we've understandably worked toward bringing more of our communications together. Email, instant messaging, meetings, telephony and collaboration increasingly sit within common platforms. It's convenient, familiar and, for the most part, works incredibly well.
But the more we consolidate, the more we potentially concentrate our dependencies. When several critical communications capabilities rely on the same underlying platform, identity service or infrastructure, a single failure can have consequences well beyond the original technology.
An email outage, for example, isn't necessarily just an email outage. In healthcare, many organizations rely on Microsoft 365 services within wider operational workflows, including automated notifications, patient appointment communications and integrations with other systems.
For some, this extends to email and SMS appointment reminders, where the process responsible for generating or delivering a message depends on Microsoft-hosted services or gateways. The SMS provider itself might be working perfectly well, but if the system responsible for passing the message to it has failed, the outcome is much the same. The patient doesn't receive the information they were expecting.
The same dependencies can affect incident coordination, internal alerts and communication between organizations. Even where individual applications remain operational, the processes connecting them may not.
We spend considerable time discussing the resilience of clinical systems, and rightly so. But the communications surrounding those systems deserve just as much attention.
Voice never stopped being critical
There's something revealing about what happens when modern digital communications become unavailable. People reach for the telephone.
For all the progress we've made, voice remains one of the most immediate and familiar ways of reaching someone. Within hospitals, it continues to underpin an extraordinary amount of everyday activity, from patient inquiries and clinical escalation to operational coordination and emergency response.
During a major incident, the ability to establish a telephone conference, contact clinical areas or initiate an emergency communications cascade becomes particularly important. These aren't especially glamorous capabilities, but they're essential to keeping organizations functioning when other systems are unavailable.
This is where on-premises and hybrid voice environments can offer something valuable. Where designed appropriately, core calling and conferencing capabilities can continue operating independently of cloud collaboration platforms experiencing disruption.
That's not to suggest on-premises technology is automatically more reliable than cloud, or that traditional telephone systems never fail. Both approaches have vulnerabilities, and both can be designed with considerable resilience. A telephone system dependent on a single network connection, power supply or external service is still vulnerable, regardless of where its core infrastructure sits.
The important distinction is understanding what depends on what, and making deliberate decisions about where those dependencies should exist. Resilience isn't necessarily about where something is hosted. It's about what continues working when something else doesn't.
Have we confused modernization with resilience?
We talk a great deal about digital transformation in healthcare. Cloud adoption, AI, automation and integrated platforms all have an important role to play. But I sometimes wonder whether, in our enthusiasm to modernize, we've become a little too quick to regard certain technologies as yesterday's problem.
Telephony is a good example. It's often treated as something to maintain until the next transformation program replaces it, rather than recognized as a strategic capability in its own right.



