Marcel That's me: Marcel

Azure Windows Virtual Desktop - Spring Release / Spring Update with WVDAdmin

Azure Windows Virtual Desktop - Spring Release / Spring Update with WVDAdmin

Azure Windows Virtual Desktop - Spring Release / Spring Update goes public today. I’m tremendously happy about that while this is the next big step that we have eagerly awaited.

The spring release gives us some feature and changes that make it even easier to deploy apps and desktops to users:

  • Add groups instead of users to desktops and apps
  • Full integration of the administration of WVD/AVD in the Azure Portal
  • Using a native ARM deployment instead of the WVD/AVD tenant API
  • Linking app groups and desktops into workspaces
  • and a lot of more things

Even the administration of WVD/AVD was missing before. This was one reason to build WVDAdmin. I was often asked in the past if WVDAdmin will be unnecessary after the spring release of WVD. My answer: Sure, for the administration, WVDAdmin will not be that important anymore, but some features still add value. That’s why I decided months ago to develop WVDAdmin further and also prepare it for the “Spring Release”. So I am proud to announce that WVDAdmin is ready for the Spring Release starting with the already available version 1.5.

To enable the Spring Release feature set a registry key (the current version will have this enabled by default):


(Reg_DWord) "FeatureSet" = 1


First, register the new service provide Microsoft.DesktopVirtualization on your Azure subscription (one-time process). You must be owner of this subscription to do this. Go to your subscription -> Resource providers -> search for “Microsoft.DesktopVirtualization” and click register:


If you restart WVDAdmin you will see the new note “WVD V2” which displays your resources in the Spring Release. Please make sure that your service principal has the right permission to create and administrate your resources (the sp needs owner permission to the resource group containing your host pool, app groups, … to assign users and groups).


But what can you do with WVDAdmin compared to the portal integration? You can (e.g.):

  • Administrate all resources with a Windows GUI
  • Create “golden images” from template/master VMs
  • Rollout several session hosts into differents host pools (in both WVD/AVD releases)
  • Re-use you created WVDAdmin images without any change
  • Higher flexibility rolling out new session hosts in different ways (you can use different VMSizes and images in one host pool)
  • Easy to use user administration to send messages, logoff, disconnect or shadowing users over the full environment (filterable)

From an architectural perspective, the “Spring Update” is really close to the previews release. But there are a few differences:

  • WVD tenant and tenant groups are no longer used
  • “Workspaces” summarize multiple apps and desktop groups. These apps and desktops are shown in the client grouped by workspaces
  • All resources like host pools, app groups are ARM resources in the Azure portal.
  • App groups must be in the same region as the host pools
  • A Workspace can group apps and desktop groups in the same region
  • The regions of the session hosts are completely independent of the regions of the host pools (which is great)
  • Today you have only a few regions to roll out host pools and workspaces (which is not so important because you can rollout the session hosts in any region)
  • And you can assign groups to apps and desktops


Check out my video rolling out session hosts from an existing WVD/AVD image into the spring update (sorry for the bad sound - I will change this later):

More details and download: WVDAdmin

And get additional information from Freek Berson

Official announcement: