There is no price for “Microsoft Sovereign Cloud”, because it is not a single product. Under that name, formerly Microsoft Cloud for Sovereignty, Microsoft groups three deployment models and a set of controls: Sovereign Public Cloud in existing Azure regions, Sovereign Private Cloud on Azure Local in customer- or partner-operated datacentres, and National Partner Clouds run by local partners such as Bleu or Delos Cloud.
A cost review therefore starts from the control you actually need, and only then from price. Start from prices and you can easily end up comparing a standard Azure region with a private or partner-run architecture built for a different requirement, a different operating model and often a different contracting party.
Where things stand on 10 October 2026
Since the first announcement, the main changes are in naming and in how mature individual controls are. These are the points that matter for a cost decision:
| Topic | Current position according to Microsoft | Cost relevance |
|---|---|---|
| Sovereign Public Cloud | Existing Azure regions plus controls; EU and EFTA datacentres add the EU Data Boundary and Data Guardian | Consumption-based Azure, billed through your existing subscriptions |
| Data Guardian | Remote access by Microsoft personnel is approved and monitored by Europe-resident staff and logged in a tamper-evident ledger | No separate cost item in the sources; check support processes and response paths |
| Key control | Azure Key Vault Managed HSM is the default route; External Key Management with keys held outside Azure is a preview that Microsoft describes as a last resort for hard legal or contractual mandates | HSM pool, partner HSM, proxy operation and availability risk |
| Sovereign Control Panel | New name for Regulated Environment Management; one view of sovereignty posture built from Azure Policy and resource configuration | Less manual evidence work, where your controls are represented there |
| Sovereign Private Cloud | Azure Local, Microsoft 365 Local, GitHub Enterprise Local and Foundry Local on Azure Local; disconnected operation of Azure Local and Microsoft 365 Local available worldwide since 24 February 2026 | Hardware, site, people and a fee per physical processor core |
| National Partner Clouds | Bleu (France, Orange and Capgemini) and Delos Cloud (Germany, an SAP subsidiary); service scope and rollout vary by country | A different contracting party, its own prices and its own billing data |
Three models, three cost questions
| Deployment model | Boundary described by Microsoft | Cost question |
|---|---|---|
| Sovereign Public Cloud | Microsoft-operated datacentres inside a defined geopolitical boundary such as the EU Data Boundary | Which additional controls and services must be enabled, and how do they change architecture, operations and support? |
| Sovereign Private Cloud | Customer- or partner-operated environment on Azure Local, connected, hybrid or disconnected | Which hardware, site, people, lifecycle and capacity costs move to the organisation? |
| National Partner Cloud | A locally operated instance with an approved national partner under national law | Which services, prices, contracting entities and operating duties apply in the specific country? |
Microsoft's overview documentation is where model selection begins. For National Partner Clouds, Microsoft points explicitly to each implementation's service matrix, and in every model you still need a quote for the configuration you intend to run.
Do not equate the EU Data Boundary with complete isolation
The EU Data Boundary covers EU and EFTA countries. For included enterprise online services, Microsoft commits to storing and processing Customer Data and personal data inside the boundary, and to storing Professional Services Data at rest there. For UK organisations this matters directly: the United Kingdom is in neither the EU nor EFTA, so UK regions sit outside the boundary.
The commitment comes with configuration conditions and documented exceptions. For Azure, regional services are in scope only when deployed to an EU Data Boundary region; non-regional services need configuring one by one, and Professional Services Data requires Azure Resource Manager to be set to the EU Data Boundary. Microsoft also keeps a record of continuing transfers, split into temporary and ongoing partial transfers, optional capabilities and excluded services.
What that means for the cost model:
- Do not treat “EU Data Boundary” as a blanket SKU; it is a configuration and contract question.
- Review data type, region, non-regional services and exceptions per workload.
- Price only the controls and architecture changes the actual requirement needs, such as replacing an excluded service.
- Keep legal assessment and technical configuration under separate accountable owners.
Map each control to a cost line
Before a supplier quote goes into the business case, map each control to the cost it creates:
| Required control | Technical evidence | Possible cost effect | Owner |
|---|---|---|---|
| Data residency | Approved region and configuration of non-regional services | Regional rate, data movement, constrained service choice | Architecture |
| Operator access | Data Guardian logs and an approved support path | Support model, process and response path | Security |
| Key control | Managed HSM, or External Key Management (preview) | HSM pool, external HSM, proxy operation, recovery | Security and platform |
| Isolated operation | Public, private or partner target | Hardware, capacity, people and lifecycle | Platform and finance |
| Assurance | Sovereign Control Panel, policies and review process | Storage, analysis and control operation | Compliance |
If a cost line cannot be traced to a control, question whether it belongs. If a control has no technical evidence behind it, it has not been implemented yet and the business case should not count it. A preview feature such as External Key Management goes into the table with its status, because Microsoft says aspects of it may change before general availability.
Azure Local: what the Azure bill shows and what it does not
Microsoft says Azure Local appears on the Azure subscription bill like any other Azure service. It is charged at a flat rate per physical processor core, regardless of how many virtual machines run. Microsoft distinguishes three tiers: L1 for hyperconverged deployments with local storage, L2 for disaggregated deployments with external storage or multiple racks, and L3 for disconnected operations with a locally hosted control plane. According to Microsoft's FAQ, Azure commitments and Enterprise Agreement discounts apply to Azure Local.
Three details matter for the cost model:
- Core counts are reported to Azure, and the system must connect at least once every 30 days for billing.
- From solution version 2504 onwards, if a cluster is shut down without deleting the Azure Local resource in Azure, billing continues until the resource has been disconnected for more than 31 days.
- Guest operating systems may need their own licences, which the core fee does not include.
What is not on the Azure bill still belongs in the comparison:
- hardware and refresh cycle;
- reserved capacity and unused headroom;
- datacentre, energy and networking;
- platform operations, updates and on-call cover;
- backup, recovery and separate test environments;
- licensing, Marketplace products and support;
- audit evidence and ongoing control operation.
Hold functional scope, risk basis and evaluation period constant. Setting on-demand public-cloud prices against fully utilised private capacity produces a number, but not one that helps anyone decide.
National Partner Clouds: a different contracting party
Bleu and Delos Cloud deliver Azure and Microsoft 365 capabilities, but they are operated by local companies under national law, physically and logically isolated. For cost work that makes them a new provider: a separate contract, price list, invoice and cost data. Before comparing, establish which services the country's service matrix includes, what cost data the operator provides, and whether your existing Azure discounts play any part there.
Select the Azure cost dataset for the question
The 2026-06-01 Exports API lists, among others, the ActualCost, AmortizedCost, FocusCost and PriceSheet types, delivered as CSV or Parquet. Each answers a different question:
- Actual Cost: an invoice-oriented view of accrued usage and purchases.
- Amortized Cost: spreads reservation and savings plan purchases across the periods and usage receiving the benefit.
- FOCUS Cost: standardised analysis using shared FinOps semantics, where the required fields and scope are covered.
- Price Sheet: the billing account's price list, useful as a dated price source.
Record scope, currency, cost type, export version and retrieval date in the review. Do not join Actual and Amortized Cost into one trend without exposing the method change. A UK team reporting in GBP should also record which currency each export is in before any conversion.
A defensible review in six steps
- Record the requirement and its decision owner.
- Select the matching deployment model: public, private or partner.
- Confirm regions, services, exceptions, preview status and required controls.
- Capture the complete target architecture, including operations, support and hardware.
- Separate recurring cost, one-off delivery and residual commitments.
- Test the cost export and monthly reconciliation before approval.
What you end up with is not a verdict on whether Microsoft Sovereign Cloud is “more expensive”. It is a decision someone can audit: which model meets a named requirement, and what that particular model costs in your organisation. The same review for AWS's separate partition is in AWS European Sovereign Cloud: the cost questions before a migration, and the cost of a later provider switch in EU Data Act: plan cloud switching costs before 2027.
What Costfluent covers
Costfluent reads Azure cost details for every subscription you assign, through a service principal with two read roles, as the Azure integration page describes. Sovereign Public Cloud workloads run in Azure regions and are billed through those subscriptions, so they appear in the same cost reports, budgets and allocation rules as the rest of your Azure usage. The same applies to the Azure Local fee where it is billed to an assigned subscription.
The hardware, energy and staff of a private cloud are on no Azure bill and therefore not in that data. National Partner Clouds are separate operators and not a Costfluent connection. Where Costfluent itself is based and how it reaches your cloud are set out on the digital sovereignty page.
Sources and method
Checked on 2026-10-10. Microsoft's What is Microsoft Sovereign Cloud?, What is Sovereign Public Cloud, Capabilities of Sovereign Public Cloud, Data Guardian, External Key Management, Sovereign Control Panel, National Partner Clouds, Azure Local billing and payment, the 24 February 2026 announcement, the EU Data Boundary, continuing transfers and the Cost Management Exports API.
Microsoft sources describe product models and commitments. The tables and sequences are Costfluent recommendations; whether a model satisfies a specific regulatory or contractual requirement is for the responsible organisation to determine legally and technically.



