Workspace 365 with Windows Virtual Desktop

In this article we describe how you can use Windows Virtual Desktop directly from Workspace 365. From update V3.9.0 we created a direct integration with Windows Virtual Desktop and Workspace 365, this means that you can start Windows Virtual Desktop apps directly from your Workspace 365.

IMPORTANT: You'll need to add an additional oAuth2 permission to the Workspace 365 Single sing on application, you can do this by following these steps:
  1. Go to with the admin account
  2. Go to Active Directory
  3. Go to App Registrations
  4. Select the Workspace 365 Single Sign-On app
  5. Go to API Permissions
  6. Click Add a permission
  7. Select API's my orginazation uses

  8. Search for Windows Virtual Desktop
  9. Select the API -> Delegated permissions
  10. Check the user_impersonation (Spring 2019 version)
  11. Check the User.Access (ARM 2020 version) 
  12. Click Add permissions
  13. When that's done click the Grant admin consent for ****

When the API permission is added, you can add the Windows Virtual Desktop app(s) to the Workspace 365 environment. 

  1. Go to the app store and select Windows Virtual Desktop:


  2. Fill in the following information:
    • App name, this is the name how the app is represented in the workspace
    • Windows Virtual Desktop version, select which version you use. 
    • Windows Virtual Desktop app name, this should be the exact name like the app name in Windows Virtual Desktop
    • Select the Microsoft remote desktop client, we recommend .rdpw which is the newer client this client can be downloaded here:
    • Now add the to the Workspace and publish it to the desired users.

TIP: Be sure that the user is singed in in the new Microsoft Remote Client.

Microsoft Remote Desktop Client with .rdpw 

When you clicked on a Windows Virtual Desktop App, an .rdp file was downloaded which you had to open and for which files needed to be added to the computer. The new client can instantly open .rdpw files, so you can immediately get started with your Windows Virtual Desktop applications.

You can use .rdpw now, this means we support another file that gets downloaded it will not run from Workspace but from your local Client.

How to set this up within the Workspace

  • Go to the App Store
  • Click on New
  • Click on Windows Virtual Desktop App
  • Fill in the right information and select .rdpw




If you are using .rdp (old client)

IMPORTANT: When opening an app from the Workspace 365 the client PC must be connected to the Windows Virtual Desktop environment. 

This can be done in 2 different ways


  1. Navigate to:
    1. Control Panel\All Control Panel Items\RemoteApp and Desktop Connections. Then Click on the Access RemoteApp and desktops.
  2. Add the following Windows Virtual Desktop Feed URL:
  3. Click Next and sign in with the account which has access to the Windows Virtual Desktop environment

Automating the feed via GPO:

  1. Open the Group Policy Management Editor on the domain controller and create a new GPO.
  2. Go to User Configuration -> Policies -> Administrative Templates -> Windows Components -> Remote Desktop Services -> RemoteApp and Desktop Connections.
  3. Double click the Specify default connection URL key and enable it. Enter the feed URL in the Default Connection URL field.
  4. Click OK.
  5. Roll out your new GPO to your domain.

If that's done your able to open the application directly from the Workspace 365, first time you'll need to fill in your Windows Virtual Desktop credentials, but you can check the "Remember me" option. And you are able to launch the apps directly from Workspace 365. 


  1. Since the latest version of the Remote desktop Client (RemoteDesktop_1.2.1186.0_x64) it looks like it has issues opening the RDPW file directly. This seems to be an bug in the Remote desktop client. We suggest to use the previous version of the Remote desktop Client (RemoteDesktop1.2.1104.0_x64) which can be dowloaded here
  2. Microsoft is working on fixing this issue in an upcoming release of the Remote Desktop Client. We suggest to keep an eye on the release notes of the Windows Desktop Client.