Skip to content

Independent marketplace for verified cloud accounts

Azure vs Hetzner

Hetzner sells capacity at a price Azure does not try to match. This comparison covers what the gap actually buys you, from licensing and egress to support and region choice.

Buy Azure Account
Microsoft ecosystem integration

Microsoft Azure

Regions noted in source
Global region network
Configurations listed
13
From$25 View account
Buy Hetzner Account
Germany, EU hardware value

Hetzner

Regions noted in source
Germany, Finland, United States, Singapore
Configurations listed
3
From$50 View account

Comparing Microsoft Azure with Hetzner looks unfair on paper. One is a global platform with hundreds of services and an enterprise sales organisation. The other is a German hosting company that sells very cheap machines and very little else. Put a vCPU next to a vCPU and Hetzner wins the price line by a distance that is not close.

The interesting question is not whether the gap exists. It is what the gap buys, and whether your workload needs any of it. Plenty of teams pay Azure prices for things they never use, and plenty of others move to Hetzner and quietly rebuild a worse version of what they gave up.

The difference is not raw performance

Hetzner runs modern hardware in its own facilities and sells it close to cost, partly because it builds a lot of its own infrastructure and partly because its support and sales overhead is small. For a CPU bound workload on a single machine, you are not buying slower silicon by going to Hetzner. People who assume cheap means underpowered are usually surprised.

What you are buying less of is everything around the machine: the managed services, the global control plane, the policy tooling, the identity integration, the compliance paperwork and the account team. Azure’s price includes all of that whether you use it or not.

So the real test is a list, not a benchmark. Write down which Azure services your architecture actually calls. If the list is virtual machines, a database you could run yourself, object storage and a load balancer, the gap is mostly going to waste.

Licensing is the line item most people miss

If your workload is Windows Server or SQL Server, the comparison changes shape. Microsoft licensing terms treat workloads differently depending on where they run and what entitlements you already hold, and the arrangements available on Azure for existing licences have no equivalent at a budget host. On Hetzner you are responsible for sourcing and complying with Windows or SQL Server licensing yourself, and the cost of doing that can erase a large part of the hardware saving.

We are deliberately not quoting figures, because they depend on your edition, your core counts and your agreement. The point is to put licensing in the model before you compare the monthly server price. A Linux workload and a Windows workload produce very different answers to the same question.

The same caution applies to other commercial software with core based or socket based licensing. Running it on a cheap dedicated machine with a lot of cores can cost more in licence fees than the hardware saves, which is one of the few places where a smaller, more expensive virtual machine is the cheaper option overall. Check the licence metric before you size the box.

Identity and access as your team grows

Azure ties access to a corporate directory, so cloud permissions follow joiners and leavers through the same process as everything else. Role assignments can be scoped narrowly, and policy can block a non compliant deployment before it is created. For an organisation with auditors, that machinery is most of what they are buying.

Hetzner has an account model suited to a hosting customer rather than an enterprise directory. It works, and for a small team it works well, but there is no policy engine standing between an engineer and a mistake. The control has to come from your own pipeline: deployments go through code review, nobody clicks in the console, and access to the account itself is tightly held. That is achievable, and it is a habit rather than a product.

Bandwidth and egress

Azure bills outbound data transfer separately, and for content heavy applications that line frequently grows past the compute line. It is the single most common cause of a bill that does not match the forecast, which is why we wrote cloud egress fees explained as a standalone guide.

Hetzner takes the opposite approach and includes a substantial traffic allowance with its servers, with overage priced low. For anything that pushes a lot of bytes to users, this is often a bigger saving than the server price itself. If you run video, downloads, backups or a busy public API, model the transfer cost on both sides before anything else.

Side by side

Dimension Microsoft Azure Hetzner
Primary buyer Enterprise IT and platform teams Developers, agencies, cost led teams
Service catalog Very broad, managed services for most patterns Compute, storage, networking, load balancing
Outbound traffic Metered and billed separately Generous allowance included with servers
Windows and SQL Server First class, with licensing arrangements You source and manage licensing yourself
Identity integration Ties into the Microsoft directory estate Local account model, no directory integration
Dedicated hardware Available as specialised offerings Core part of the product line
Operational burden Lower if you adopt managed services Higher, you run more of the stack

