Best European Alternatives to Microsoft Azure

Why people leave Microsoft Azure

Azure has a European story and it is a good one. The EU Data Boundary spans the EU and the EFTA states and runs on Microsoft datacentres in fifteen European countries, and for the services in scope, customer data is stored and processed inside it. If your requirement is that European data sits on European soil, Azure can satisfy it.

The catch is particular to Azure and it is easy to miss. For Microsoft 365 the boundary follows from where the tenant signed up: an organisation is inside it without anyone doing anything. For Azure, scope is something you produce.

Regional services count when you deploy them into an EU or EFTA region, which is a decision an engineer makes per resource. Non-regional Azure services have to be configured individually to fall inside, with a separate documentation page describing how for each one. And to keep the professional services data associated with Azure inside the boundary, Azure Resource Manager itself has to be set to it.

So the boundary in Azure is not a property of your subscription. It is a per-resource configuration task spread across everyone with deployment rights, and a service brought up in the wrong region or left unconfigured puts that workload outside a commitment your compliance register says you have. On a European provider there is no configuration that could produce the wrong answer, because there is no boundary to fall out of.

• Scope is something your engineers produce, resource by resource A West Europe deployment is in; a resource somebody spun up in East US for a load test is out; a non-regional service nobody configured is out until it is configured. None of that is hidden and all of it is documented, which is the point: the commitment is real and its application depends on hundreds of small decisions made by people who are optimising for latency, quota and cost rather than for jurisdiction. Nobody audits a subscription for it until an auditor does.
• Entra ID is the lock, and it is not on the price list you are reviewing Compute is portable and identity is not. Entra ID authenticates your applications, your devices and your Microsoft 365 tenancy, and moving virtual machines to Hetzner changes nothing about that dependency. Microsoft also documents that limited directory data, including username and email address, is replicated outside the boundary to operate the service. So the component that binds you hardest to Azure is also the one least covered by the European commitment you are relying on.
• Sovereignty has become a product tier Microsoft now sells a Sovereign Public Cloud, a Sovereign Private Cloud including disconnected deployments, and an independently operated partner ecosystem, with European personnel approving operational access, tamper-evident logging and customer-held keys in hardware security modules. It is a serious answer and for some regulated buyers it is the right one. It is also a supplier selling the remedy to a concern about the supplier, on terms the supplier sets. A German or French provider charges you for compute and the jurisdiction is not a SKU.
• The invoice is unpredictable by design Azure prices per service, per region, per tier, adjusted by reserved instances, savings plans, hybrid benefit and a support agreement, and almost no organisation can forecast next month from this month. Hetzner publishes about €4.51 a month for its entry cloud server, OVHcloud about €3.50 for a VPS and IONOS from about €1. You can argue the services are not equivalent, and often they are not. You cannot argue about which figure a budget holder can work with.

What you have to replace, not just match

Sort your Azure estate into three piles before you look at a price list, because the four providers here cover one pile completely, one partially and one not at all.

The first is infrastructure: virtual machines, block and object storage, load balancers, managed Kubernetes, managed databases. Every provider on this page does this, generally at a fraction of what you are paying. The second is identity, and nothing here replaces Entra ID. The third is the managed catalogue — the data pipelines, event buses, integration runtimes and model endpoints you consume rather than operate — and replacing those means rewriting applications rather than moving them.

Organisations that succeed at this start with the first pile, plan the second as its own project, and deliberately leave the third on Azure for a year or more. Those that fail try to do all three at once because the business case was written as a single number.

The alternatives compared

How each alternative compares to Microsoft Azure

What actually breaks when you switch

Identity is the project, and everything else is logistics. Entra ID underpins device access, application sign-in and your Microsoft 365 tenancy, and none of the four providers here replaces it. Decide early whether you keep Entra for identity while moving workloads, or stand up your own directory, because that decision determines the sequence of everything after it.

