Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Applies to: ✔️ Linux VMs ✔️ Windows VMs ✔️ Flexible scale sets ✔️ Uniform scale sets
Azure Compute offers virtual machine sizes that are isolated to a specific hardware type and dedicated to a single customer. Isolated sizes run on specific hardware generations. They're deprecated when the hardware generation is retired or a new generation becomes available.
Isolated virtual machine sizes are best suited for workloads that require a high degree of isolation from other customers’ workloads. This requirement sometimes applies to compliance and regulatory standards. Utilizing an isolated size guarantees that your virtual machine is the only one running on that specific server instance.
Additionally, as the isolated size virtual machines are large, customers may choose to subdivide the resources of these virtual machines by using Azure support for nested virtual machines.
Isolated VM sizes
1 These sizes are announced for retirement
Note
Isolated VM sizes have a limited lifespan that is tied to the lifetime of the hardware they run on.
Retired Isolated VM Sizes
Isolated VM sizes have a hardware limited lifespan. Azure issues reminders 12 months in advance of the official deprecation date of the sizes and provides an updated isolated offering for your consideration. The following sizes are retired or announced for retirement.
| Size | Retirement Announcement | Isolation Retirement Date | Migration Guide |
|---|---|---|---|
| Standard_DS15_v2 | 05/15/2020 | 05/15/2021 | Migration Guide |
| Standard_D15_v2 | 05/15/2020 | 05/15/2021 | Migration Guide |
| Standard_G5 | 02/15/2021 | 02/28/2021 | Migration Guide |
| Standard_GS5 | 02/15/2021 | 02/28/2021 | Migration Guide |
| Standard_E64i_v3 | 02/15/2021 | 02/28/2021 | Migration Guide |
| Standard_E64is_v3 | 02/15/2021 | 02/28/2021 | Migration Guide |
| Standard_M192is_v2 | 03/22/2027 | 03/31/2027 | Migration Guide |
| Standard_M192ims_v2 | 03/22/2027 | 03/31/2027 | Migration Guide |
| Standard_M192ids_v2 | 03/22/2027 | 03/31/2027 | Migration Guide |
| Standard_M192idms_v2 | 03/22/2027 | 03/31/2027 | Migration Guide |
FAQ
Q: What specific scenarios benefit most from isolated VM sizes?
A: Isolated VM sizes run on dedicated physical servers for maximum security and consistency. These sizes are best for regulated workloads, highly sensitive data, and performance-critical systems.
Q: How are isolated VMs different from Azure Dedicated Hosts and Confidential VMs?
A: Isolated VMs run on a single physical server dedicated exclusively for one VM for strict compliance and isolation. Dedicated Hosts reserve an entire physical host for multiple VMs belonging to a single customer, giving full control on VM placement and maintenance scheduling. Confidential VMs use hardware-based encryption to protect data without requiring physical isolation.
Q: Is the size going to be retired or only its "isolation" feature?
A: If a VM sizes is published as isolated but doesn't have an "i" in its name, only the isolation feature is being retired (unless stated otherwise). VM sizes with an "i" in the name are deprecated entirely. We provide reminders 12 months in advance of the official deprecation of the isolated size.
Q: Is there downtime if my VM moves to nonisolated hardware?
A: For sizes where only isolation is retired (not the size), no action is needed and there's no downtime. If isolated is required, the announcement will include a recommended replacement size. Moving to that sizes requires resizing your VM.
Q: Is there any cost difference when moving from an isolated VM to a non-isolated VM?
A: Yes, isolated VM sizes carry a premium compared to non-isolated sizes. The premium is roughly 10% higher for isolated VMs
Q: What should I do if the isolated VM size I need is not available in my region?
A: Choose an alternative isolated SKU with similar specs or deploy to one of the supported regions.
Next steps
Customers can also choose to further subdivide the resources of these isolated virtual machines by using Azure support for nested virtual machines.