Bulk Start/Stop of Azure Virtual Desktop Session Hosts in a Host Pool via Single Trigger
Hi Community, We manage an Azure Virtual Desktop (AVD) host pool with a large number of session hosts (e.g., around 100), and we’re looking for a way to start or stop all session hosts in bulk using a single trigger—preferably via PowerShell or an API. Currently, we use a scheduled script that loops through each VM individually to start or stop them, but this approach doesn't scale well. We’ve noticed that the Azure Portal provides a one-click option to start or stop all session hosts in a host pool, and we’re trying to replicate that behavior programmatically. What We’re Looking For: A PowerShell command or script that can start/stop all session hosts in a host pool without iterating through each VM. If PowerShell doesn’t support this directly, is there an ARM template, Azure CLI command, REST API, or any other method that can be triggered from PowerShell to perform this bulk action? Any official documentation, community guidance, or examples from someone who has achieved this would be greatly appreciated. Goal: To simplify and optimize our automation by using a single command or API call to manage all session hosts in a host pool, rather than looping through each machine individually. Thanks in advance for your help and suggestions!
Proxy Settings when using OMS Agent VM Extension via ARM template
Hi all I'm adding the Monitoring Agent using a VM extension in an ARM template, using the following code. My question is whether it's possible to specify authentication details in the template code so that the agent can authenticate to the proxy server. Is this possible? "properties": { "publisher": "Microsoft.EnterpriseCloud.Monitoring", "type": "MicrosoftMonitoringAgent", "typeHandlerVersion": "1.0", "autoUpgradeMinorVersion": true, "settings": { "workspaceId": "[parameters('omsworkspaceid')]", "proxyUri": "proxy:8080" },AVD Domain Join Errors
Just curious of other people are seeing errors during domain join when creating a new AVD pool in ARM, but when the VM's are checked they were successfully joined. I have seen this several times in the last three months. What it looks like to me is that the template in the ARM tries to perform the join while the new VMs are coming out of Sysprep, throws the error message, then later successfully joins the VMs. The one time I did get into a VM that had this error, I was able from within the VM using a Bastion connection, join the computer to the domain using the same service account credentials I had specified in the ARM.
Where is image: "Microsoft Windows 10 + Office 365 ProPlus"
Where is image: "Microsoft Windows 10 + Office 365 ProPlus" Hi I haven't been to the Market Place for a while and today I was looking for an updated image of W10 21H1 with Office but I can only find one with 21H1... Where has the office image gone? Thanks
