EU regulators, works councils, and increasingly cautious public-sector buyers have spent the past few years pushing the big three US hyperscalers toward a specific promise: your data, and ideally your cloud operations, stay inside the EU/EEA, governed by EU law, run by EU-based staff. Each of AWS, Google Cloud, and Microsoft has answered differently, on a different timeline, and — as of 2026 — with meaningfully different degrees of “done.” This piece separates what’s actually live today from what’s still a roadmap item.
AT A GLANCE
| Offering | Status as of 2026 | Scope | Key detail |
|---|---|---|---|
| AWS European Sovereign Cloud | Generally available — launched January 15, 2026 | New, physically/logically separate AWS partition; first Region in Brandenburg, Germany | Operated exclusively by EU residents, with independent EU governance entities; no critical dependency on non-EU AWS infrastructure; >90 services at launch; Local Zones planned for Belgium, Netherlands, Portugal |
| Google Cloud EU Data Boundary / sovereign controls | Partially live — rolled out incrementally via Assured Workloads since 2021, still expanding | Per-workload controls layered onto existing Google Cloud regions, not a separate partition | EU-only data residency (5+ EU regions), cryptographic Key Access Justifications, and EU-based support; relies partly on third-party sovereign partners (e.g. T-Systems, Thales) for full operational sovereignty |
| Microsoft EU Data Boundary for the Microsoft Cloud | Completed — final phase finished February 26, 2025 | Existing Microsoft 365, Dynamics 365, Power Platform, and most Azure services, EU/EFTA-wide | Customer data, pseudonymized personal data, and technical-support data now stored/processed in EU/EFTA; limited exceptions remain for coordinated global security response |
Short Verdict
These three offerings are not apples-to-apples. Microsoft’s EU Data Boundary is the most mature as a data residency commitment layered on its existing cloud — it’s been rolling out since 2023 and Microsoft says it completed the final phase in February 2025. AWS has gone furthest on operational sovereignty — a new, separate cloud partition with its own EU-resident leadership and governance structure, but it only reached general availability in January 2026 and currently has just one live region. Google Cloud’s approach is the most incremental and partner-dependent: real, usable controls (data residency, cryptographic access justifications, EU support) have existed in some form since 2021, but full “operational sovereignty” explicitly leans on third-party partners like T-Systems and Thales rather than being delivered end-to-end by Google alone.
What “Sovereign Cloud” Actually Means — Three Different Things
Vendors and analysts use “sovereignty” loosely, but it generally decomposes into three distinct guarantees, which matters because each vendor delivers a different mix:
- Data residency: Data at rest (and ideally in processing) stays within a defined geographic/legal boundary.
- Data sovereignty: Cryptographic and policy controls over who can access data and under what legal authority — e.g., blocking or requiring justification for provider-side access tied to non-EU legal requests.
- Operational sovereignty: The infrastructure and the people running it — including during outages, legal disputes, or geopolitical disruption — are themselves EU-based and independent of the parent company’s non-EU operations.
AWS European Sovereign Cloud: A Separate, EU-Only Partition
AWS took the most structurally aggressive approach: rather than adding controls to existing regions, it stood up a new, physically and logically separate cloud partition, which reached general availability on January 15, 2026. Per AWS’s own announcement, the new partition has no critical dependencies on infrastructure outside the EU and is designed to keep operating even during a connectivity disruption with the rest of AWS’s global network. It is governed through a dedicated parent company and three German GmbH subsidiaries, led by EU citizens, with an advisory board made up of EU citizens/residents; day-to-day operations and all personnel with access to the infrastructure and customer data are EU residents. The first Region launched in Brandenburg, Germany, with more than 90 services available at launch, and AWS has committed to investing over €7.8 billion in Germany, supporting an estimated 2,800 full-time-equivalent jobs annually. Sovereign AWS Local Zones in Belgium, the Netherlands, and Portugal are planned to extend coverage, though AWS hasn’t published a firm timeline for those. This is the only one of the three offerings that is a genuinely distinct cloud, not an overlay of controls on an existing one.
Google Cloud: Per-Workload Controls, Built Incrementally
Google’s approach runs through Assured Workloads and its EU Data Boundary control package, applied per workload rather than as a separate region or partition. Its current official documentation describes an EU-only resource location constraint restricting workloads to EU regions (including europe-west1, europe-west3, europe-west4, and europe-north1), a minimum TLS version restriction, and a restricted service list so only vetted products/API endpoints are usable inside the boundary — with the most granular restrictions and exceptions documented for BigQuery. The underlying capabilities trace back to Google’s 2021 announcement of sovereign controls for EU customers: EU-only data residency across several regions, Key Access Justifications (cryptographic visibility into, and the ability to deny, each data-access request, tied to Cloud External Key Manager), and EU-based customer support. Google has been explicit that these controls do not by themselves deliver full independent operational sovereignty — for that, it points customers to partner-delivered sovereign offerings such as T-Systems (Germany) and Thales (France), which add independent oversight on top of Google’s technical controls. In other words, Google’s sovereignty story is real but composite: Google provides the technical primitives, and a local partner often provides the operational independence layer.
Microsoft: The Most Complete Data-Residency Rollout
Microsoft’s EU Data Boundary for the Microsoft Cloud is a phased commitment to keep customer data within the EU/EFTA for its core cloud services — Microsoft 365, Dynamics 365, Power Platform, and most Azure services — rather than a new separate cloud. Per Microsoft’s own announcement, the rollout happened in three phases: Phase 1 (January 2023) covered core-service customer data; Phase 2 (January 2024) added pseudonymized personal data; and Phase 3, which Microsoft says completed the boundary, finished in February 2025, adding professional-services/technical-support data (such as support logs and case notes) to the in-region requirement. Microsoft notes that for certain Azure services, customers may need to take additional configuration steps to get the full professional-services data-storage commitment, and that in limited security situations requiring a coordinated global response, some data may still be transferred outside the boundary, with encryption and strict access controls applied. Microsoft frames this alongside its separate Microsoft 365 Advanced Data Residency add-on and its broader Microsoft Cloud for Sovereignty program, which adds policy and operational controls on top of the data boundary for customers who need them.
Comparison: What’s Actually Guaranteed
| Guarantee | AWS European Sovereign Cloud | Google Cloud (EU Data Boundary / Assured Workloads) | Microsoft EU Data Boundary |
|---|---|---|---|
| Data residency | Yes — new EU-only partition | Yes — per-workload EU region restriction | Yes — EU/EFTA, phased, now covering support data too |
| Cryptographic access control | Native to the separate partition | Yes — Key Access Justifications + external key management | Not the primary mechanism; relies on EU Data Boundary + encryption/access controls |
| EU-resident operations staff | Yes, by design (new legal entities, EU citizens only) | Partial — relies on partners (T-Systems, Thales) for full independence | Not structurally separate; Microsoft’s global org still operates the service |
| Independent from parent company’s non-EU infra | Yes — explicitly no critical non-EU dependencies | No — same global Google Cloud infrastructure, EU-scoped | No — same global Microsoft Cloud infrastructure, EU-scoped |
Pros and Cons
AWS European Sovereign Cloud
- Pros: Strongest operational-independence story of the three; purpose-built legal/governance structure; large committed investment.
- Cons: Brand new (GA only since January 2026) — single region, limited service catalog relative to AWS’s full global footprint, and planned Local Zones aren’t live yet.
Google Cloud EU Data Boundary / Sovereign Controls
- Pros: Flexible, per-workload controls usable across existing EU regions today; strong cryptographic access-justification tooling; partner ecosystem for full sovereignty where needed.
- Cons: Not a fully independent operational entity on its own — true operational sovereignty requires a third-party partner layer; service coverage inside the EU Data Boundary control package is uneven (some products/features explicitly unsupported).
Microsoft EU Data Boundary
- Pros: Broadest, most mature phased rollout; covers Microsoft 365, Dynamics 365, Power Platform, and most Azure services; now includes support/technical data, not just customer data.
- Cons: Not an operationally independent entity — same global Microsoft infrastructure and staff, just data-residency-scoped; limited exceptions remain for global security response; some Azure services need extra customer configuration for full coverage.
Who Each Is a Good Fit For
Organizations with the strictest regulatory or political requirements — public-sector bodies, defense-adjacent entities, or enterprises in heavily regulated sectors demanding provable EU-only operations — are the target for AWS’s new sovereign partition, accepting its current single-region limitation as a trade-off. Enterprises already standardized on Google Cloud that need EU data residency and strong cryptographic access controls, and are willing to pair Google’s technical controls with a sovereign partner (T-Systems, Thales) for full independence, fit Google’s model well. Organizations whose primary exposure is Microsoft 365/Dynamics/Azure workloads and whose main regulatory concern is “where is our data stored and processed” rather than “who operates the infrastructure” are well served by Microsoft’s now-completed EU Data Boundary.
Bottom Line
All three vendors can now credibly claim EU data residency. Only AWS currently offers a genuinely separate, independently operated EU cloud partition — and it’s brand new, with a single region and a growing-but-still-limited service catalog. Microsoft’s EU Data Boundary is the most completed data-residency commitment of the three, having finished its final rollout phase in February 2025, but it doesn’t change who operates the underlying global infrastructure. Google’s controls are flexible and technically strong but explicitly depend on third-party partners for full operational independence. “Which is more sovereign” depends entirely on which of the three guarantees — residency, cryptographic sovereignty, or operational independence — matters most for your specific regulatory requirement.
FAQ
Is the AWS European Sovereign Cloud available everywhere in the EU?
No. As of its January 2026 general availability, it has one live Region, in Brandenburg, Germany, with more than 90 services. Sovereign Local Zones in Belgium, the Netherlands, and Portugal are planned but not yet confirmed as live.
Has Microsoft’s EU Data Boundary fully rolled out?
Microsoft says its three-phase rollout completed in February 2025, covering customer data, pseudonymized personal data, and technical-support data for core services across the EU/EFTA, with narrow exceptions for coordinated global security incidents.
Does Google Cloud offer a fully independent sovereign cloud like AWS’s?
Not entirely on its own. Google’s EU Data Boundary/Assured Workloads controls deliver strong data residency and cryptographic access controls, but Google has said that full operational sovereignty depends on partnering with local providers like T-Systems or Thales.
What’s the difference between data residency and operational sovereignty?
Data residency means your data physically stays within a region. Operational sovereignty means the infrastructure, personnel, and governance running that cloud are themselves independent of the parent company’s non-EU operations — a much higher bar that only AWS’s new partition currently targets directly.
Which offering should an EU public-sector buyer evaluate first?
It depends on the specific regulatory requirement, but if the requirement explicitly demands independent EU operation (not just EU data storage), AWS’s European Sovereign Cloud and Google’s partner-backed sovereign offerings (via T-Systems/Thales) are the closest match; if the requirement is primarily data-location-based and the workload is Microsoft 365/Azure-centric, Microsoft’s completed EU Data Boundary may already satisfy it.
Sources
- AWS Launches AWS European Sovereign Cloud and Announces Expansion Across Europe — Amazon press release
- Microsoft Completes Landmark EU Data Boundary — Microsoft official blog
- EU Data Boundary control package — Google Cloud official documentation
- New sovereign controls for EU customers — Google Cloud blog
