Share via

Excluding VM Application version from "latest" does not work.

Ed Hanway 0 Reputation points
2026-03-05T23:11:16.5666667+00:00

If a VM scale set is configured to install a VM Application version "latest" then the version selected will always be the latest deployed (or highest version number), even if that version was marked to be excluded from "latest" and an earlier version is correctly shown as "latest" in the Azure portal. Is that not working as designed?

Azure Virtual Machine Scale Sets
Azure Virtual Machine Scale Sets

Azure compute resources that are used to create and manage groups of heterogeneous load-balanced virtual machines.

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Nikhil Duserla 9,685 Reputation points Microsoft External Staff Moderator
    2026-03-11T07:32:17.53+00:00

    Hello

    Firstly, could you please provide a brief description of the issue you are experiencing? It would be helpful if you could include clear screenshots/snips and any error messages, as this will help us better understand the exact problem you are facing.

    Additionally, if you are trying to deploy Azure Virtual Machine Scale Sets (VMSS) with the latest configuration, you can refer to the following documentation link-https://learn.microsoft.com/en-us/azure/virtual-machine-scale-sets/flexible-virtual-machine-scale-sets-portal.

    It provides detailed information about VMSS and step-by-step guidance on how to deploy it.

    Also, please note that Azure Spot is an available feature that allows you to use unused Azure capacity at a discounted price- https://learn.microsoft.com/en-us/azure/virtual-machines/spot-vms.

    However, workloads running on Azure Spot should be able to tolerate interruptions or infrastructure reclamation, as Azure may reclaim the capacity when it is needed elsewhere.

    Using VM Scale Sets, you can automatically scale out (increase instances) or scale in (decrease instances) depending on your application demand and usage patterns.

    0 comments
  2. Jilakara Hemalatha 11,515 Reputation points Microsoft External Staff Moderator
    2026-03-06T00:06:22.3033333+00:00

    Hello

    Thank you for reaching out. We are currently reviewing the behavior and would appreciate a few additional details to better understand the scenario.

    Could you please help confirm the following:

    What is the exact VM Application version that gets installed on the VMSS instances?

    Is the VM Scale Set using Uniform or Flexible orchestration mode?

    Was the VM Application version marked excludeFromLatest = true before or after the VM Scale Set was created or scaled out?

    Can you confirm that the VMSS configuration references the application using "version": "latest"?

    What application versions currently exist in the gallery, and which version has Exclude from latest enabled?

    If you deploy a new VM Scale Set referencing "latest", does it still install the excluded version?

    How was the VM Scale Set deployed (Azure Portal, ARM/Bicep template, Terraform, CLI, PowerShell, etc.)?

    These details will help us determine whether the behavior is expected or if further investigation is required.

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.