On the 30th of April the Spring Update Release of Windows Virtual Desktop (WVD) entered Public Preview. This means anyone can go to the Azure Portal and deploy an WVD Workspace and test the new capability.

Video Walk-Through:


Resource Provider Registration:

As WVD is now an ARM object you need to register the Windows Virtual Desktop ARM Resource Provider. This enables you to interact with the service that orchestrates WVD within the ARM service.

  • The first seep is perform the Microsoft.DesktopVirtualization resource provider registration
  • So to start, in your subscription go to the Subscription blade
  • Once in here on the left in the Settings section select Resource Providers
  • In the search bar, type “desktop” and it will show the “Microsoft.DesktopVirtualization” resource provider. This is the WVD ARM Resource Provider.
  • Click on it and then select Register.
  • Now you can interact with WVD from the Azure portal.
  • Now we are done with the pre-steps. We can now start with the enrolment process.

Create your host pool

  • Within the Azure portal search for “Windows Virtual Desktop” which will then open and look like below. This is the WVD HUB.
  • On the basics tab the only change is that if you select the “Personal” Host pool type you can select the Direct Assignment type, this was only possible via PowerShell previously.
  • Choose your subscriptionmetadata location and host pool properties

Click on Next: Virtual Machines

Note: Metadata locations are only active in the USA at the moment. Europe will be added soon. You can deploy continue deploying while having the metadata in the US (e.g. East US 2) and deploying your virtual desktops in West Europe. Make sure that your Managed Imaged is deployed in the same region as the Workspace/metadata. 
  • First click on Yes
  • Give in the VM details –select the size and image for your enrolment 
Note: Session hostnames cannot exceed 10 characters due to the auto-count prefix that comes extra.
  • Provide the properties for your Azure Virtual Network to join your session hosts in.

Administrator account

  • Enter in a service account to join your session hosts to your AD (Kerberos – ADDS) domain

Create the Workspace

The Workspace is the new name for tenant. We can now create this directly do this in the Azure Portal instead of using PowerShell before!

  • Click on Yes and Create new
  • Give in a name for your Workspace (tenant)
  • Click on Ok
  • Click on Review + Create

Start the enrolment

  • Review your settings – click on Create to start the deployment

Install the Windows Virtual Desktop Client

To run your Windows Virtual Desktop – Full Desktops or RemoteApps directly from the client and/or start menu, you must install the WVD Client.

Download the WVD client here: http://aka.ms/wvd/clients/windows

  • Start the WVD Client – Desktop app
  • Enter user that has a desktop or apps applied.
  • Click on Next
  • Enter your credentials
  • Your Desktops are ready to use!

Use the HTML5 Web portal

WVD can be accessed without a client or agent from a web browser, which can be beneficial when you need to do some work without having your own device with you.

Bonus Content:

Some extra information regarding client supports; Windows Virtual Desktop supports the following clients as of today.

This URL goes directly to the official Microsoft download page to download the WVD client.

  • Windows 10
  • Windows 7
  • Android
  • Chromebook*
  • Samsung DeX
  • HTML5 Web client on Windows, macOS and Linux
  • Linux SDK – zero /thinclients (via IGEL Next-gen OS)
  • Which basically means every device is supported with a HTML5 browser installed.

See here a comprehensive troubleshooting overview and what to do when for feedback and support!


I hope the information provided was helpful.

For a complete guide please refer Christiaan Brinkhoff‘s blog here


Notify of
1 Comment
Inline Feedbacks
View all comments

[…] Step-by-Step: WVD (ARM) Session Host Deployment in Azure Portal […]