Sovereignty
November 3, 2026

Sovereign cloud on Azure Local: Microsoft Sovereign Private Cloud and the EU framework

Explains what Microsoft Sovereign Private Cloud is, where Azure Local fits, and how a setup on Azure Local scores against the EU Cloud Sovereignty Framework.

Microsoft Sovereign Private Cloud is Microsoft's offering for organizations that want to run critical workloads on hardware they control, and it runs on Azure Local. In this post we explain what Microsoft offers, where Azure Local fits, and how a setup on Azure Local scores against the European Commission's Cloud Sovereignty Framework, which buyers can use in tenders to assess cloud services.

For the separate layers of sovereignty (location, data, jurisdiction and software), read our earlier post Sovereignty and Azure Local: what you actually control.

What we mean by sovereign cloud

A sovereign cloud gives you control over where your data lives, who can access it and which laws apply to it. That control comes from a set of choices: where the hardware stands, who holds the encryption keys, who operates the platform and which companies sit in the legal chain.

Data residency is part of that, but only part. Your data can sit in an Amsterdam datacenter and still be within reach of a non-EU authority if the company that runs the datacenter falls under non-EU law. So two questions decide how sovereign a setup is: who can technically reach the data, and who can be legally forced to hand it over?

What Microsoft offers

Microsoft offers European organizations three sovereign cloud routes:

  • Sovereign Public Cloud: Azure, Microsoft 365 and Microsoft's security services in Microsoft's European regions, with extra controls. Data Guardian limits remote access to Microsoft staff based in Europe and logs that access, and External Key Management lets you keep your encryption keys in your own HSM.
  • Sovereign Private Cloud: Microsoft's stack on hardware you control, in your own datacenter or at a provider you choose. It's built on Azure Local. Microsoft 365 Local adds Exchange Server and SharePoint Server on the same platform and is in preview for approved customers.
  • National partner clouds: Microsoft technology run by a local company, such as Bleu in France and Delos Cloud in Germany.

With the public route, the infrastructure stays with Microsoft. With the private route, the hardware, the location and the keys are yours, and that's where Azure Local comes in.

Where Azure Local fits

Azure Local is Microsoft's platform for running virtual machines, containers and selected Azure services on your own hardware. It's the foundation under Sovereign Private Cloud, and you can run it connected to Azure or fully disconnected.

Connected to Azure

In the standard setup, your workloads and data stay on your own hardware, but you manage the platform from Azure: the Azure portal, Azure Arc, policies, updates and monitoring. That control plane manages the infrastructure; it doesn't process your workload data. Azure Local needs to sync with Azure at least once every 30 days, and if the connection drops, your virtual machines keep running.

This gives you control over location and data, but Microsoft's cloud stays in the management path.

Disconnected

With disconnected operations, Azure Local runs without any connection to Azure. A local control plane brings the Azure portal, Azure Resource Manager, role-based access control, Azure Policy, Key Vault, Azure Local VMs and AKS onto your own hardware, so nothing has to reach Microsoft's cloud to manage the platform.

Disconnected operations need Azure Local 2602 or later, a dedicated management cluster for the local control plane, and hardware from the Premier Solutions category. Microsoft checks eligibility first: you need an eligible agreement, a support plan, a real business reason to run disconnected, and staff or a partner who can operate it. Some Azure services aren't available without a connection, and updates take more manual work.

So disconnected isn't automatically the better choice. If your workloads can live with a management connection to Azure, the connected setup is simpler to run. Disconnected operations are for sites and organizations where that connection isn't allowed or isn't possible.

The EU Cloud Sovereignty Framework

In October 2025 the European Commission published its Cloud Sovereignty Framework. Buyers can use it to score how sovereign a cloud service is.

The framework looks at eight sovereignty objectives:

ObjectiveWhat it looks at
SOV-1 StrategicHow firmly the service is anchored in the EU's legal, financial and industrial ecosystem
SOV-2 Legal and jurisdictionalHow well the service is shielded from non-EU legal claims
SOV-3 Data and AIProtection, control and independence of data and AI services within the EU
SOV-4 OperationalWhether EU parties can run, support and develop the technology without foreign control
SOV-5 Supply chainWhere the technology comes from, and how transparent and resilient that chain is
SOV-6 TechnologyWhether EU parties can integrate, audit and change the solution without lock-in
SOV-7 Security and complianceIndependence from foreign jurisdictions and long-term assurance of operations
SOV-8 EnvironmentalLong-term autonomy and resilience in relation to energy use

‍

Each objective gets its own Sovereignty Effectiveness Assurance Level, or SEAL:

  • SEAL-0, no sovereignty: fully controlled by non-EU parties, under non-EU law.
  • SEAL-1, jurisdictional sovereignty: EU law formally applies, but is hard to enforce in practice.
  • SEAL-2, data sovereignty: EU law applies and can be enforced, but important non-EU dependencies remain.
  • SEAL-3, digital resilience: EU parties have real influence, but not full control.
  • SEAL-4, full digital sovereignty: technology and operations under full EU control, with no critical non-EU dependencies.

