AVD scaling plans are missing some basic feature and are restricted to a single day schedules. I'm missing: - option to do a dry run to see what would happen if I enable it - option for several ...
I'd like to upvote the exclusion tag part brought up by the OP. Why can't drain mode be used as the parameter used to determine if a session host should be included in the scaling logic or not? Having to put a tag in manually and the drain mode option often leads to issues.
We are trying to deal with this using pipelines to set tagging and drain mode for VMs for patching Cycles / when a session host needs maintenance but I can't help feel it would be a lot cleaner if existing options were used for the scaling logic.
Thanks,