If you go looking for the price of “Microsoft Sovereign Cloud”, you will not find one, because in 2026 it is not a single Azure product. Microsoft describes several deployment models: Sovereign Public Cloud in Microsoft-operated datacentres, Sovereign Private Cloud on Azure Local in customer-controlled infrastructure, and National Partner Clouds operated with regional partners.
That is why a cost review has to start from the control you actually need. Start from prices instead, and you can easily end up comparing a standard Azure Region with a private or partner-run architecture that was built for a different requirement and runs on a different operating model.
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, including hybrid or disconnected scenarios | Which hardware, site, people, lifecycle, and capacity costs move to the organisation? |
| National Partner Cloud | Local implementation with an approved national or regional partner; scope and rollout vary | Which services, prices, contracting entities, and operating duties apply in the specific country? |
Microsoft's Sovereign Cloud documentation is where model selection begins. You will still need the service matrix and 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 specified Customer Data and personal data inside the boundary, and to storing Professional Services Data at rest there.
That commitment comes with configuration conditions and documented exceptions. For Azure, regional services must be deployed to an in-scope EU Data Boundary Region, while non-regional services need the applicable configuration. Microsoft also maintains a current record of continuing transfers outside the boundary.
What that means for the cost model:
- Do not treat “EU Data Boundary” as a blanket SKU.
- Review the data type, Region, non-regional services, and exceptions per workload.
- Price only controls and architecture changes required for the actual decision.
- 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 service configuration | Regional rate, data movement, constrained service choice | Architecture |
| Operator access | Approved operations and support path | Support model, process, and response path | Security |
| Key control | Selected key-management model | HSM, key operations, availability, and recovery | Security and platform |
| Isolated operation | Public, private, or partner target | Hardware, capacity, people, and lifecycle | Platform and finance |
| Assurance | Logs, 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.
Compare public cloud and Azure Local on total operating scope
Sovereign Public Cloud is still consumption-based Azure. With Sovereign Private Cloud, much of the responsibility moves to your organisation or its operator. Comparing the two fairly takes more than compute and storage prices:
- hardware and refresh cycle;
- reserved capacity and unused headroom;
- datacentre, energy, and networking;
- platform operations, updates, and on-call coverage;
- backup, recovery, and separate test environments;
- support and vendor dependencies;
- licensing and Marketplace products;
- audit evidence and ongoing control operation.
Hold the functional scope, the risk basis and the evaluation period constant. Setting on-demand public-cloud usage against fully reserved private capacity produces a number, but not one that helps anyone decide.
Select the Azure cost dataset for the question
Azure Cost Management supports exports for Actual Cost, Amortized Cost, and FOCUS Cost. The 2026-06-01 Exports API lists all three types.
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, when the required fields and scope are covered.
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 defensible review in six steps
- Record the requirement and decision owner.
- Select the matching sovereign deployment model.
- Confirm Regions, services, exceptions, and required controls.
- Capture the complete target architecture, operations, and support.
- 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 sovereign cloud is more expensive in general. It is a decision someone can audit: which deployment model meets a named requirement, and what that particular model costs in your organisation.
The same review for AWS’s separate partition is set out in AWS European Sovereign Cloud: the cost questions before a migration. The Azure integration page lists which Azure cost data Costfluent reads.
Sources and review boundary
Reviewed on 6 September 2026: Microsoft’s Sovereign Cloud overview, Sovereign Public Cloud capabilities, EU Data Boundary overview, documented transfers outside the boundary, and Azure Cost Management Exports API.
Microsoft sources describe product models and commitments. The responsible organisation must determine legally and technically whether they satisfy a specific regulatory or contractual requirement.