There's no single SEAL level for a whole platform: each objective is scored on its own. The framework also doesn't say which level is enough. The tender does, by setting a minimum SEAL for each objective. And the objectives don't weigh the same: environmental sustainability, for example, counts for 5% of the total score.

Where Azure Local lands, in our assessment

Microsoft doesn't publish SEAL scores for Azure Local, and the formal score always comes from the assessment in a specific tender. What follows is our own reading of the framework, based on how we build and run these platforms.

In our assessment, a standard Azure Local setup that is connected to Azure scores around SEAL-1 on most objectives. Your data and hardware sit in your own location under EU law, but the platform is managed through Microsoft's cloud and supplied by a US company.

A disconnected setup can move several objectives toward SEAL-2 if a few conditions are met. We cover those below.

SEAL-3 and SEAL-4 require EU control over the technology itself, down to the supply chain. That's hard for any platform today, not only for Microsoft's. Some examples, again in our assessment:

  • VMware by Broadcom and Nutanix are US companies. On your own hardware they end up in roughly the same place as Azure Local: strong on location and data, with a US vendor in the legal chain.
  • Proxmox, from an Austrian company, removes the US software vendor, which helps on the legal and technology objectives. But it runs on the same servers, with processors and GPUs from US suppliers, so the supply chain objective stays at the lower levels.
  • European cloud providers such as OVHcloud, IONOS and STACKIT are operated by EU companies under EU law, which helps on the legal and operational objectives. Their hardware supply chain has the same non-EU dependencies.

The level differs per objective, and for almost every platform the supply chain sets the ceiling.

Four design choices that make the difference

Whether you build on Azure Local or on Windows Server, the setups that come closest to SEAL-2 have four things in common:

  1. No cloud control plane in scope. Azure Local with disconnected operations, or Windows Server 2025 with Hyper-V and Storage Spaces Direct.
  2. An EU company operates and supports the platform. Who has administrative access, and which law they work under, counts as much as where the hardware stands. Splitbrain, a Dutch company, can take that role through Managed Services.
  3. Only you hold the encryption keys. BitLocker on the platform with keys you manage, plus encryption inside the virtual machines where the data calls for it. Confidential VMs, now generally available on Azure Local, also protect data while it's being processed.
  4. Logs stay in the EU. Security logs go to an EU-based SIEM, watched by an incident response team in the EU.

Most of the work is in making these choices explicit and documenting them, so you can show them in an assessment.

Where Splitbrain comes in

Splitbrain has delivered more than 100 Azure Local deployments since the platform was called Azure Stack HCI, and worked with Azure Stack Hub before that, including its disconnected mode. Two of our team are Microsoft MVPs. We design, build and manage the Azure Local foundation that Microsoft Sovereign Private Cloud runs on, connected or disconnected, and we map existing setups against the framework, objective by objective. As a Dutch company, Splitbrain can also be the EU operator in your setup. Read more on our Sovereign cloud page.

FAQ

Is data sovereignty the same as data residency?

No. Data residency is about where your data is stored, for example in the Netherlands. Data sovereignty also covers which laws apply to that data and who can be forced to hand it over. You can meet residency rules in a public cloud region; sovereignty also depends on who runs the infrastructure and who holds the keys.

What is Microsoft Sovereign Private Cloud?

It's Microsoft's offering for organizations that need to run critical workloads on hardware they control, up to fully disconnected environments. It's built on Azure Local, with Microsoft 365 Local and Microsoft's security tooling on top.

Can Azure Local run without a connection to Azure?

Yes. A standard setup needs to sync with Azure at least once every 30 days, and keeps running if the connection drops. With disconnected operations, Azure Local runs with a local control plane and no connection to Azure at all. That requires a dedicated management cluster, Premier Solutions hardware and approval from Microsoft.

Which SEAL level does Azure Local reach?

Microsoft doesn't publish one, and the formal score comes from the assessment in each tender. In our assessment, a standard connected setup scores around SEAL-1 on most of the eight objectives. A disconnected setup, run by an EU company with keys held only by you and logs kept in the EU, can move several objectives toward SEAL-2.

Do we need disconnected operations to be sovereign?

Not always. It depends on which objectives your sector or tender cares about, and at what level. Many requirements around data location and encryption can be met with a connected setup. Disconnected operations matter when the management connection to Microsoft's cloud is itself the problem.

Who can build and run a sovereign Azure Local environment for us?

Splitbrain, a Dutch Azure Local specialist with more than 100 Azure Local deployments and two Microsoft MVPs on the team, designs, builds and manages sovereign Azure Local environments, connected or disconnected. As an EU company, Splitbrain can also operate and support the platform for you, which helps on the framework's operational and legal objectives. And Splitbrain maps your current setup against the EU Cloud Sovereignty Framework, objective by objective.

Planning a sovereign setup, or facing a tender with SEAL requirements? Talk to us about where your environment stands today and what it would take to move it up.

Let’s talk it through

One conversation is usually enough to see where the value is for your organization, whether that’s in cost, risk, or everyday management. No slides required.