What Is Azure Dedicated Host?

Microsoft announced a public preview of Azure Dedicated Host in August 2019, a service that provides organizations with exclusive access to physical Azure servers — hardware that is not shared with any other customer. This model is commonly called single-tenant infrastructure, as opposed to the multitenant model in which multiple customers share the same underlying hardware.

For most Azure customers, virtual machines (VMs) run on shared physical hardware alongside workloads from other organizations. While Azure’s hypervisor and security architecture isolate those workloads, certain industries — healthcare, finance, defence and government contracting, for example — operate under regulatory or compliance mandates that explicitly require dedicated, unshared hardware. Azure Dedicated Host was designed to satisfy those requirements.

Supported Workloads

Azure Dedicated Host supports a range of common enterprise workloads on its single-tenant physical servers:

• Linux VMs — any Azure-supported Linux distribution running on a dedicated host.
• Windows Server VMs — Windows workloads with the option to bring existing licenses.
• SQL Server on Azure VMs — SQL Server instances hosted inside Azure VMs on dedicated hardware.

How Azure Dedicated Host Compares to Competing Services

Azure Dedicated Host is broadly comparable to similar offerings from the other major cloud providers:

• AWS Dedicated Hosts — Amazon Web Services launched dedicated hosting several years before this Azure preview, giving AWS customers a head start with the single-tenant model.
• Google Cloud Sole-Tenant Nodes — Google Cloud Platform offers an equivalent feature called a sole-tenant node, which reserves a physical Compute Engine server for a single project.

It is worth noting that Azure Government is not a single-tenant service. According to a Microsoft spokesperson at the time: “Azure Government is a cloud service that is shared but dedicated to government customers. As a shared cloud service, Azure Government does not provide customers control over the actual VM to physical host mapping.” Azure Dedicated Host fills a different and complementary role.

Hardware Options and VM Series

Customers provisioning an Azure Dedicated Host select a host type that determines the underlying hardware characteristics — VM series, RAM capacity, processor brand, and core count. A single host type supports only one VM series, though multiple VM sizes within that series can be mixed on the same host.

At preview launch, Microsoft documented two dedicated host types on its pricing page:

• Dedicated Host Type 1 — supports the Dsv3 and Esv3 Series VMs (general purpose and memory-optimised workloads).
• Dedicated Host Type 2 — supports the Fsv2 Series VMs (compute-optimised workloads).

Additional host types were expected to become available as the service moved toward general availability.

Maintenance Control: Deferring Updates Up to 35 Days

One of the most operationally significant features of Azure Dedicated Host is granular control over host-level maintenance. On multitenant Azure infrastructure, Microsoft schedules and applies host OS updates on behalf of all customers. With a dedicated host, that control shifts to the customer.

“With an Azure Dedicated Host, you can control all host-level platform maintenance initiated by Azure (e.g., host OS updates). An Azure Dedicated Host gives you the option to defer host maintenance operations and apply them within a defined maintenance window, 35 days. During this self-maintenance window, you can apply maintenance to your hosts at your convenience, thus gaining full control over the sequence and velocity of the maintenance process.”

— Microsoft Azure announcement, August 2019

This is particularly valuable for organisations running high-availability applications where unplanned reboots can cause costly downtime or SLA breaches. A 35-day deferral window allows teams to align host maintenance with pre-approved change control periods.

Pricing Model

Azure Dedicated Host uses a layered pricing structure:

• Host cost — a charge for reserving the entire physical host, regardless of how many VMs are actually running on it.
• VM hourly cost — standard Azure VM charges for each virtual machine provisioned on the host.
• Windows licensing cost — an additional hourly charge when running Windows Server VMs, unless existing licenses are applied via Azure Hybrid Benefit (see below).

Because customers pay for the entire host upfront, right-sizing the host type relative to actual VM density is essential for cost efficiency. Underutilised dedicated hosts can be significantly more expensive per workload than equivalent multitenant VMs.

Licensing: Azure Hybrid Benefit and the October 2019 Deadline

Microsoft used the Azure Dedicated Host launch to introduce updated licensing rules that rewarded early adoption. Organisations could apply their existing on-premises Windows Server and SQL Server licenses to Azure Dedicated Host workloads through the Azure Hybrid Benefit program — the mechanism that allows on-premises volume licenses to be re-used on Azure infrastructure.

The key licensing conditions at the time of the preview announcement were:

• Licenses purchased before October 1, 2019 could be used on Azure Dedicated Host without requiring active Software Assurance coverage.
• Licenses purchased on or after October 1, 2019 would require Software Assurance to qualify for Azure Hybrid Benefit on dedicated hosts.
• The October 2019 deadline also applied to software hosted by what Microsoft called Listed Providers: Microsoft itself, Alibaba, Amazon (including VMware Cloud on AWS), and Google. Other hosting providers were not subject to this change.

This licensing approach gave organisations running compliant on-premises estates an economic incentive to migrate to Azure Dedicated Host before the deadline, while aligning future dedicated-host licensing more closely with Microsoft’s standard Software Assurance requirements.

Key Takeaways for DevOps and Cloud Engineers

• Compliance-driven architectures — if your organisation requires physical host isolation for regulatory reasons (PCI-DSS, HIPAA, FedRAMP equivalents, etc.), Azure Dedicated Host provides a documented single-tenant boundary within the Azure public cloud.
• Maintenance windows matter — the ability to defer host OS patching by up to 35 days gives platform and SRE teams meaningful control over change management schedules.
• VM series constraints are real — plan host type selection carefully; mixing VM series on a single dedicated host is not supported.
• Cost modelling is non-trivial — pay-for-the-whole-host pricing requires higher VM density to achieve cost parity with standard Azure VMs.
• Azure Hybrid Benefit is the cost lever — organisations with existing Windows Server and SQL Server volume licenses should evaluate whether Azure Hybrid Benefit applies before provisioning.