@Jasmer you would just deploy a new Windows Virtual Desktop like you did the original and add it to the same host pool. it will be available to all users that are already in that host pool. For example I have created three different Windows Virtual Desktops using the Azure Portal, each one of them is in the same host pool because at the start of the tutorial, I simply typed the same host pool name that I created in PowerShell.
After deploying a hostpool, can we extend or add more VDIs in that pool later on?
I could achieve that in the following way. Add Session Host: Install WVD Agent and WVD Agent Boot Loader on the target VM. In addition, Token of HostPool is required at the time of Boot Loader installation.
Currently, settings can not be made in Portal, and it seems to incorporate scripts into the task scheduler of session host. You can, of course, use Azure Automation(Hybrid Runbook Worker) instead of the task scheduler, There is no big difference between them.