This article is based on reporting originally published at ibtimes.com (August 2019) covering the announcement of Azure Dedicated Host.
What Is Azure Dedicated Host?
Microsoft announced Azure Dedicated Host, a service that provisions single-tenant physical servers inside Azure data centers. Unlike standard virtual machines, which run on shared physical hardware alongside other customers’ workloads, an Azure Dedicated Host gives your organization exclusive use of the underlying physical machine. You then deploy your Azure VMs onto that dedicated hardware just as you would on any other Azure compute resource.
This is a meaningful architectural shift for enterprises that need hardware-level isolation rather than the logical isolation that ordinary virtual machines provide.
Why Hardware Isolation Matters
Standard multi-tenant cloud infrastructure is cost-effective, but it is not always appropriate. Common drivers for dedicated hardware include:
- Regulatory compliance – Industries such as finance, healthcare, and government often require demonstrable hardware-level isolation to satisfy auditors and regulators.
- Bring-your-own-license (BYOL) – Certain software vendors (notably Microsoft itself for Windows Server and SQL Server) allow existing on-premises per-core or per-socket licenses to be reused only on dedicated hardware.
- Security posture – Eliminating shared physical hardware removes a class of side-channel attack vectors (such as speculative-execution exploits) that are difficult to fully mitigate in multi-tenant environments.
- Controlled maintenance windows – On dedicated hosts, Azure exposes maintenance control options that let teams schedule host-level updates rather than accepting platform-driven restarts.
Supported Workloads and Operating Systems
Azure Dedicated Host supports virtual machines running Windows Server, Linux, and SQL Server. Hosts are available in different SKU families (for example, general-purpose, compute-optimized, or memory-optimized) that map to the underlying physical server specifications. The VM sizes you can deploy on a given host are determined by the host SKU you select.
Pricing Model
Azure Dedicated Host is billed per physical host, not per individual virtual machine. This means you pay for the entire host regardless of how many VMs are running on it. The practical implication is that the service becomes more cost-efficient the more densely you pack VMs onto the host. Pricing varies by host SKU and Azure region. Microsoft also offers Reserved Instances for Dedicated Hosts to reduce costs when committing to one- or three-year terms.
Host Groups: Organizing Dedicated Infrastructure
Azure allows you to create Host Groups, logical containers for multiple Dedicated Hosts. Host Groups operate within a single Azure region and can span multiple Availability Zones. This lets teams:
- Distribute workloads across hosts for fault tolerance.
- Manage related hosts as a single administrative unit.
- Optionally enable automatic VM placement so Azure selects the best available host within the group.
How Azure Dedicated Host Compares to Isolated VM Sizes
Azure already offered isolated VM sizes (such as the Standard_M128ms or certain Lsv2 sizes) that guarantee a VM occupies an entire physical host by virtue of consuming all available resources. Azure Dedicated Host is a different mechanism: you explicitly provision and manage the host, choose which VM sizes to run on it, and retain visibility into the physical layer. Isolated VM sizes are simpler but offer less control; Dedicated Host trades simplicity for greater flexibility and licensing transparency.
Competitive Landscape
Azure Dedicated Host entered a market where dedicated single-tenant hardware was already available from major cloud providers:
- Amazon Web Services offers EC2 Dedicated Hosts and Dedicated Instances, with similar per-host billing and BYOL support.
- Google Cloud provides Sole-Tenant Nodes, which operate on the same principle of exclusive physical server access within GCP’s infrastructure.
Microsoft’s entry strengthens Azure’s credibility with enterprise customers who have strict compliance requirements and had previously viewed the dedicated-hardware option as a reason to favor AWS.
Security and Compliance Considerations
Microsoft positions Dedicated Host as part of its broader enterprise compliance story. Because your organization controls which VMs run on the host, you can demonstrate to auditors that no other customer’s workloads co-reside on the same physical hardware. Azure’s standard security controls — including disk encryption, network security groups, Azure Defender, and Azure Policy — all apply to VMs running on Dedicated Hosts.
Key Takeaways for DevOps and Platform Teams
- Azure Dedicated Host is appropriate when compliance mandates, software licensing, or security policy require physical isolation — not simply logical isolation.
- Cost modelling should account for the per-host billing model; under-utilized hosts are expensive.
- Host Groups and Availability Zone support make it feasible to build resilient architectures on dedicated hardware.
- Existing Azure tooling (ARM templates, Terraform’s AzureRM provider, Bicep) supports Dedicated Host provisioning, so it integrates into standard IaC workflows.
- Evaluate BYOL eligibility carefully with your licensing team; the savings can be significant for SQL Server and Windows Server workloads at scale.