When building new Azure Virtual Desktop hosts via the AVD portal, if you select an OS disk size for the host that is anything other than the default 128GB, the host is provisioned with a 128GB disk and then resized/upgraded as part of the VM's build process. The problem with this is that the OS volume is still the default 128GB and needs to be manually extended after the host has been built.   This detracts from the otherwise impressively polished process of provisioning AVD hosts in the Azure portal, where it's clear a lot of automation already takes place as the VM is created and set up for AVD.   I have not been able to find mention of the need to extend the OS Volume after provisioning in the Azure Virtual Desktop documentation, nor was it clear that this would be required when selecting 256GB OS Disk size during host creation.   If the host were created with a 256GB OS Disk from the beginning (rather than upsizing) I anticipate this would solve the need to extend the OS volume manually afterward. Alternatively, if its possible to automate extending the OS volume to utilise the full disk size after it has been resized that would also address the problem ... View more

Is it possible for you to add a group policy to forbid end users using legacy Remote Desktop client?  ... View more

The new preview version of the AVD insights configuration workbook for the AMA agent only recognizes data collection rules that are created in a resource group called "AzureMonitor-DataCollectionRules" and does not recognize any DCR that was created elsewhere.   We would like to have the option to use other resource groups and DCR. Hope this can be adjusted during the preview. ... View more

It would be nice if we could get deep links to specific AVD sessions to quickly open their machines on the AVD web client or the desktop app. The deep links should be available via the web client's view (copy link button), be available via the RDS feed, or be constructed easily with workspace/hostpool names in the feed. ... View more

When session host VMs are manually placed into drain mode, update the available capacity of the host pool to reflect this. This would then allow autoscale to intelligently power on additional VMs to compensate for those that have been made unavailable for new sessions. ... View more

A few months back the column labelled "Active Sessions" in the AVD admin console changed to show total session per session host rather when you drill into the host pool and list the session hosts. See below examples of current inconsistent data at present   This request/idea is   1) to fix the active session column to show the active session count again   2) improve the session host list to include three columns to show "total sessions on host", "active sessions on host" and "disconnected sessions on host" to mirror the data available at host pool summary level - all of those are useful bits of information in their own right to an admin in different circumstances when looking at the session usage/state per host for example when looking at load levels and when initiating maintenance activities and diagnosing connectivity issues like are a very high % of session disconnected on a given host when they aren't on others say.     Example of current Web UI   Host pool overview screen shows accross the entire host pool "Total sessions", "Active sessions" and "Disconnected sessions"     When you then click onto the "Total machines" count or "Session hosts" in the left menu the list of session hosts in the host pool shows a column titled "Active sessions" has a count of what is "Total sessions" per the definition on the previous screen rather than the "Active sessions" per host i.e. the aggregate of active and disconnected sessions.       If you then drill down into a given host in the example above there is 1 session that is "active" and 6 that are "disconnected"       ... View more