My customers are asking for improvements in the authentication of the WVD App

Copper Contributor

My customers are asking for improvements in the authentication of the WVD App

The current WVD App stores authentication information for the time specified in the Conditional Access(in my case : 1 hour), even if you shut down the app or reboot your PC once it is authenticated

My customers want the credential removed when the WVD app is closed

Because they want to use the WVD app on a public PC, so they think that maintaining the credential for an hour with conditional access can cause serious security problems

After searching several documents, I found that the only way to control the cookie values of the tokens stored in the app is only the app




"Once an application issues its own session token, access to the application is governed by the application's session. At this point, the user is affected by only the authorization policies that the application is aware of.

The authorization policies of Azure AD are reevaluated as often as the application sends the user back to Azure AD. Reevaluation usually happens silently, though the frequency depends on how the application is configured. It's possible
that the app may never send the user back to Azure AD as long as the session token is valid.

For a session token to be revoked, the application must revoke access based on its own authorization policies. Azure AD can't directly revoke a session token issued by an application"


Is it possible to change the WVD app to delete information about credential when it is closed or "unsubscribe"?


And my customers have one more requirement

Citrix and VMware Horizon View that is our competitor offer the option for end users can reboot VM by themselves

This is a very convenient way for end users to solve these problems most easily if a simple problem occurs in the VM

By adding the reboot option in the WVD app, it seems that simple issues in VM can be solved very easy by end users.


Thank you

2 Replies
Are you deploying Windows 10 multi-session VMs as pooled hosts? Allowing end users to reboot those is obviously not a good idea. I haven't played with WVD using personal hosts and non-multi-session Win10. Are you saying end users can't reboot in that scenario either?
For the reboot issue, if the user is assigned to a personal desktop and given the right permissions, they should be able to reboot the VM from within the session. We don't currently have an option in the client to remotely reboot the PC without being connected to it. And as David mentioned, you don't generally want users rebooting multi-session VMs.

For the credentials, the client doesn't save the credentials, it's standard behavior for Azure AD. We are working on an option to prompt for credentials every time which may help with this. Otherwise, when the signs out of the subscription, it should clear the user as expected. If they are using a public device, they really should be signing out.