AVD Scaling plans are too simplistic

AVD Scaling plans are too simplistic
0

Upvotes

Upvote

 Jan 27 2022
2 Comments (2 New)
Tell us more

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 messages in different intervals to the users about the shutdown

 - option to do only some of the tasks (for example: only notify and shutdown for personal desktops and only scale up for hostpools running over the weekend for after hour employees)
 - exclusion tag is applied to VM while drain mode is applied to session host object in host pool - this is not a good design and will lead to people forgetting about one or the other when doing maintenance and having to set the flags in two different places

 - plan is restricted to a single day, I can't start hostpool of Friday, scale over weekend and shutdown on Monday
 - option to ramp down at the end of the day and scale up to a smaller threshold over night

Comments
Microsoft

Hi @enecoTD , thank you for your feedback! I have a few follow up questions:

- For the option to do a dry run to see what would happen if I enable it, how would this work? Could you just enable Autoscale in a validation host pool to see that it works as expected before enabling it in a production environment?

 - For the option to send several messages in different intervals to the users about the shutdown, what is the use case for this?

 - For the option to ramp down at the end of the day and scale up to a smaller threshold over night, how is this different from the ramp down and off peak hour configuration flexibility that scaling plans afford today?

Microsoft
Status changed to: Tell us more