Windows Virtual Desktop Cons

Copper Contributor



I think the potential is incredibly high for this Windows Virtual Desktop (WVD) solution, and I'm looking forward to improvements and new features as they are released. There doesn't appear to be a UserVoice forum set up for reporting issues to Microsoft. I wanted to summarize some of the issues I've found, or read about that would make production implementation difficult on the short term.

- In multi-windows VD environments, if a user is disconnected they aren't necessarily reconnected to original VD (RD session broker).

- With new Microsoft Remote Desktop program, Azure MFA is only required when first subscribing to a feed.


- Azure MFA can be bypassed with Microsoft Remote Desktop Preview app (v 10.1.1098.0). (Subscribe to feed


- No apparent way to host WVD VMs so they are only accessible from a corporate network.


- Can't control resolution or monitor spanning in new Microsoft Remote Desktop client (v


- Printer redirection through web client doesn't work as well as through the Remote Desktop client.


- Initial connection to WVDs frequently fails or is slow to connect. (Noticed during afternoon business hours, US Eastern time zone).


I hope this feedback gets to resources at Microsoft that can address them. At this point, remote desktop services on Windows Server still offers the most flexibility in deployments. Thank you!

2 Replies

@5alarm603: Thank you for your detailed feedback. We will be reviewing it within the team. 


For any future features suggestion we are working on getting UserVoice being available shortly.

@5alarm603and Microsoft


We are testing with WVD since today and are really looking forward to using this. It would reduce or on-premises hardware requirements while at the same time simplifying the whole RDP gateway concept. That being said, I would also love to give some feedback and I was looking for a uservoice as well. It would be great if the team could create a uservoice.


Some observations I made after testing with it just a short while:


1) When doing the role assignment ( we ran into an error if part of the deployment was done by a different admin user.  In the end we solved this by removing the RdsTenant created by the other user and creating it again by the user that would do the role assignment.  That seems to be weird as we would expect these tenants to be AzureAD-wide. The user performing the operation should not affect the RdsTenant creation (as long as he/she has the necessary rights).


2) The word 'tenant' can be confusing in the documentation (AzureAD/Office 365 tenant vs RDS).


3) The new Remote Desktop client does not seem to support Single Sign-on in Windows 10 when subscribing to the feed. In my case I had to enter my UPN, choose Work/School or Personal account and enter the password although I have SSO for everything else active (Windows 10 1903, Azure AD registered and domain joined device).  SSO would be so much more elegant.


4) When connecting to the WVD with a client with Windows Hello enabled in Key Trust mode, the system does not allow me to log in.  RDP should either do SSO (preferred) or support Windows Hello (key trust without ADFS). This problem is not specific to WVD as it is also present when you connect to a classic on-prem RDP deployment. However, with the new client I kind of hoped that support for Windows Hello would be included. It was a bit of disappointment it was (not yet) supported.


But, as indicated above, WVD seems to be very promising and we keep testing it in the hope to roll it out soon.