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.

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

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.

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?

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

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

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

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.

The current mgmt UI (website ux) allow a few admin actions to be performed, however it is inadequate to for Service Desk/Operation teams who only requires limited actions as Remote Shadowing, Viewing Session on Pools, Disconnect or Terminate Sessions or Processes. It would be usefull to implement a RBAC model for this portal/management UI.

add the possibility to configure "Connection Authorization Policies" based on user or group membership.

I am aware that RD Client is in preview for MacOS but just to ensure that you know....
I am not able to launch WVD ressources from RD Client although I can subscribe and see my resources in the client.

I'm using Remote Desktop Client 10.3.3

Hey there!

Diagnostics app and management app could be included in functionality with Windows Admin Center as extension - so we don't actually have to go around deploying two complex apps that look and feel alike much loved Windows Admin Center

There are a number of custom rdp properties which can be set via PowerShell as directed here (https://docs.microsoft.com/en-us/windows-server/remote/remote-desktop-services/clients/rdp-files) but the property showconnectionbar:i:0 is not available. We can set it via PowerShell in Azure but it does not push down to the client. For thin client scenarios, we would prefer the bar to be hidden from users.

When I can use WVD at my iSO client?

Allowing Linux Host on WVD would enable Linux users in various industries to take advantage of similar capabilities.

Many Canadian nonprofits and government users require that their data be stored in Canadian data centres. WVD data will be hosted in the US which means those organizations cannot use WVD. When will WVD data be stored in Canada (i.e., how many months after General Availability)?