In this series on Windows Virtual Desktop (WVD), we have provisioned a WVD tenant in Azure and added a host pool. Now all that’s left to do is connect to your published desktop or apps. Microsoft provides two ways to connect to a WVD host pool. You can either download and install the WVD Remote Desktop client or use the web client. WVD doesn’t support connections from RemoteApp and Desktop Connections (RADC) or Remote Desktop Connection (MSTSC).
Let’s start by trying to connect to a host pool from an HTML5-compatible browser. Microsoft says that in principle, any HTML5-capable browser should work with WVD, but official support is provided only for Microsoft Edge, Internet Explorer, Apple Safari, Mozilla Firefox, and Google Chrome.
Open the Windows Virtual Desktop web client using this link. If you are already signed in to Azure Active Directory (AD) with an account that doesn’t have access to the host pool, you may need to sign out before opening the web client. Otherwise, enter an Azure AD account with permission to access the host pool when prompted.
Once you have access to the client in the browser window, you should see any published desktops and applications. In my host pool, I just have a published desktop.
You should now have access to the desktop or app in the browser window. If you have access to a desktop, notice that unlike on a Windows Server desktop, you can use Microsoft Edge and other Windows 10 features. Also see in the ‘About Windows’ (winver) dialog that we are running Windows 10 Enterprise for Virtual Desktops.
Alternatively, you can connect to a desktop or app using the local client.
You should now have access to the desktop or app in a separate window.
That is it for this introductory series on Windows Virtual Desktop. In the future, I hope to look at some of the more advanced configuration options.