The hyperscalers' sovereign offerings are products that confine data, operations and administrative access to Europe, either as a separate environment with its own accounts or as additional controls on the standard cloud. For the bill, that shape matters more than the label. A separate environment comes with its own price list, its own accounts, its own billing data and possibly its own invoice, while controls on the standard cloud run at the familiar prices plus whatever the controls themselves cost. Anyone weighing a European sovereign cloud therefore compares the shape of the offering first and the prices second.

How it works

The three providers use one word for very different products, described here as each provider names them today.

AWS

AWS describes the AWS European Sovereign Cloud as physically and logically separate from its other Regions, with an independent billing system. Its first Region is in Germany. Existing AWS accounts cannot be used there: a customer creates a new account, and AWS states that these accounts are not interoperable with other Regions. The first Region is operated by companies established under German law with AWS European Sovereign Cloud GmbH as their parent, by personnel who are EU residents located in the EU, and AWS describes a transition to operation exclusively by EU citizens. According to the FAQ, the contracting entity is Amazon Web Services EMEA SARL in Luxembourg. Billing, invoices and the cost management tools work in euro. AWS publishes separate pricing pages for the AWS European Sovereign Cloud, offers Private Pricing to eligible customers and sells Compute and machine learning Savings Plans there. Its user guide lists the available services, each with its significant differences from the other Regions.

Azure

Microsoft groups its offerings as Microsoft Sovereign Cloud, formerly Microsoft Cloud for Sovereignty, and distinguishes three deployment models. Sovereign Public Cloud runs in Microsoft's existing Azure regions within defined boundaries such as the EU Data Boundary and adds controls on top: customer-managed keys, confidential computing, Data Guardian and a Sovereign Landing Zone with policy as code. Sovereign Private Cloud runs on Azure Local in datacentres the customer or a partner operates, connected to Azure or fully disconnected. National Partner Clouds are operated by a national partner independently of Microsoft's own operations, and Microsoft restricts them to eligible customers in a few countries, such as Germany and France.

Google Cloud

Google Cloud Data Boundary sets data residency and access controls inside the public cloud: core customer data stays in the chosen region, administrative access is logged and bound to conditions the customer defines, and keys can be held externally. Google Cloud Dedicated is dedicated, isolated infrastructure with independent operations by a national partner. Google Distributed Cloud brings Google Cloud into the customer's own facilities, either connected or air-gapped.

What it means for your cost

The cost question follows the shape. Controls on the standard cloud leave the price list alone: for Sovereign Public Cloud, Microsoft states that you pay standard Azure prices and that added cost comes from the services, SKUs or regions you choose to get the controls you need, such as confidential computing or customer-managed keys. Microsoft also notes that its pricing calculator may not cover the sovereignty controls completely. A separate environment, by contrast, changes almost everything a cost report takes for granted:

  • Its own price list. The AWS European Sovereign Cloud has its own pricing pages and Private Pricing. For National Partner Clouds, Microsoft says the partner sets pricing, service availability and support. Sovereign Private Cloud adds hardware, licences and the work of running it as new kinds of cost.
  • Separate accounts, separate data. New AWS accounts in an independent billing system mean separate billing data and a separate invoice in euro. The billing documentation lists features that are missing there: the legacy Cost and Usage Report, several CUR 2.0 features including split cost allocation data and billing views, the CSV download on the Bills page, and AWS Billing Conductor.
  • Fewer services and regions. A service that does not exist in the target environment has no price there, and an architecture that depends on it has to change.
  • Commitments. In the AWS European Sovereign Cloud, group sharing of Savings Plans and Reserved Instances is not available. Because the accounts are not interoperable with other Regions, it follows that commitments bought in existing accounts do not cover usage there.
  • Data transfer. Data moving between the separate and the standard environment leaves one and enters the other. AWS lists data transfer in as free and data transfer out as tiered; which rate applies is set by each side's price list.

A comparison therefore only works service by service, with the provider's own price list for the target environment and only for services that actually exist there. A flat percentage premium says nothing about a specific bill. The questions to settle before a move are laid out in AWS European Sovereign Cloud: the cost questions before a migration, and the comparison on the Microsoft side in Microsoft Sovereign Cloud: compare controls and cost correctly.

Where it goes wrong

  • Standard prices assumed. The estimate uses the prices of a familiar region although the separate environment has its own price list. The first invoice differs with no change in usage.
  • Every service assumed. The architecture relies on a service or feature that is missing or implemented differently in the target environment. The replacement costs something else, found only during the migration.
  • Commitments in the wrong environment. A Savings Plan or reservation is bought in an existing account while the workload runs in the new AWS European Sovereign Cloud accounts. The commitment goes unused and the new usage is billed at on-demand rates.
  • Two invoices nobody joins. Separate accounts deliver separate billing data, often in a different currency from the existing estate. Without a combined view, part of the cost is missing from reports and budgets.
  • A label read as a legal status. An offering's name is a product name, not a legal classification. Microsoft itself states that the customer decides which controls apply, configures them and keeps the evidence. Whether an offering meets a requirement is for your legal adviser and auditor to decide.

Example

Google publishes a Free and a Premium tier for Assured Workloads, read on 2026-10-15. The EU Data Boundary control package carries no additional charge. The EU Data Boundary and Support and EU Data Boundary with Access Justifications packages carry 5% on all Google Cloud service usage expenditure within the folder, shown as a separate line under the Assured Workloads SKU.

Sources

Read on 2026-10-15. AWS European Sovereign Cloud FAQ, AWS European Sovereign Cloud pricing, AWS Billing and Cost Management in the European Sovereign Cloud, AWS Services in the European Sovereign Cloud, Microsoft What is Microsoft Sovereign Cloud?, Microsoft Cloud Adoption Framework: digital sovereignty adoption, Google Google's sovereign offerings, Google Assured Workloads pricing.