On Thursday 12 November 2026, at 8:17 p.m. UAE time, Exchange Online went into issues. As I write this on Friday evening, MS Outlook, Teams, SharePoint, Copilot and parts of Defender XDR have been disrupted for more than 20 hours, and recovery is still uneven.
This is not a post about Microsoft failing. Every major cloud platform has its bad days. AWS, Google, and Cloudflare have all experienced outages that affected millions of users. This is a simple blog post about my thoughts on concentration, our growing dependence on handful of SaaS platforms. Three out of four of the world’s largest companies run on a single productivity platform. Three out of four of the world’s largest companies rely on Microsoft 365. Email, meetings, files, AI assistants, and increasingly security operations all sit within the same ecosystem.
It works brilliantly when everything is running. But when something goes wrong, the impact reaches far beyond. It affects how entire organizations communicate, collaborate, operate, and respond to incidents. And here is the thing – cloud outages are not going away. Just like our winters are a season, not an anomaly.
More than 20 hours later, recovery remained uneven across regions, with Microsoft still working to stabilise services and clear delayed email queues. Microsoft has so far stated no evidence of malicious activity and has committed to publishing a full Post-Incident Report once mitigation is complete. We will wait for that.
I see two important lessons emerging from this outage:
For enterprise leaders : What should we rethink about our cloud dependency, and how do we prepare for the next outage rather than simply hope it doesn’t happen?
For SaaS providers : How does a platform spread across hundreds of datacenters still end up with a single point of failure? And more importantly, what does it take to design systems that can withstand?
How can a cloud platform spread across hundreds of datacenters still experience a failure that affects services across the globe? Many datacenters. Few points of control.
Geographic redundancy and huge scale do not automatically mean architectural independence. Microsoft operates hundreds of datacenters, but they rely on shared systems and services to coordinate how the wider platform operates. Consider four key dependencies here –
Identity : Shared authentication services connecting users and applications.
Traffic management : Global load balancing and health checks deciding where traffic goes.
Change pipelines : Configuration and software deployments that can affect multiple regions.
Service dependencies :Teams, Copilot, Safe Links, Purview and parts of Defender have dependencies and integrations with other Microsoft services, including Exchange Online.
The public updates from this incident point to a possible cascading failure,. Microsoft reported elevated load, servers failing automated health checks, an overwhelmed core process, and restored servers becoming quickly unavailable again.
Consider how this cycle can develop: (1) Servers slow down under increased traffic. (2) Health checks mark them unhealthy and remove them from service. (3) Traffic shifts to fewer servers, which become overloaded in turn. (4) Engineers restore capacity, but simultaneous client retries create another surge, overwhelming recovering servers.
The recovery process starts amplifying the original failure. A mechanism designed to protect the platform, such as automated health checks, can end up making the situation worse. Interestingly, one of Microsoft’s early mitigation steps was to bring some servers back using an alternative health-check method. Breaking this cycle requires controlled traffic redistribution, limits on automated server removal, and retry budgets to prevent recovering infrastructure from being overwhelmed. The cloud did not eliminate single points of failure. It moved them up a layer above, from hardware we can see to shared systems and control mechanisms we often cannot.
For enterprises – plan for the season; What must change in our thinking
Cloud concentration is a board-level risk, not just an IT issue. An SLA credit compensates you after an outage. It does not keep your sales team selling, your contact centre answering, or your employees working. We need to start asking a different question.
Stop asking: “What is our uptime?” Start asking: “What is our Minimum Viable Operation if our primary platform is unavailable for 24 hours?” Many organizations may have discovered this week that they have never properly answered that question. AI makes this dependency even deeper. Copilot and agentic workflows increasingly sit on the same platforms as the email, files and data they depend on. When those platforms fail, automation can fail alongside the people relying on it. The more AI we embed into our operations, the more critical it becomes to understand the blast radius. Security is part of this equation too. Defender XDR was among the affected services. Major outages also create opportunities for attackers. Expect phishing campaigns disguised as Microsoft outage notifications, asking users to verify their accounts or restore access. Losing security visibility during an outage is more than an availability problem. It can become a security problem.
How to act, starting Monday
A few practical steps every enterprise should consider
> Define your Minimum Viable Operation. Identify the five business processes that must continue during a 24-hour outage. Map the people, data and tools each one needs.
> Establish out-of-band communications. Have a crisis communication channel on a different platform, ideally with an independent identity provider. Test it regularly.
> Keep security visibility independent. Stream critical logs to a SIEM or data platform you control. Your SOC should not go blind because your primary security console is unavailable.
> Build identity break-glass access. Maintain emergency administrative access that does not depend entirely on the identity infrastructure affected by the outage.
> Make data accessible during an outage. Back up mail, files and calendars independently. More importantly, make sure people can actually access and use that data while the primary platform is unavailable.
> Run “SaaS winter” exercises. Simulate a two-hour outage of your primary platform. Watch what breaks, who loses access and which business processes stop. A plan that has never been tested is a hope, not a plan.
> Make resilience part of procurement. Before renewing contracts, ask vendors about failure isolation, blast-radius limits, change management, recovery processes and post-incident reporting. Get the answers in writing.
For SaaS providers – untangle the architecture
A few architectural principles can help turn the next global outage into a much more contained incident.
> Pods, not one big service. Partition customers and workloads into independent pods, each with its own capacity and dependencies. A failure shouldn’t affect all of customers, not the entire platform. AWS has publicly documented this architectural approach.
> Keep the data plane working when the control plane fails. Critical services should continue operating where possible, even when central management systems are unavailable. Users should still be able to access cached data and perform essential tasks.
> Graceful degradation over complete failure. Read-only access, delayed synchronization and offline capabilities are far better than making everything unavailable.
> Make recovery deliberate. Build admission control, load shedding and retry budgets into the architecture. Restore capacity gradually and distribute traffic carefully. Recovery should not trigger another collapse.
> Ensure health checks cannot bring down the platform. Limit how much capacity automated systems can remove at once. When too many servers suddenly fail the same health check, the health check itself may be part of the problem.
Communicate clearly and honestly. Clear status updates help organizations decide when to activate their own continuity plans and when it is safe to resume normal operations.
Build for Winter, Not Just the Storm
Microsoft will recover. Services will return, backlogs will clear and a Post-Incident Report will eventually explain what went wrong. But the bigger question is not whether Microsoft can recover. It is whether the businesses depending on it can keep operating while it does. This is not just a Microsoft problem. It is a cloud dependency problem that we all are facing, and it applies to every provider that becomes central to how we work.
For enterprises, resilience means knowing what happens when your primary platform is unavailable, and having a tested way to keep the business running.
For SaaS providers, it means designing systems where failures stay contained, and recovery does not create another failure, and one weak point does not bring down an entire ecosystem.
Keeping a service available is very important. But true resilience is about ensuring the business can continue when that service is unavailable. Isn’t it?
That distinction matters more than ever now.
Perhaps the most useful next step is a simple one, before the end of this month, run a simple exercise. Treat your primary SaaS platform as unavailable. Test your communications, access to critical data, security visibility and essential business processes. That should get us started towards more resilient tomorrow.
– Murali Konasani











