Zscalerのブログ
Zscalerの最新ブログ情報を受信
The Microsoft 365 Outage Is A Wake-Up Call to Prioritize Business Continuity
Yesterday’s Microsoft 365 and Exchange Online outage impacted 430+ million users across 74 countries for 18+ hours, making it likely the biggest one to hit enterprises since the Crowdstrike outage of 2024. Like other recent disruptions to hyperscalers and major SaaS providers, it serves as a wake-up call for enterprises. When a critical, highly relied-upon cloud dependency goes dark, can your business continue to operate?
.png)
Zscaler Digital Experience (ZDX) showing downtime of Outlook Online
This outage offers important lessons for our resilience strategy:
Lesson #1: Identify & Prioritize Your Mission-Critical Services and Ensure You Have a Business Continuity Plan
Not all enterprise systems are created equal. If your HR portal goes offline for an hour, it’s an inconvenience, but the business survives. You can live with a standard 99.9% availability SLA for non-critical systems.
Critical systems are different. They require 99.999% resilience, however mission-critical systems must have a 100% availability through business continuity/disaster recovery strategy, as any minute of downtime can cost the business millions and reputational damage. Research from Oxford Economics puts the total cost of unplanned downtime for Global 2000 companies at $400 billion annually — $540,000 per hour.
Regulators agree. Under DORA, CPS 230, and ISO 22301, “Our cloud provider went down,” is no longer an acceptable defense. Enterprises must prove operational resilience across every critical dependency.
This is why CIOs are building toward a minimum viable IT stack — the three services that every organization needs to maintain during any disruption:
- Identity services
- Zero trust connectivity services
- Business-critical applications
Together, these three form the complete resilience chain. Miss any one, and your business will be disrupted.
Lesson #2: Don’t Take Shortcuts With Cloud Services
In the "good old days" of mainframe computing and corporate data centers, IBM and IT leaders had strict separation between their active production data centers and physically isolated backup data centers. If an unforeseen issue or outage occurred at the primary site, customers switched over to the disaster recovery data center in minutes, allowing business to carry on.
In the cloud era, we must maintain these same principles rather than relying purely on high-availability SLAs. The biggest and best platforms in the world still have disruptions. An architecturally independent business continuity cloud follows the same principles as the separate data center infrastructure, and provides insurance against cloud outages to maintain uptime and business productivity.
Lesson #3: Don’t Buy Your Applications and Security From the Same Place
Under massive suite licensing agreements, enterprises have increasingly consolidated their productivity, collaboration, and security tools under a single provider and hosted them on connected architecture, leading to increased risk.
Microsoft Defender for Office 365 and critical Microsoft security services, such as Intune and Purview were also impacted yesterday due to the weave of infrastructure interdependencies underlying Microsoft’s services.
Using security services that rely on your application infrastructure to function is the digital equivalent of letting the fox watch the hen house.
We cannot control when a major cloud provider or critical infrastructure dependency will fail. But we can control how our systems respond. Enterprises should look for a dedicated business continuity cloud for each of their mission critical services. By decoupling your zero trust security from your application layer and establishing true architectural independence with the Zscaler Business Continuity Cloud, you ensure your business remains resilient, compliant, and unstoppable—no matter what.
Hear Zscaler senior leadership explain how the Business Continuity Cloud delivers architectural independence — and why customers are deploying it now. Watch the webinar →
このブログは役に立ちましたか?
免責事項:このブログは、Zscalerが情報提供のみを目的として作成したものであり、「現状のまま」提供されています。記載された内容の正確性、完全性、信頼性については一切保証されません。Zscalerは、ブログ内の情報の誤りや欠如、またはその情報に基づいて行われるいかなる行為に関して一切の責任を負いません。また、ブログ内でリンクされているサードパーティーのWebサイトおよびリソースは、利便性のみを目的として提供されており、その内容や運用についても一切の責任を負いません。すべての内容は予告なく変更される場合があります。このブログにアクセスすることで、これらの条件に同意し、情報の確認および使用は自己責任で行うことを理解したものとみなされます。




