Logging into the portal and then again when connecting is a pain for users. Please enable true SSO.

Operating from South Africa I created a test VM on Windows Virtual Desktop and the response was not great considering that it was deployed it in South Africa North DC. The best RTT was measured at 226 ms whereby 150 ms or less is required for an acceptable experience. This was mainly due to the session controller service being managed from a US DC.

We will take 20 steps backwards by creating an ADDS or AD server just to in the end utilize our Azure AD authentication.

WVD should support native Azure AD join and authentication.

Right know you cant deploy both desktop and apps to an AppGroup and you cant assign two app groups in the same host pool to a user.

Sometimes a user might need to use the web client on a public computer and login with the full desktop but on their private computer they have the remote app set up via the desktop client.

We dont want to setup extra servers for this...

It would be beneficial to have the option to add both traditional domain-joined clients as well as Azure AD-joined devices into Windows Virtual Desktop. I think of a scenario with two separate host pools (one for each client type) where applications that may behave differently in these environments can be targeted to different groups of users.

Currently invited guest users from other Azure AD tenants cannot access WVD in the "inviting" AAD. We are forced to create new "twin" user accounts.

A lot of the Management of WVD is done in powershell and multiple different nodes in Azure portal. Add a new GUI node in azure portal for VWD management

Instead of providing another portal to end-users to connect to the published virtual clients please integrate them into the already existing myapps.microsoft.com portal.

When creating a new WVD host pool, there is an option to provide the default desktop users. Can you change it so that you can enter an Azure AD or AD group as well please, as it will make it easier to add and remove users who can log onto the RDSH after the deployment rather than using PowerShell?

Hi Team,

As per: https://techcommunity.microsoft.com/t5/Windows-Virtual-Desktop/AAD-Reauthentication-MFA-enforcement/m-p/775217

Is there a way to enforce MFA each time a user connects to WVD?

We have 3rd party users who are to connect to our WVD environment and we need to enforce MFA.

Optionally can we block off the client and force users to use a HTML5 compatible browser?

With Microsoft's interest in going passwordless, and with the new public preview for FIDO2 key support, it would make sense to allow users to login to these virtual desktops and remote apps using the same passwordless solutions. Seems counterintuitive to test going passwordless, but then requiring a password using password hash sync for these vms.

Currently the WVD deployment mechanism is via ARM template. This requires on big arm template to be submitted. If there are errors we need to wait 30+ to figure out and then try again

WVD seems to be sending all traffic to US-East. This is plain stupid and not acceptable. The gateway and mgmt should be in the local region where my desktops are hosted.

Currently, the Web Client has an URL "https://rdweb.wvd.microsoft.com". Can we have an option to change this URL to our domain?

Currently we have to setup an additional High-Available VM cluster if we want the profile containers to be available in a SLA approved way whenn we use file shares.

It would be great if we could use Azure Storage to host this fileshare instead of an additional (set of ) vm(s).

Be able to apply conditional access policies at pool level rather than to the whole of Virual Desktop

WVD is a great use case for NV series with their GPUs. However, these aren't available everywhere, and even when available some regions lag far behind others. For instance, NV is not available in UK West; NVsv3 or NVs v4 not available in UK South. Also the NVIDIA based NV series VMs are still using M60 GPUs (Maxwell based Quadro) , which are 3-4 years behind the current Turing based Quadro GPUs.