Then find the managed services you forgot you were consuming. A Service Bus queue, a Key Vault, a Logic App wired into finance, a Cognitive Services endpoint behind a feature nobody owns any more. Each one is a rewrite rather than a migration, and each one is discovered late. Enumerate the resource groups before you commit to a date.

And budget for the operational load that comes back to you. On Azure, patching, backup, failover and monitoring are line items; on a European VPS they are rotas. The saving on the invoice is real and so is the work it hands back, and a migration plan that counts only the first has not been costed.

We deploy in West Europe already. Are we inside the boundary or not?

For those regional resources, yes. Microsoft is explicit that regional Azure services deployed into an EU or EFTA region are in scope, and West Europe qualifies.

The question is what else is in the subscription. Non-regional Azure services are not automatically in scope and each has its own configuration to bring it inside. Anything sitting in a non-European region, for whatever good operational reason, is outside. And the professional services data tied to Azure stays in the boundary only if Azure Resource Manager has been configured for it.

The practical test is to ask who in your organisation has ever checked. In most Azure estates the answer is nobody, because the people choosing regions are choosing for latency and quota. That is not negligence; it is what happens when a compliance property is implemented as a deployment-time option.

What does Azure do that none of these four do?

Identity, first and decisively. Entra ID is the spine of a Microsoft estate and there is no drop-in equivalent on this page. If devices, applications and Microsoft 365 all authenticate through it, moving compute does not move that, and you need a plan for it before you move anything else.

The managed catalogue, second. Azure sells hundreds of services you consume rather than run. These four sell compute, storage, networking, managed Kubernetes and managed databases, which covers infrastructure thoroughly and the layer above it barely at all.

Third, the commercial relationship. Enterprise agreements, hybrid licensing benefits and an account manager with discounting authority are real advantages at scale, and a comparison that leaves them out is not an honest one.

Is Swiss hosting stronger than German or French for this?

Not in the way people assume, and Microsoft's own boundary illustrates why: it includes the EFTA countries, Switzerland among them, so on that measure Swiss and German hosting sit on the same side.

Switzerland's distinction is that it is outside EU law as well as American law while holding an adequacy decision, so personal data flows there lawfully. Some organisations read that as a second layer of independence; others read it as an extra border introduced into a procurement process that did not need one.

For an EU public body with a rule about processing inside the single market, Infomaniak's Geneva and Winterthur datacentres are outside it, and that is a decision to take deliberately rather than discover at audit. For a private company concerned about American legal reach, Swiss and EU providers answer equally well.

How much of the saving is actually real?

The headline gap is genuine. Entry pricing around €4.51 a month at Hetzner, about €3.50 for an OVHcloud VPS and from about €1 at IONOS is not the same order of magnitude as a comparable Azure line item, and the included outbound traffic allowances widen it further.

The gap narrows against the work that comes back. Patching, backup, failover, monitoring and an on-call rota are services on a hyperscaler and jobs on a European VPS. For a team of three without an infrastructure engineer, part of that saving is being paid for in evenings.

The rule that holds up is this: the saving is close to the headline for steady-state workloads you already operate yourself, and much smaller wherever you were paying Azure to do the operating on your behalf.

Which one to pick

If your reason for leaving is the exception list rather than the storage location, any of these four removes it, because none of them needs a boundary document in the first place. Choose on price, scale and paperwork instead.

For conventional compute where the bill is the complaint, Hetzner wins and it is not close. Select the European locations explicitly and the jurisdiction question is closed.

For an organisation replacing Microsoft 365 in the same programme, Infomaniak is the only provider here that covers both halves, with Swiss jurisdiction as the reason it was shortlisted and the suite as the reason it wins.

For anything large, regulated, or answerable to a national security framework, OVHcloud is the answer and the SecNumCloud qualification is why. IONOS is the one to choose when the obstacle is not technical at all but a committee that needs a German supplier it recognises.