Hello @Nazeer, Shalomon ,
Exclusion tags are used to tell the autoscale to ignore specific VMs during scaling operations.
When you apply an exclusion tag to a VM, autoscale stops managing that VM (it won’t deallocate or start it in future cycles).
However, applying the tag does NOT automatically start a VM that is currently deallocated.
- Autoscale does not proactively power on VMs when you add the tag.
- The tag only affects future scaling decisions
As per your description, this is what you can do: If the VM is already deallocated, you must manually start it after applying the exclusion tag. Once powered on, autoscale will leave it running because the tag excludes it from further scaling actions.
Let me know if it helped to clarify your query!!