7 Min Read
When one of the world's largest technology providers experiences an outage, the effects can be felt across thousands of organisations and millions of users.
A recent disruption to Microsoft's services, including Outlook, Teams and other Microsoft 365 applications, is a timely reminder of just how dependent modern businesses have become on cloud-based technology.
The outage, reported on 12 November 2026 (US time), affected access to Exchange Online mailboxes and a range of Microsoft 365 services. Microsoft attributed the connectivity problems to infrastructure issues, with a number of servers unexpectedly becoming unavailable and placing additional load on the remaining systems.
While Microsoft worked to restore services, the incident highlighted an important consideration for organisations of all sizes: what happens to your business when a technology provider you rely on experiences an outage?
The reality is that no technology platform is entirely immune to disruption. The bigger question isn't whether an outage will happen, but whether your business is prepared when it does.
Cloud outages happen. Is your business prepared?
Cloud computing has transformed the way organisations operate, providing access to scalable infrastructure, applications and services without the need to manage everything themselves.
However, as businesses increasingly move critical operations into cloud environments, their reliance on technology providers and interconnected services also grows.
An interruption to email or collaboration tools might seem relatively minor, but when those systems underpin customer communications, internal operations, financial processes and decision-making, the business impact can quickly escalate.
For organisations running critical applications and databases in the cloud, an infrastructure disruption can have even wider implications.
This is why cloud strategy needs to consider more than performance, scalability and cost. Resilience and business continuity need to be part of the conversation from the outset.
Why relying on a single provider can create risk
Many organisations have consolidated their technology environments around a small number of major providers. While this can simplify management and deliver efficiencies, it can also create dependencies that are not always fully understood.
A disruption affecting one provider or platform can potentially impact multiple business functions at once.
This doesn't mean organisations should avoid major cloud providers. Rather, it highlights the importance of understanding where dependencies exist and how critical services would be maintained if one part of the technology environment became unavailable.
A well-considered cloud strategy should account for:
- Infrastructure redundancy: Are critical workloads supported by appropriate backup infrastructure or alternative environments?
- Disaster recovery: How quickly can systems and data be restored following an interruption?
- Business continuity: Can essential business functions continue while technology services are unavailable?
- Provider dependencies: Does the organisation understand its reliance on individual providers, platforms and underlying infrastructure?
- Recovery testing: Have backup and recovery processes been tested to ensure they will work when needed?
Having a backup is one thing. Knowing that you can successfully recover from a disruption is another.
What does a resilient cloud environment look like?
Cloud resilience isn't achieved through a single solution. It requires a combination of appropriate infrastructure, planning, security and ongoing management.
For some organisations, this might involve maintaining a separate disaster recovery environment for critical workloads. For others, a hybrid or multicloud architecture may provide the flexibility and separation needed to manage risk.
Key considerations include:
1. Understand your critical workloads
Identify which applications, systems and data are essential to business operations. Not every workload requires the same level of protection, so recovery priorities should reflect the potential business impact of an interruption.
2. Establish clear recovery objectives
Recovery Time Objectives (RTO) define how quickly a system needs to be restored, while Recovery Point Objectives (RPO) establish how much data loss, measured in time, an organisation can tolerate.
These objectives help determine the appropriate backup, replication and disaster recovery arrangements.
3. Build appropriate backup and recovery environments
Critical workloads may require separate backup locations, replicated infrastructure or dedicated disaster recovery environments. The right approach depends on the organisation's operational requirements, risk profile and budget.
4. Test your recovery arrangements
A disaster recovery plan is only useful if it works. Regular testing helps identify gaps, validate recovery processes and give organisations greater confidence that they can restore critical services when required.
5. Review your provider and data dependencies
Understand where your infrastructure and data reside, which providers are involved and what happens if a particular service or environment becomes unavailable.
Why cloud resilience matters for New Zealand organisations
For New Zealand businesses and government organisations, cloud decisions involve additional considerations around data residency, sovereignty, security and operational control.
As more critical services and sensitive information move into cloud environments, organisations need confidence not only in the technology itself, but also in where their data is hosted and how the underlying infrastructure is governed.
A sovereign cloud approach provides an opportunity to maintain greater control over the location and governance of data, while accessing the scalability and capabilities of modern cloud infrastructure.
At TEAM Cloud, we provide a New Zealand-owned and operated sovereign cloud, powered by Oracle Cloud Infrastructure (OCI).
Our focus is on helping New Zealand organisations access enterprise-grade cloud infrastructure while addressing the local requirements that matter, including data residency, security, governance and control.
Sovereignty and resilience are different considerations, but both deserve a place in a well-planned cloud strategy.
Is it time to review your cloud strategy?
The recent Microsoft disruption is another reminder that even the largest global technology providers can experience service interruptions.
Rather than viewing cloud outages as isolated technical incidents, organisations should use them as an opportunity to review their own technology dependencies and preparedness.
Are your critical systems protected? Do you know how quickly they could be recovered? Have you tested your disaster recovery arrangements? And do you have the right level of visibility and control over your cloud environment?
Cloud technology should give businesses the confidence to operate, adapt and grow. Building resilience into that environment is an essential part of achieving this.
At TEAM Cloud, we believe a good cloud strategy should deliver more than performance and cost efficiencies. It should give organisations confidence in the security, control and resilience of the infrastructure supporting their business.
If you're reviewing your organisation's cloud strategy or want to better understand your infrastructure and disaster recovery options, we'd be happy to have a conversation.
Talk to TEAM Cloud about building a more resilient cloud environment.