I really like the Azure Capacity Extender feature. However, we have now noticed something that I did not expect. If Autoscale cannot provision VMs with the SKU configured in Autoscale when they are started or deployed, then an alternative SKU is used.
Unfortunately, this SKU is then retained. Even if the pool is re-imaged, you would have to manually select the SKU that is configured in Autoscale (it might also be helpful here to be able to simply use a checkbox to indicate that you want to use the SKU from Autoscale).
I would like Autoscale to regularly check whether the VM can be started with the configured SKU when it starts up, so that the planned SKU is used again, for which you may also have reservations or saving plans.
Perhaps Advisor could also create a report listing pools and then the hosts where there are configuration drifts from the configuration (VM SKU, Disk SKU).
Comments (0 comments)