# Outdated virtual machine version in Azure | Cloud Efficiency Hub Canonical: https://www.pointfive.co/efficiency-hub/inefficiencies/outdated-virtual-machine-version-in-azure Many organizations choose a VM SKU and version (e.g., `D4s_v3`) during the initial planning phase of a project, often based on availability,... By: Jurian van Hoorn Updated: 2026-09-28 [Cloud Efficiency Hub](https://www.pointfive.co/efficiency-hub) # Outdated Virtual Machine Version in Azure The short version Many organizations choose a VM SKU and version (e.g., \`D4s\_v3\`) during the initial planning phase of a project, often based on availability, compatibility, or early cost estimates. [Jurian van Hoorn](https://www.linkedin.com/in/j-hoorn/) Operations Senior (Azure Cloud) @ Netcompany Azure service [Azure Virtual Machines](https://www.pointfive.co/efficiency-hub/cloud-services/azure-virtual-machines) Category [Compute](https://www.pointfive.co/efficiency-hub/service-category/compute) Reference CER-0102 Type Outdated Version ## Explanation Why the waste happens and who it affects. Over time, Microsoft releases newer hardware generations (e.g., \`D4s\_v5\`, \`D4s\_v6\`) that offer equivalent or better performance at the same or reduced cost. However, existing VMs are not automatically migrated, and these newer versions are often overlooked unless intentionally evaluated. This inefficiency tends to persist because switching to a newer version typically requires VM deallocation and resizing, which introduces temporary downtime. As a result, outdated VM series versions continue to run indefinitely, even in environments where brief downtime is acceptable. The cost delta between series versions - especially across certain families like \`D\`, \`E\`, or \`F\`-can be significant when scaled across environments or multiple VMs. Note that VM series versions (v3 through v7) are distinct from VM generations (Gen 1 vs Gen 2), with series versions representing the primary opportunity for cost optimization. The two are linked for the newest series, however: v6 and v7 sizes require Generation 2 images with NVMe disk support, so moving an older VM to them is a planned migration rather than a simple resize. ## Billing model The pricing dimensions that drive this cost. Azure VMs are billed per full minute of runtime based on instance size, operating system, and hardware generation (series version). Newer VM versions typically offer equivalent or better performance at the same or reduced cost due to improved infrastructure efficiency. Legacy versions may persist in production environments despite suboptimal price/performance ratios, simply because they were originally selected during initial provisioning or project planning. ## How to detect 8 checks to find it in your estate. - Identify running VMs using older version SKUs (e.g., v3 or v4 when v5, v6, or v7 are available) - Compare current SKUs to newer available versions within the same family and size class - Check whether newer versions are available in the same region and support the required OS or workload - Confirm whether the VM image is Generation 2 and supports NVMe storage and the MANA network adapter before targeting v6 or v7 sizes - Assess cost differences using the Azure Pricing Calculator - Confirm with application teams whether brief downtime for resizing is acceptable - Review whether the original SKU selection is still aligned with performance and cost objectives - Consider that some older series may have limited regional availability or eventual deprecation timelines ## How to fix 5 ways to remove the waste. - Evaluate alternative VM versions (e.g., v5, v6, or v7) within the same family to identify better cost/performance options - Plan and schedule VM resizing during maintenance windows to avoid unplanned downtime - Coordinate with application owners to validate compatibility and risk tolerance - Periodically audit VM fleet for outdated versions as part of cost governance - Prioritize migrations from significantly outdated series (e.g., v3 to v5 or later) for maximum benefit ## Documentation Vendor references for pricing and configuration. - [Virtual machine sizes overview learn.microsoft.com](https://learn.microsoft.com/en-us/azure/virtual-machines/sizes/overview) - [Linux Virtual Machines Pricing azure.microsoft.com](https://azure.microsoft.com/en-us/pricing/details/virtual-machines/linux/) - [Resize a virtual machine learn.microsoft.com](https://learn.microsoft.com/en-us/azure/virtual-machines/sizes/resize-vm) ## Related inefficiencies [Browse the library](https://www.pointfive.co/efficiency-hub) - Azure Virtual Machines CER-0289 ### [Underutilized Azure Savings Plan Due to Overly Narrow Scope](https://www.pointfive.co/efficiency-hub/inefficiencies/underutilized-azure-savings-plan-due-to-overly-narrow-scope) An Azure Savings Plan is scoped too narrowly relative to where eligible compute usage actually runs. When usage is spread across multiple subscriptions or fluctuates significantly (for example, development and test workloads that are... Compute - Azure Virtual Machines CER-0240 ### [Azure Hybrid Benefit Not Enabled on Virtual Machines](https://www.pointfive.co/efficiency-hub/inefficiencies/azure-hybrid-benefit-not-enabled-on-virtual-machines-a8f4b) Many organizations purchase Software Assurance or subscription-based Windows and SQL Server licenses that entitle them to use Azure Hybrid Benefit. However, if the setting is not applied on eligible resources, Azure continues charging... Compute - Azure Virtual Machines CER-0104 ### [Suboptimal Architecture Selection for Azure Virtual Machines](https://www.pointfive.co/efficiency-hub/inefficiencies/suboptimal-architecture-selection-for-azure-virtual-machines) Azure offers x86-64 VMs (Intel and AMD) and Arm64 VMs (Ampere Altra and Azure Cobalt 100), but default provisioning often leans toward Intel-based SKUs due to inertia or pre-configured templates. AMD and ARM alternatives offer lower list... Compute --- Source: the public page above. Product screenshots and illustrative interfaces are examples, not live customer data.