We have some graphical applications that works well when used directly with RDP Gateway, or with RDP over VPN connexion, but the same application lag and is almost unusable using WVD, because traffic goes trough gateways in US. SO at the end we have to stop using WVD and uses VMs with traditional RDS architecture (Gateway, Session Broker, Licenses server, etc.)

We would like to deploy the subscriptioninfo in the RD Client automatically for our AAD-Intune administered devices. For example with an answerfile/parameters together with the install-file as we deploy it, registry-settings or a Configuration Profile in Intune or OMA-URI.

Our users are used to no-config to connect to applications in other RDP and Citrix environments. This is already possible in the "RemoteApp and Desktop Connections", but this is not supported for WVD.

It's weird how West Europe is so far behind on the WVD implementation. That should probably be the number one priority for WVD - currently we have been waiting a full year to be able to use this feature since we want to eliminate the old RDS server.

I've been this logic app to scale up/down VMs

https://github.com/Azure/RDS-Templates/tree/master/wvd-templates/wvd-scaling-script

Although i can't figure it out how to scale up/down based on concurrent number of users connected, although can see time zone

could you help here?

Rgds,
Aj

We already have a limited number of characters for the hostname, why waste one with a mandatory hyphen. If a customer still requires the hyphen, they can still add it to the end of their hostname prefix

Currently SSO (with for example Office 365) only works with a Domain Controller VM and Azure AD Connect. It would be great if we could also enable this when using Azure Active Directory Domain Services, so we don't have to manage a (set of) Domain Controller VMs.

support windows 10 multi-session for professional edition for organization using m365 business premium license

Create single session Marketplace Windows 10 Enterprise + Office 365 Pro Plus offerings

Make MSIX app attach available outside of WVD and Azure.

When deploying new session hosts with new image versions from a shared image gallery, it would be good to see the image version next to the session host

i am in Cambodia.
i can't find my region in the drop down list.
the below is my country address on google map.

"https://goo.gl/maps/BhQ2cfaPR6Rs2quk9"

Printing to a PDF is a big no-no for us as that could save confidential documents to the local PC that the user is using to access their session hosts via a web browser. Is there a plan to have a plugin for browsers to allow printer redirection?

At the moment, we publish web apps by opening new browser windows or tabs to specific URLs. I propose that some sort of integration/plugin could be supported natively in WVD to display these web pages as program windows, without possibility to change URL, or create new tabs.

In summary, something similar to a kiosk mode but without fullscreen.

Please can we have [smalldisk] images for Windows 10 gallery images for Windows Virtual Desktop. When using application deployment tools like App-V or MSIX AppAttach, we do not need huge amounts of space for the OS partition, but the minimum size is currently 128GB with no supported way of shrinking the disks in the portal. We don't really need more than half of that, maybe even a quarter. (expanding a small disk is also easy if we do need more space)

WVD service is not describing how the user connects to the session. For security compliance, we need to know where is the client talking to for control and data traffic (location/region) and restrict the user to connect to a specific country.

This link for latency estimation is misleading because it does not show where the desktop gateway is located and used for our remote users. Our testing shows that some traffic is still going to US even though our users are in South East Asia.
https://azure.microsoft.com/en-us/services/virtual-desktop/assessment/

With the recent announcement about WVD Spring Update, we're wondering when it will become available in Canadian regions ?

Meanwhile we wait the AAD join, would be nice the have a validation check for the DC credentials as many times we had a typo in user or password, so we waited 15 minutes to see a join error. If you could pre-validate those credentials in the final validation step would be a time saver :)

Face recognition the WVD could be integrated with Windows Hello.

WVD runs fantastic on Ephemeral Disks from my experience and can be set to directly from the ARM with a small tweak to the JSON. Would be great to have the option available right out of the marketplace ARM.