Technology makes business easier, but when one system goes down, how much of your organisation can still function? Over the last
Technology makes business easier, but when one system goes down, how much of your organisation can still function?
Over the last couple of days, I have received several SMS messages from corporate contacts explaining why they have been unable to respond to emails in a timely manner. The reason? The Microsoft outage.
I also know of people whose daily work depends almost entirely on Microsoft’s platforms. With the disruption, some have found themselves unable to access their emails, documents and other work tools.
It got me thinking about how much modern businesses have come to depend on technology, and more importantly, how prepared they are when that technology becomes unavailable.
The recent Microsoft disruption affected Outlook, Teams, Copilot and other Microsoft 365 services, leaving businesses and institutions across different countries struggling to maintain normal operations.
It raises a question every business should be asking:
If the system you depend on today became unavailable tomorrow, would your business still operate?
Convenience can create vulnerability
There is no doubt that cloud-based systems have transformed how we work.
We can access emails remotely, collaborate on documents, hold virtual meetings and store information without maintaining physical servers in our offices.
For many organisations, this has made operations more efficient and reduced the need for extensive IT infrastructure.
But somewhere along the way, convenience has also created dependency.
We have businesses whose entire communication systems run through one email provider. Employees whose work documents exist only in one cloud environment. Teams that cannot coordinate without a particular collaboration platform.
When everything works, this arrangement feels perfectly reasonable.
Until it doesn’t.
The problem is not that businesses are using technology. It is that many have not adequately prepared for the possibility of losing access to it.
Your Plan B must be independent
Take email communication, for instance.
Most organisations use Outlook as their primary communication platform. But what happens when employees cannot access their Microsoft 365 accounts?
One option worth considering is maintaining an alternative, official communication channel.
For example, an organisation could have a secondary Gmail account or another independently hosted email service that can be activated during an outage.
This should be properly managed, secured and communicated to relevant employees, clients and suppliers.
There is, however, an important distinction: accessing Outlook through a web browser is not necessarily a backup. If the underlying Exchange Online service is unavailable, both the desktop application and webmail may be affected.
The alternative needs to be independent of the infrastructure that has failed.
The objective is not to abandon your primary system. It is to ensure that a disruption does not completely cut you off from your customers and stakeholders.
Don’t let your data hold your business hostage
The other issue is data.
Many organisations have moved almost everything online. Documents, reports, contracts, financial records, operational schedules and customer information are stored in cloud environments.
While cloud storage is useful, businesses should not confuse accessibility with resilience.
What happens when employees cannot access those files?
Can the finance department retrieve the information it needs to continue critical processes? Can the operations team access deployment schedules? Can management retrieve essential reports?
Businesses should consider maintaining independent backups of critical information.
This could include secure offline copies, scheduled backups to a separate environment and controlled local access to essential operational documents.
The important thing is to avoid having all your information dependent on one service or one access point.
And having backups is not enough. Organisations should periodically test whether they can actually retrieve and restore their information.
Business continuity is everyone’s responsibility
I think this is where many organisations need to change their thinking.
Business continuity is often treated as an IT department responsibility.
But the consequences of a system failure go far beyond IT.
Sales teams may be unable to respond to enquiries. Finance teams may struggle to process payments. Operations teams may lose access to schedules. Customer service teams may be unable to retrieve customer information.
Every department needs to understand what it should do when its primary systems are unavailable.
That means having alternative communication channels, documented procedures, clear responsibilities and access to essential information.
It also means periodically testing these arrangements rather than waiting for an actual outage to discover that they don’t work.
Don’t wait for the next outage
Here are a few practical questions every organisation should consider:
These are not necessarily expensive interventions. Some require little more than planning, discipline and a deliberate investment in redundancy.
Technology should enable business, not stop it
The Microsoft outage is a useful reminder that even established technology providers can experience disruptions.
No organisation should assume that because it uses a reputable provider, it is immune to service interruptions.
The goal is not to maintain a duplicate of every system or spend unnecessarily on technology.
It is to identify what your business cannot afford to lose access to, and prepare accordingly.
A business that can only function when everything is working perfectly is a business with an operational vulnerability.
So, as organisations continue to digitise their operations, perhaps the question should not only be which systems make us more efficient.
It should also be which arrangements will keep us operational when those systems fail.
Have a Plan A that makes your business efficient. Have a Plan B that keeps it running.