PARIS — For most of the past decade, a European customer asking for a sovereign cloud got a geography lesson. Here is the region, here is the data center, the data stays inside the border.
Microsoft Corp. now argues that the question was never about a single border. At an event in Paris on Tuesday, the company said customers should be able to decide, workload by workload, how much control they want and where the computing happens, choosing among its public cloud, systems they run themselves and facilities operated by partners.
The shift is a departure from the packaged approach that cloud providers have sold since the Schrems II ruling in 2020 threw out the transatlantic data transfer arrangement and sent European regulators, banks and health agencies looking for ways to keep data out of American hands. Most of the industry’s answer was to build a separate region and promise that support staff in the United States would not touch it.
Douglas Phillips, president and chief technology officer of Microsoft Specialized Clouds, wrote in a blog post that business-critical applications should not be forced into rigid, one-size-fits-all models. He said customers wanted control and choice over their most sensitive workloads, rather than a single template applied to everything they run.
Microsoft attached three pieces of machinery to that argument. The first is a Sovereign Control Panel, a view inside the Azure portal that is meant to show administrators how much control they actually hold over a given workload, where the gaps are, and what happens to operations if a region or a supplier becomes unavailable.
The second concerns administrative access, which is where sovereignty claims usually break down. Microsoft is rolling out a “data guardian” role and a tamper-proof, auditable log it calls the Production Touch Ledger, which records every remote administrative session and every action its own engineers take on customer production systems. A customer who cannot see who touched the database has not bought sovereignty, whatever the contract says.
The third is cryptography. External key management with Azure Managed HSM is now generally available, which lets customers keep physical control of their root keys rather than holding them inside Microsoft’s infrastructure. The company pointed as well to confidential computing and hardware-isolated clean rooms, where data is protected while it is being processed, not just while it sits on disk.
None of this makes the choice simple. Each workload now carries its own decision about which of three deployment models it needs, and the models differ in cost, latency and the features available. A bank running a payments ledger and a bank running a marketing analytics job do not need the same answer, and the person who has to give both answers is usually a chief information security officer with a fixed budget.
The commercial logic is easier to see from Microsoft’s side. European governments and regulated industries have spent three years writing rules that make American hyperscalers expensive to use for sensitive systems. France’s SecNumCloud certification, Germany’s C5 catalogue and the European Union’s cloud services scheme all attach conditions to who may operate infrastructure and under which law. Losing those workloads to OVHcloud, SAP’s Delos Cloud or the Bleu joint venture backed by Orange and Capgemini would cost Microsoft more than offering them a hybrid.
So the company is trying to move the argument from legal jurisdiction to engineering configuration. If a customer can run sensitive applications on hardware it controls, with keys it holds, under an audit trail it can read, then the question of which country’s law governs the vendor becomes one factor among several rather than a disqualification.
Auditors may not accept that framing. The CLOUD Act gives American authorities reach over data held by American companies, and a configuration does not change the corporate relationship. A regulator reviewing a customer-operated deployment will ask who supplies the patches, who holds the recovery keys in an emergency, and whether the arrangement survives a contract termination. The answers tend to be less clean than a slide.
There is a practical risk as well: complexity. Modular offerings are harder to sell, harder to audit and easier to misconfigure. Microsoft’s own control panel is an admission that customers cannot tell, from the outside, how sovereign their setup is.
The event was part of a tour the company has run through European capitals this year, with Chief Executive Satya Nadella appearing alongside Phillips. Microsoft does not disclose revenue from sovereign offerings, which makes the strategy difficult to grade. What can be graded is the direction: after years of selling a product defined by location, the company is now selling one defined by permissions.
European buyers have heard promises about data residency before, and several have been burned by clauses discovered after signature. The new controls are testable in a way the old promises were not, which is the strongest thing that can be said for them. Whether customers trust the tests is a different matter, and one they will settle in procurement, one workload at a time.
