BRK439 Breakout Tue 17 Nov 15:15 PST
Sovereign cloud mythbusters: Separating fact from fiction
Rick Claus, Pierre Roman
Summary
From the recording / Microsoft AI summary
Sovereignty was presented as a set of workload controls rather than one product: data residency, key ownership, operational control and compliance. Three models were described: sovereign public cloud on Azure, sovereign private cloud on Azure Local (connected or disconnected), and national partner clouds such as Bleu and Delos.
Session description
Microsoft's catalogue description
Does digital sovereignty require a local cloud provider? Is disconnected always more secure? Does data residency alone address sovereignty requirements? Join Microsoft experts as we separate fact from fiction and examine the real-world tradeoffs behind sovereignty, AI governance, resilience, data protection, and cloud operations. Through practical examples and customer scenarios, you'll gain a framework for evaluating requirements and making informed cloud and AI decisions.
Demo timestamps
Microsoft's player does not support links to a specific time, so open the recording and skip to the time shown.
- Skip to 0:15:50
Residency and key control through Azure Policy
Shows a policy denying any deployment outside West US, and policies requiring customer-managed keys in an HSM the customer controls, which can be on-premises.
- Skip to 0:29:51
Enabling Customer Lockbox
Checks the support plan, assigns the Customer Lockbox approver role to a named person with a time limit, and enables Lockbox on the demo subscription so Microsoft support needs explicit approval for access.