Ans: This might be due to the upgrade policy set on the VMSS. You can read more about it here. You can use the documentation there to update the virtual machine instance to latest model. You can also switch the upgrade policy. For example, to upgrade the policy, followig Az CLI command can be used:
az vmss update --set upgradePolicy.mode=Automatic -g <resource group name> -n <vmss name>
Files
AzureVmssDeploymentV0
Folders and files
Name | Name | Last commit date | ||
---|---|---|---|---|
parent directory.. | ||||