What Is Azure Dedicated Host?

Microsoft announced the preview launch of Azure Dedicated Host, a cloud service that allows customers to run virtual machines on single-tenant physical servers inside Azure’s data centers. Unlike standard Azure VM deployments — where multiple customers share the same underlying hardware — Dedicated Host gives a single organization exclusive use of a physical machine.

This is a meaningful shift for enterprises that have strict requirements around hardware isolation, whether for regulatory compliance, security policy, or workload predictability.

Why Single-Tenant Hosting Matters

Shared multi-tenant infrastructure is the default model in public cloud. It is cost-efficient and highly flexible, but it introduces concerns that some organizations cannot accept:

• Noisy neighbour risk: Other tenants’ workloads can compete for CPU, memory bandwidth, or I/O on the same physical host.
• Compliance requirements: Regulations such as HIPAA, FedRAMP, and PCI-DSS may require demonstrable physical isolation of compute resources.
• Data sovereignty and audit trails: Some industries require the ability to certify exactly which physical hardware processed sensitive data.
• Scheduled maintenance control: Dedicated Host gives customers more visibility and control over when maintenance events affect their machines.

Azure already offered isolated VM sizes for a limited set of large instance types before this announcement, but those options did not provide the same level of flexibility or hardware visibility that Dedicated Host introduces.

Hardware Specifications

At preview launch, Microsoft offered two host types based on Intel Xeon processors:

• Type 1: Intel Xeon E5-2673 v4 (Broadwell), base clock 2.3 GHz, boost up to 3.5 GHz.
• Type 2: Intel Xeon Platinum 8168 (Skylake), single-core boost up to 3.7 GHz.

Both types were available with memory configurations ranging from 144 GiB to 448 GiB. Hosts offered up to 48 physical cores, giving teams a large pool of resources to allocate across their VMs.

Supported Workloads and OS

When generally available, Azure Dedicated Host was planned to support virtual machines running:

• Windows Server
• Linux distributions available on Azure
• SQL Server

This covers the vast majority of enterprise workloads that teams typically migrate to or build on Azure.

Pricing Model

Azure Dedicated Host uses per-host pricing, meaning customers are billed for the physical host itself rather than for the individual VMs running on it. At preview launch, pricing was listed at approximately $4.039 per hour per host. This model has a significant implication: the cost is fixed regardless of how many VMs you deploy on the host, so teams benefit from maximising host utilisation.

This is a different cost profile from standard pay-per-VM pricing. Engineering and finance teams evaluating Dedicated Host should model their expected VM density carefully before committing.

Host Groups: Building Private Clusters in Azure

One notable feature is the ability to aggregate multiple Dedicated Hosts into host groups within an Azure region. This lets organizations effectively build clusters of private physical servers inside the Azure data center — combining the control of on-premises hardware with the operational benefits of cloud infrastructure (geographic redundancy, Azure networking, managed storage, and so on).

Host groups can span availability zones within a region, supporting high-availability architectures without sacrificing physical isolation.

How Azure Dedicated Host Compares to Competitors

Azure is not the first major cloud provider to offer single-tenant dedicated hardware. Both AWS and Google Cloud have had equivalent products for some time:

• AWS Dedicated Hosts: Single-tenant EC2 capacity, per-host billing, supports Bring Your Own License (BYOL).
• Google Cloud Sole-Tenant Nodes: Single-tenant physical servers within GCP, configurable node types.

Azure Dedicated Host brings Microsoft into parity with its main competitors for this use case. For organizations already invested in the Microsoft ecosystem — particularly those running Windows Server and SQL Server with existing software assurance or BYOL agreements — Azure Dedicated Host may offer licensing cost advantages worth modelling.

Key Use Cases for DevOps Teams

• Regulated industries: Financial services, healthcare, and government workloads that require physical isolation attestation for audits.
• Lift-and-shift migrations: Moving on-premises workloads that were running on dedicated hardware and cannot be placed on shared infrastructure.
• Licensing optimisation: Running Windows Server or SQL Server with existing per-core licenses under BYOL terms, which may reduce software costs significantly on a dedicated host.
• Performance-sensitive workloads: Eliminating noisy-neighbour effects for latency-critical or throughput-intensive applications.

Summary

Azure Dedicated Host fills a real gap for enterprise customers who need physical isolation without abandoning public cloud infrastructure. The per-host billing model, flexible VM placement, host groups, and compliance positioning make it a credible option for regulated workloads. Teams evaluating this service should assess VM density requirements, compare total cost against reserved VM instances, and confirm whether their compliance framework specifically mandates physical isolation — because for many workloads, Azure’s existing isolation VM sizes or confidential computing options may be sufficient.