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.

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.

add true autoscaling like vm scaleset which will add host in hostpool if all session hosts are full with sessions or cpu/ram is full and remove session host if its not used or dont have sessions. also consider minimum / max session host count for each hostpool while scaling up/down.

whatever WVD autoscaling runbook we have on github is actually auto shutdown/start during peak / non-peak hours which is not true auto scaling.

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

As a bank, we have a concern of data leak when we allow user to use WVD to connect to on-prem server/services. We need to have the ability to:
- Allow copying data from user's endpoint (laptop, PC) to WVD
- Block copying data from user's endpoint (laptop, PC) to WVD
- Allow copying data from WVD to user's endpoint (laptop, PC)
- Block copying data from WVD to user's endpoint (laptop, PC)

Today if we allow or block, it will be bi-direction, which is not sufficient to address security risk: it could be either too loosely, or too strictly.

In the contact center scenario, the agent supervisor often has to monitor the service and help the agents by viewing the agent's screen. This functionality could be available to a user with a profile as a supervisor and not to the machine admin.
The WVD could have a functionality like that where teh Supervisor type the agente ID and connect to agente session to help or whatch the screen.

We use some Azure Automation to allow the users to Self Service their Logoff when application freeze the WVD session.

For WVD classic it was this command: invoke-RdsUserSessionLogoff and it worked fine.

For WVDv2 (Spring Update) it is this command: Remove-AzWvdUserSession

And it fails horribly because we make it a best practice to put a delete lock on the Resource Groups.

So please make "Remove-AzWvdUserSession" work when a Delete Lock is in place, or rename the command to invoke-AzWvdUserSessionLogoff.

Thank you very much!

Remove-AzWvdUserSession

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.

When using either a WVD Desktop or App, Teams is using the System Time instead of the user's time zone when posting conversations. I can see the clock on a desktop and that matches my time zone. When I post a conversation, Teams is using the System Time of the server which is default UTC.

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.

What are the plans for supporting MSIX app attach on windows server. So far all I found was about windows 10 ent or multi session. MSIX is available on WS why not MSIX app attach.

Management of WVD via Intune and AAD, without on-prem AD requirement.

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?

Currently, if you want to discover who is currently connected to a hostpool, you have to troll through each and every host in the hostpool to gather this info. The hostpool summary tells you how many users are connected - can we make this user count something we can drill into to list all users

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.

Seems like a straightforward ask that we be able to either configure a default feed (already possible with on-prem RDS) at time of install or through a command like parameter that can be passed to the MSRDCW.exe.

As a previous user mentioned, we need a more seamless way to deploy this functionally rather than asking users to perform “one more login.”