# Microsoft Sovereign Cloud Core Customer Scenarios: Business Continuity ## Метаданные - **Канал:** Microsoft Azure - **YouTube:** https://www.youtube.com/watch?v=zQHKnpsutZU ## Содержание ### [0:00](https://www.youtube.com/watch?v=zQHKnpsutZU) Segment 1 (00:00 - 05:00) (bright music) (bright music continues) - We will now focus on a sovereignty scenario that has become especially important in a world shaped by geopolitical uncertainty, cyber risk, and operational dependence on digital infrastructure, business continuity. For many customers across public sector and regulated industries, resilience and business continuity of their systemically important workloads and IT systems are critical, as their core business processes rely on the availability of these systems. Furthermore, in the financial services industry, regulatory frameworks require resilience, but also to have concrete and tested exit plans ready in case necessary. So customers require protection from disruptive events, technical failures, or cybersecurity threats. But business continuity, when tied to sovereignty concerns, also entails autonomy, resilience, and business continuity in case of any forced suspension or disruption of operations in or from the cloud service provider, or in case cloud regions become disconnected from other regions. The questions from those cases go beyond whether systems stay online, but they ask for continuity in disconnected or even air-gapped scenarios. These concerns are exactly why the business continuity sovereignty scenario exists. Now let me bring this to life with a real world example. Imagine a national healthcare provider serving millions of citizens every single day. They depend on digital systems for everything, electronic health records, medical imaging, emergency dispatch, pharmacy coordination, and real-time data exchange between hospitals. Now, picture a sudden geopolitical crisis or a major fiber cut that interrupts international connectivity. Overnight, this healthcare system becomes partially isolated from global networks, but the work doesn't stop. Doctors still need access to patient records. Ambulances still need to be routed. Local systems must keep running. Medical supplies must continue to move, and data exchange still must continue in real time. All of this, while operating offline or in a severely restricted connectivity environment. In moments like these, continuity is no longer a nice-to-have. This is a classic business continuity sovereignty trigger. The organization must be able to operate mission critical workloads on cloud infrastructure that is highly available, resilient, and under local control. And for the most critical functions, it must continue to operate even when cloud connectivity may be disrupted or constrained. We've established how this scenario arises in a live setting. Now let's discuss how Microsoft defines business continuity. So in Microsoft's sovereignty model, business continuity refers to customer needs where national resilience, operational independence, and failsafe access to critical services are required, even during disconnected, degraded, or high-risk scenarios. And these needs are specifically common for public safety agencies, national healthcare systems, defense, intelligence, utilities, and critical infrastructure, of course, the financial services industry, and emergency management. The scenario focuses on enabling workloads to withstand failures or technical disruptions in cloud IT infrastructure, but also connectivity loss or regional segregation requirements, national emergencies, and cyber incidents. And finally, the scenario also evaluates regulatory obligations for in-country failover and long-duration isolation periods. It's sovereignty through resilience and operational independence. So how does Microsoft's Sovereign Cloud enable this level of resilience? First, it is important to emphasize that a major benefit from hyperscale public clouds is that it provides built-in capabilities to enable high availability and business continuity, multiple geographies spanning local regions with multiple data centers, support availability zones, and advanced workload replication scenarios. That is also why Microsoft adds sovereign controls in its scalable public cloud, providing resilience and high availability without the need to migrate to less resilient, segmented sovereign cloud solutions. But we also understand and appreciate that customers need solutions for highly critical or sensitive workloads ### [5:00](https://www.youtube.com/watch?v=zQHKnpsutZU&t=300s) Segment 2 (05:00 - 10:00) or need resiliency scenarios in case of disruptive events or unlikely, but critical, doomsday scenarios. In those cases, customers need resilience and contingency options with no or less dependence of public cloud, even though that may come against the cost of lower scalability and a reduced cybersecurity posture. We have designed a comprehensive set of capabilities that support continuity in both online and disconnected states. So let's go a bit deeper through these options. First, let's talk about disconnected and semi-connected operations. Azure Local allows mission critical workloads to run inside a customer's data center, ensuring continued operation even during full disconnection. Combined with Azure Arc, customers get consistent management, policy enforcement, and application modernization while retaining local execution independence. Microsoft is investing significantly in its local solutions. Azure Local can scale to many nodes per cluster, can run fully air-gapped over multiple zones, and it enables AI innovation as it supports local GPUs, and can run a subset of Microsoft Foundry's over-1,900 AI models. For organizations that require an isolated cloud environment that can operate independently of the public cloud, the Sovereign Private Cloud model provides that fully controlled in-country cloud environments designed to withstand disconnection while maintaining operational continuity. Sovereign Private Cloud leverages Azure Local and Microsoft 365 Local. Through that Sovereign Private Cloud, many essential services, communication, collaboration, emergency response workflows can be maintained inside country borders through Microsoft 365 Local-Azure Local deployment patterns. Microsoft 365 Local runs Exchange, SharePoint, and Skype for Business Server for which we extended support to at least 2035. Now, in some countries, such as France and Germany, there may be even more stringent requirements for public sector or critical infrastructure entities, such as providing services under full national control. Microsoft enables access to national partner clouds under its Sovereign Partner ecosystem, operated by domestic entities for eligible customers to address those specific digital jurisdictional sovereignty requirements. These clouds ensure continuity under national oversight even when external networks or cross-border connections are disrupted. In addition to the Sovereign Cloud deployment models, Microsoft delivers reference architectures and sovereign landing zones designed to help customers architect resilient, compliant, and even air-gapped workloads. Customers can design for country-level failover, fully isolated backup regions, local emergency only mode, or tiered resilience for critical workloads. Furthermore, customers can build reversible architectures on top of Microsoft Azure, which can easily migrate to on-premises Azure Local environments. Microsoft supports and is a platinum member of the CNCF, the Cloud Native Computing Foundation, which seeks to drive adoption of the paradigm to build and run scalable applications in modern, dynamic environments, such as public, private, and hybrid clouds. Business continuity is more than technology, its trust. And it requires continued investment as trust is not a one-off campaign, but an everyday discipline. So to summarize our approach for the business continuity scenario, first, we've gained valuable experience as a company with national resilience programs. We've partnered with governments and regulated industries globally to design sovereign architectures that withstand crisis conditions. So then we offer those unique, demonstrable flexibility in deployment models, Public Sovereign Cloud, Private Cloud, air-gapped options, and our Sovereign Partner ecosystem all supported on a unified platform. We also built a proven track record with mission critical workloads in health, finance, defense, and public safety, where workloads already run on Microsoft Cloud today. And then we integrate security and resilience into the platform, not bolted on, but integrated end-to-end. And of course, we help to drive continuous innovation. Microsoft is continually expanding capabilities for disconnected operations, local processing, and resilient AI, helping customers stay prepared for the unexpected. To close out and summarize with what we've discussed ### [10:00](https://www.youtube.com/watch?v=zQHKnpsutZU&t=600s) Segment 3 (10:00 - 10:00) the business continuity scenario is all about ensuring that critical or systemically important services can operate, even when networks fail, regions disconnect, or geopolitical risks emerge. With Azure's built-in resiliency, business continuity, and disaster recovery options, Azure Local Sovereign Private Cloud, Microsoft 365 Local, and Sovereign Partner Ecosystem, and resilient sovereign architectures, Microsoft helps customers remain operational when it matters most. Thanks for joining us. Up next, explore the next video in our series on sovereign scenarios. (bright music) --- *Источник: https://ekstraktznaniy.ru/video/44723*