Where the machines are

Azure operates a large global region estate with availability zones inside many regions, which is the mechanism that lets you survive a single datacenter failure without changing provider. If your users are spread across continents, or your design assumes zone redundancy, that architecture is doing real work. Our guide to how cloud regions and availability zones work explains what the distinction actually guarantees.

Hetzner’s footprint is concentrated in Europe with a smaller presence elsewhere. For a European audience that is fine and often better, since latency to European users is excellent. For a global consumer product, you will be adding a content delivery network and accepting longer round trips for distant users, or running capacity with more than one provider.

What you end up operating, and who you call

On Azure you can hand off database patching, backup scheduling, certificate rotation, secret storage and cluster upgrades to managed services. On Hetzner most of that is yours. Not impossible, and for an experienced team not even difficult, but it is work that recurs forever and it needs someone on call.

Count that honestly in hours. An engineer spending a day a week on maintenance is a real cost, and at a certain team size it exceeds the saving. Below that size, especially for teams who already automate their infrastructure, the saving is substantial and the extra work is marginal. Infrastructure as code and the provider model is worth reading if you intend to keep the Hetzner estate reproducible rather than hand built.

Support follows the same split. Azure sells support as tiered plans with defined response commitments and escalation paths, and at enterprise tiers you get named contacts. Hetzner provides support appropriate to its price point: competent for hardware and network issues, not a substitute for an architecture consultant.

Neither is wrong. Just do not plan a regulated production system around a support relationship you have not purchased.

Running both on purpose

The split estate is underrated here. Keep the workloads that need Azure on Azure, for identity integration, Windows licensing or a managed service you genuinely rely on. Put the bulk capacity, the batch processing, the build runners, the staging environments and the bandwidth heavy pieces on Hetzner. Many teams cut a large share of their bill this way without touching the parts of the architecture that justify the premium.

The cost is a second set of credentials, a second monitoring target and a connection between the two. Treat each environment as its own account boundary, as described in separate cloud accounts per environment, and the complexity stays manageable.

Picking one

Go with Azure when Windows licensing, directory integration, zone level redundancy, broad managed services or an enterprise support commitment are part of the requirement. Go with Hetzner when you want a lot of compute and bandwidth for a small amount of money, your audience is largely European, and your team is comfortable running the stack.

Verified accounts for both are listed under Buy Azure Account and Buy Hetzner Account. Any credits included with an account are the provider’s to control: they expire, they carry service restrictions, and you should verify the remaining balance inside the provider console after transfer. For a closer look at the budget end of the market, the Hetzner vs Contabo comparison covers how the value hosts differ from each other.

Other comparisons to consider

Google Cloud vs Azure
vs

Google Cloud vs Azure

Google Cloud and Microsoft Azure both cover the full hyperscaler surface, but identity, data tooling and commercial structure pull teams…

AWS vs Azure
vs

AWS vs Azure

Azure is usually chosen through identity and licensing rather than through infrastructure. This comparison covers enterprise agreements, hybrid estates, hierarchy…

Azure vs IBM Cloud
vs

Azure vs IBM Cloud

Azure sells a platform, IBM Cloud sells a platform plus an engagement. This comparison looks at workload lineage, governance, support…

Hetzner vs Contabo
vs

Hetzner vs Contabo

Both are German hosts competing on low prices, and Contabo is usually the cheaper number on the page. The useful…

Background reading

What Cloud Credits Cover, and What They Never Cover
Cost Management 7 min read

What Cloud Credits Cover, and What They Never Cover

A credit is a conditional, time limited, provider controlled entitlement, not money. What a balance actually buys, what it refuses to buy,…

Multi-Factor Authentication Across Cloud Providers
Security and IAM 7 min read

Multi-Factor Authentication Across Cloud Providers

MFA is the single highest-value control on a cloud login, but only if recovery is planned. This guide compares factor types, enrolment…

Decided which platform fits?

Both accounts are documented in the catalog, with configurations, credit balances and service limits listed before you buy.

Telegram