Windows Virtual Desktop Spring Update enters Public Preview
Published Apr 30 2020 09:12 AM 44.1K Views

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. This article discusses the new updates and capabilities in this new release, as well as changes and other items you need to consider when deploying Spring Update WVD deployments.

"Spring Update"

First thing - the name, "Spring Update". WVD is now a first class Azure service (more on that below). Azure does not have versions. It is a platform that gets constant updates continually dropped in. This is the same with WVD. As such this is the set of updates being applied in the Spring. WVD receives many continuous updates, however major changes such as this shift to ARM are bundled into a larger periodical update. Expect future continuous updates to be dropped into platform in the future in a similar manner, with some larger updates getting some kind of seasonal naming.

WVD is now an ARM service

Up to this point WVD has not been an Azure Resource Manager service. But rather the WVD objects have all existed within a separate database. With the Spring Update all WVD objects now are ARM resources in their own right. Azure Resource Manager is the service that sits between the user and the underlying Azure Fabric and is responsible for the provisioning and management of all Azure services. This is achieved by "Resource Providers". Each Azure service has a resource provider i.e. Compute Resource Provider, that ARM can interact with to construct a Virtual Machine for example. More information on ARM is here.

WVD becoming an ARM service has a number of benefits all of its own summarised below:


Azure AD Groups
Up until the Spring Update it was only possible to publish RemoteApps and Desktops to individual users. Now in ARM you can publish these to Azure AD Groups, which is a significant improvement and time saver in its own right.

Azure RBAC for access control
In WVD there are four RDS specific admin roles, that can be applied against the tenant or host pools. This has now been moved into native Azure Role Based Access Control. This can be applied at every single WVD ARM object enabling you to have a full rich delegation model.
Azure Portal Integration
This is a big one for most customers. Prior to the Spring Update the options to manage a WVD tenant was, PowerShell or a simple Management App Service Web App, or a third party tool. The Azure portal was shown a long time back by Scott Manchester but this now goes live, more info below.

Dedicated Scale out capability
Prior to the spring update if you wanted to scale out a host pool you would run the Azure Marketplace deployment or the Github template a second time and reference the existing Resource Group and Host pool. You would specify the number of VM's you wanted to end up in the host pool, i.e. 10. If your host pool had five VM's it will deploy five VM's to make up the difference.  

Now with Spring Update there is a specific option to scale out your host pool - no need to rerun anything, and you just specify how many VM's you want to add, more info below.


Shared Image Gallery

The Host Pool deployment now is fully integrated with Azure Shared Image Gallery SIG is a separate Azure service for the storage of VM image definitions, that includes versioning, which opens the door for monthly (or any cadence) updates to your image. The image has a property called "latest" that allows you to just reference the image definition every time and SIG will supply the latest image version every time seamlessly. Hence you can automate the session host pool deployment to always use your latest build which includes the latest patches, or application updates etc. It also manages the replication of the images to any Azure region around the globe, so that you don't have to, as well as the number of replica's which is important if you require a large number of deployments. The more replica's you have the higher the throughput. SIG is integrated into the Host pool creation process, as well as the expansion process.



WVD Monitoring

Again consumption of monitoring information was via either PowerShell or another Diagnostics App Service Web App. This has now been moved into Log Analytics within the Azure portal natively. Each WVD ARM object can independently be connected to the same or a different Log Analytics Workspace form where you can run Kusto queries or you can integrate with PowerBI to create visual reports

Consent for consuming Azure Active Directory

The very first step in creating a WVD tenant was to consent for the WVD service to use your specific AAD tenant. This was because the WVD service was not a first class Azure citizen. Now that it is, there is no longer a requirement for this consent to happen. However, note that with the consent page you could specify exactly what AAD tenant you wanted to use for user authentication into the WVD service i.e. it could be separate to the AAD tenant that your Azure subscription that you deploy the WVD session hosts into is itself linked to. Now with ARM the AAD tenant that your Azure subscription is the same AAD tenant used to authenticate your users to WVD, as well as provide RBAC controls for your admin users. Hence your selection of an appropriate Azure subscription is more critical as you have slightly less flexibility than before.

Service meta-data storage location

The meta-data, i.e. the data about your deployment or all of the configuration of your overall deployment used to be only stored in the US. Starting with the Spring Update you will be able to select alternative locations staring with additional US regions, then the European geography, and additional locations will also become available over time. This is great for organizations with data sovereignty requirements.

PowerShell support

Prior to the Spring Update there was a RDS specific PowerShell module. This has now been replaced with WVD support being integrated with existing Az module: AzWvd. This is supported in PowerShell Core which runs on .NET Core. E.g. Get-AzWvdWorkspace. To install just run: Install-Module Az.DesktopVirtualization, and then run: Get-Command-Module Az.DesktopVirtualization to get a list of available commands.


 Final consequence of the WVD objects moving to ARM is that they inherit a largely flat hierarchy rather than the top down hierarchy. This is illustrated here:

Some things that need to be considered as part of this change to the ARM object model are:


  • All native WVD objects are fully independent ARM objects. Each will have its one Azure region location, and they can be placed anywhere. They all need to reside within a Resource Group and can be any resource group. However for them to be associated together i.e. having an App Group associated with your Workspace they need to be within the same location (Azure Region). The one exception is the Session Host object. This object is a representation of an Azure Virtual Machine and this can be in any location.
  • The relationship between the old model and the ARM model, is as follows:
    • Most people will have never seen the Tenant Group. The vast majority of customer tenants get automatically deployed into the aptly named "Default Tenant Group". For partners and service providers managing many customer Azure Subscriptions or specifically WVD Workspaces this can be managed by Azure Lighthouse, which is an Azure service that allows them to manage multiple Azure services across multiple customers and tenants.
    • The WVD Tenant was effectively the top level of WVD administration, this directly translates to a WVD Workspace in the ARM model.
    • Host Pools, Session Hosts and AppGroups are largely the same and provide the same capability. However their relationship is displayed in a different manner.
    • To publish applications or desktops to users, they need to be assigned to an "App Group" which in turn needs to be registered to a Workspace. The App Group can be assigned to any Workspace (within the same region), and you can have multiple Workspaces. If the App Group is not registered to a Workspace the applications will not be visible in any of the clients.
  • Whilst the ARM object hierarchy is largely flat there are still dependencies between the objects. Starting from the bottom up:
    • A host pool contains Session Hosts (VM's)
    • Applications groups contain individual Remote Applications or the Full Desktop.
    • Users are assigned to Applications Groups
    • Applications groups are added to a Host Pool
    • Workspaces contain Application groups
    • Users interact with Workspaces via the WVD Clients.
  • Deployment: There are some dependencies to be aware of when creating the above objects
    • When creating a Host pool you can either allow it to create sessions hosts, or not. If you select No you then need to add them manually later. Also you can optionally choose to register the Desktop Application group that gets created by the deployment to a Workspace.
    • When creating an Application Group, a Host pool is the only object required. Actual applications and users can be added now or you can say No and add later.
    • When creating a Workspace nothing is required to be assigned. You can create an empty Workspace and then add Application Groups later.
  • Migration. The Spring Update release will not display non-ARM Tenants, there will be a migration PowerShell capabilty that will enable the migration of the existing WVD objects into the ARM model.

Azure Portal

This is the most visual of updates and what most customers and partners ask me about. So let's take a look at the new user experience, and create all of the WVD ARM objects.

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.


  1. So to start, in your subscription go to the Subscription blade:
  2. Once in here on the left in the Settings section select Resource Providers:
  3. In the search bar, type "desktop" and it will show the "Microsoft.DesktopVirtualization" resource provider. This is the WVD ARM Resource Provider.
  4. Click on it and then select Register.
  5. Once registered it will appear alongside all of the other registered resource providers.
    Now you can interact with WVD from the Azure portal.
  6. Within the Azure portal search for "Windows Virtual Desktop" which will then open and look like below. This is the WVD HUB.

Before we create anything, I have already created a Workspace, Host Pool and Application Groups. It's important to see that when you create hew Host pools and Application Groups you can register them with existing objects, or choose not to.


This is the Host Pool View:




This is the Application Groups View:

This is the Workspaces View:

Just to demonstrate that all of these ARM objects also reside within a Resource Group, in my case one single Resource Group, but you can place them in any Resource Group.




If you go back to the Overview tab the UI suggests creating a host pool first. However you could create a Workspace first if you wanted to if you wanted to follow the previous top down hierarchy.


Creating the host pool

If you have deployed a host pool prior to the Spring Update you will recognize most of the questions that need to be answered as well as the format.


  1. 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.
  2. On the VM details you now have the option not to add virtual machines. This is if you already have session host VM's that you are going to join to this host pool. 
    If you select yes it will show the standard questions that needed to be completed for new VM's.
  3. Next is the Workspace Tab.
    Again you have two options here. In Register desktop app group, if you select No it does just that. However if you select yes you can register the default Desktop Application Group, which is the default group that publishes a published desktop, either to an existing Workspace or you can create a new one here.
    In my case I am adding it to my existing Workspace.
  4. You can then optionally add Tags, then Review and Create
    This will now create Session Hosts, do the AD Domain Join, install the WVD agents create the new host pool, add these session host VM's to this new host pool, create the default Desktop Application Group which is named "HostPoolName"-DAG. This publishes the desktop, although it doesn't publish to any users as it would previously at this point.
  5. So to assign users or group go to the host pool and then go to "Assignments" then click on Add and you can select a user or group using the standard AAD picker:



Creating the Application Group

So we have a new host pool with a Desktop Application Group published to some users, lets now create a group to present actual applications directly - what's known as a RemoteApp Group.

  1. Go to the Application groups part of the WVD Hub, and click on Add
  2. Select a Resource Group, then select your Host pool, and then in Application group type select RemoteApp and give this group of applications a name.
  3. Click on Next: Assignments.
    In here you can optionally add users or groups to the Application Group. If you don't add them now you will have to assign this Application Group to users later in order for them to see them.
  4. Click on + Add Azure AD users or users groups and you will see the standard AAD user picker menu.
  5. Choose some users or groups to publish these applications to.
  6. Click on Next: Applications
    This is where we select applications to be added to this Application Group. Out of the box there are two methods to find applications: The Start menu and finding the exe file in the file system aka File Path 
    Note:  at least one VM in the Host Pool needs to be powered on and accessible for this section to work as it requires to talk to a VM to grab the icons from the application selected.
  7. Click on + Add applications and select Start menu in the Application Source drop down. Then find an application you want to publish.
  8. Click on Save
  9. Click on + Add applications again and this time select File Path in the Application Source Drop down.
  10. Add an application using its file path.
  11. Click on Save. Applications should now be added to the Application Group.
  12. Click on Next: Workspace
    This is where we register this application group with a Workspace. This is optional. If you say No, you will need to later complete this assignment. Also No allows you to create Application groups prior to Workspaces and later do the registration. If you don't have a Workspace select No and we can create one later.
    I already have a Workspace so I select Yes.
    In my instance I already have the Desktop Application Group from this same host pool registered to the "Tomboy WVD Workspace" hence it is forcing the registration of this application group in the same host pool to this same Workspace
    If that Desktop Application Group didn't exist or was not linked to this or any Workspace the Register application group would be active and allow me to select the Workspace that I wanted:
  13. Click on Next: Tags - where you can add any Tags you want.
  14. Click on Next: Review + Create >
  15. Click on Create.

This will deploy Your Application Group and Register it to your Workspace.

Create the Workspace

The third piece of the puzzle is to have a Workspace. This translates to a tenant in the previous model. You may well want to create this object first (at least that's how I have done this)

  1.  Click on Workspaces. Then Click on + Add
  2. Select your Resource Group and enter the naming details for your Workspace and include your location

  3. Click on Next: Application Groups
    If you have any Application Groups that are not already registered with another Workspace, this is where you can register them to this Workspace.
  4. Click on + Register application groups, and select the Application group you want to be associated with this Workspace
  5. Click on Next: Tags and add any of your tags
  6. Click on  Next: Review + create >
  7. Click on Create

This will now create you a Workspace. If you open any of the WVD clients and log in as a user who had been assigned to the application group you should now see your workspace and those applications.

Note that throughout all of this the Host pool, Application Group and Workspace all need to be in the same Azure region to be associated with each other.

Scaling out a host pool

Prior to the spring update if you wanted to scale out a host pool you would run the Azure Marketplace deployment or the Github template a second time and reference the existing Resource Group and Host pool. You would specify the number of VM's you wanted to end up in the host pool, i.e. 10. If your host pool had five VM's it will deploy five VM's to make up the difference.


Now with Spring Update there is a specific option to scale out your host pool - no need to rerun anything.


  1. Navigate to the Host pool and go to the Session Hosts section and select the Add button located at the top.
  2. Click on Add and you are taken to the specific Session Host addition screen:


On the Virtual Machines section, you just need to complete all the standard answers as before. The only difference is the Number of VMs. In here enter the number of new VM's you want to have deployed and added to this Host Pool:


On the Virtual Machines section, you just need to complete all the standard answers as before. The only difference is the Number of VMs. In here enter the number of new VM's you want to have deployed and added to this Host Pool.

Also the host name can not be changed, and the prefix is hardcoded to the pre-existing prefix. In my example it will add four session hosts, and as I have one existing VM called test2-0 it will create test2-1 through to -4.


RDP Settings


Another nice feature is the ability to set RDP Custom properties for each host pool directly in Azure Portal. This was previously only possible via PowerShell. Go to the Host pool and Properties, the RDP Settings. Here you enable any of the options you need.

WVD Monitoring

Each WVD ARM can be directly linked to either Log Analytics, Event Hub, or to Azure Storage.

  1. Just click on Diagnostics settings on any object:
  2. Then choose what you want to log and where you want it to be stored.
Senior Member

This looks great! Really been waiting for this. Did I miss how existing WVD deployments can be added to the new Management Blade? Mine don't show up.


Unfortunately, it is not backward compatible. There will be some PowerShell tooling being released to enable a migration. Watch this space.

Occasional Contributor

@TomHickling So did this release nuke existing customers? Our desktops have been down the past hour and have been having issues all morning :(


Our WVD environment is down as well.

Occasional Contributor

Adding comment so i can track this. 

Occasional Visitor

I've ported my Farm to the new Spring release, re-registering hosts and applications. I wont need the Github Web UX Management anymore. Great!!


One thing i noted is that you cannot register an APP twice. As an example. If you want to register application Remote Desktop Connection from start menu you can only do it once using the Start Menu. If you try to add it a second time, this time with Command Line (/V:SERVERNAME.FQDN) it will just over-ride the current one already added. Therefore you must FilePath Apps for the second Remote Desktop Connection using MSTSC with Command Line. One trick is to select the Apps in StartMenu first, then switch to FilePath, this auto-complete the App then you just have to complete the command line.


Even though you define a Command Line the (REQUIRE Command Line) Column remains at (NO)

2020-04-30 15_40_10-IT5 DOMAIN - Microsoft Azure.png


Another Feature:
You can also use the same hosts to do RemoteApplication and Desktops, but not at the same time, your user must logoff from Desktop Sessions before doing RemoteApp Based activities, its usefull for some Dev/Tests scenario on a single node.

@TomHickling it took me quite a few minutes to find out where were the RDP Settings, i initially though it was on desktop config, then remote application config but neither. You might want to refine your post.


So from HOST POOLs select a HostPool, then properties then its very small next to Basic, (RDP Settings)...


2020-04-30 15_27_47-APPS _ Properties - Microsoft Azure.png


I also couldn't find a way to set a FriendlyName on a Publish Desktop, once created it seems to stick with the created name?




Senior Member

@Phil_DESM - how destructive was your porting over from your original deployment? Did you create a new deployment, drop the host from the old deployment, add it to the new deployment, and re-create you applications and/or desktops?


Thank you, I have seen my new host pools show up in all my apps, but not on the web.  Is there a new address for the rdweb client?

Occasional Visitor

Hi @dylanlloyd , you will not have access through the old link.


for access your new app, access:



Not applicable

Great news to see WVD becoming a proper ARM based service! It's good if you point out that the name of the new PowerShell module is Az.DesktopVirtualization and in order to install the new modules you should run:


Install-Module Az.DesktopVirtualization

To find out what command are available:

Get-Command -Module Az.DesktopVirtualization
Regular Visitor

When does this new panel become GA?  And what approximate date will the migration from powershell to ARM be ready?


@daaazure It will go GA later this year, the migration tools will be ready much sooner.

New Contributor

Any news on when WVD will be able to leverage AADJoin, rather than requiring a traditional Active Directory Service?


That is currently on the roadmap but is a little way out at this point

Occasional Visitor

Hi Tom


Thank you for the article.  


I'm curious, will scale down tools (Logic App) such as the one referenced below still work with an ARM based WVD deployment?


Thanks again



It will. Its just being updated to support ARM and will be released shortly

Occasional Visitor

I´m very excited with all these new features. I´m already working on a PoC so I can get familiar with the new administration/provisioning model, I´ll give it a shot and will try to migrate existing hosts to this new model, however I've found a stopper and I'm honestly not sure if this is something that is just temporarily in place until this new release is officially supported.


Here´s the issue:


If a User uses the "Remote Desktop" client to subscribe, he´s only able to see everything that was associated with his old Non-ARM model stuff (Desktop Apps/RemoteApp, etc).




However, I created a new Workspace, Hostpool, DesktopApps and RemoteApps with new ARM process, the user is now forced to re-subscribe in order to be able to see any available WORKSPACE associated with all new features provisioned with the ARM WVD model. This is not acceptable for my environment, as I´m already using Multi Factor authentication and other features, forcing the user to go through authentication/multifactor twice is a stopper for me at the moment. 


I suspect that subscription process for the user would work smoothly and directly to the new Workspace ARM environment (with only 1 authentication prompt), if I didn't happen to had any preexisting Non-ARM resources assigned to the User. Have any of you tested this?






Senior Member

I'm really looking forward to see this working ;) That's a really nice one! 

Having AAD-Join possibility and Intune Management option would be really great for us to better manage that environment...

Occasional Contributor


Do you have any tutorial on how to migrate from the old non-arm deployment model to the new way?


Hi Phil - not at this point but it will be avalible shortly - watch this space.


@TomHicklingFYI: the Docs page you link for the current management WebApp is 404


@Mary Branscombe Hi Mary - thanks the docs site has had a make over due to the Spring Release.

Occasional Visitor

@TomHickling Any idea when the Desktop App will get updated? I created one of our Clients to latest WVD ARM, it is not working with existing WVD Client App anymore.


@Sush22 The Windows client supports both the new Spring Release (ARM) as well as the existing release, and will display a WVD tenant alongside a new WVD Workspace. You just need to ensure you are suubscribed using the correct credentials. The Web client has a new dedicated URL: 

Regular Visitor

We will be waiting for the migration process of old WVD hostpools to the ARM one, Is there any timeline for the availability??

Senior Member

Getting a permissions error when attempting to make user assignments any idea as to the issue, also how are image updates to an existing pool handled, in the fall release there was a arm template that produced various results.   The account used for user assignments is a subscription contributor and Global Admin.













Occasional Visitor

@Phil_DESM Can you provide instructions on the porting over process you were able to perform?

New Contributor


I kept getting an error with the Remtote Desktop, trying to connect to the new WVD (arm deployed) environment.

While checking the logs, I saw that the Remote Desktop apps fetches the registry key "DefaultFeedURL" located in [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSRDC\Policies].
I understood that the remote desktop app should redirect automatically to the new ARM Workspace, but that didn't work for me.

That's why is set the key like this:



After restarting the Remote Desktop app, I could see the new workspace and could successfully login to my desktop. 



@TomHickling Hi,


Just want to know how can I specify exactly what AAD tenant I wanted to use for user authentication into the WVD service


i.e. it could be separate to the AAD tenant that your Azure subscription that you deploy the WVD session hosts into is itself linked to.


hiw can I address that now ?

i am an msp and need to have one subscription and not one by customer !!



Occasional Contributor

Hi @arexhaj , just for curiosity. Which Logs did you checked? where did you found them?


Worked for me also on a clean client - needed to create the keys manually.





@Bishopedd With the Spring Release as the WVD objects are all ARM, they inherit the AAD that the Azure subscription is linked to. You cant force the WVD Workspace to use a seperate AAD Tenant anymore.

New Contributor


Ok and how can MSP can do now ?

must have 1 subscription by customer even if the customer have 2 users for example. 

it make not sense for me to manage hundred of subscriptions. 

Occasional Contributor

@Bishopedd As an MSP Azure Lighthouse is something to investigate:


Azure Lighthouse offers service providers a single control plane to view and manage Azure across all their customers with higher automation, scale, and enhanced governance. ... This offering can also benefit enterprise IT organisations managing resources across multiple tenants

Occasional Contributor

@Steve Motton  "...also how are image updates to an existing pool handled..."  The following may help....

Windows Virtual Desktop - #23 - Update Session Hosts from Latest Image
Learn how to use the Shared Image Gallery to update your WVD Session Hosts from the latest image today at The Azure Academy. Shared Image Gallery is a service that helps you build structure and organization around your managed images. Using a Shared Image Gallery you can share your images to different users, service principals, or AD groups within your organization. Shared images can be replicated to multiple regions, for quicker scaling of your WVD deployments.

As well as this coming soon:

Occasional Contributor

@Steve Motton  "Getting a permissions error when attempting to make user assignments any idea as to the issue, also how are image updates to an existing pool handled, in the fall release there was a arm template that produced various results.   The account used for user assignments is a subscription contributor and Global Admin."

I just tested this in my environment with the same permissions and it returns the message below; this is because the Contributor role does not have the 'write action' ... user account must have Microsoft.Authorization/roleAssignments/write permission 

{"details":[{"code":"InvalidTemplateDeployment","message":"{\"content\":{\"error\":{\"code\":\"AuthorizationFailed\",\"message\":\"The client '' with object id 'xxxxxxxxxx' does not have authorization to perform action 'Microsoft.Authorization/roleAssignments/write' over scope '/subscriptions/xxxxxxxxxxxxxxxxxxx/resourceGroups/wvd02-rg/providers/Microsoft.DesktopVirtualization/applicationgroups/pool1-DAG/providers/Microsoft.Authorization/roleAssignments/c5a75bcb-7bfb-439a-89e3-ed07dab7000d' or the scope is invalid. If access was recently granted, please refresh your credentials.\"}},\"headers\":{\"cache-control\":\"no-cache\",\"content-length\":\"585\",\"content-type\":\"application; charset=utf-8\",\"expires\":\"-1\",\"pragma\":\"no-cache\",\"x-ms-correlation-request-id\":\"0264e216-7f77-4a01-a8a6-7189f360e562\",\"x-ms-failure-cause\":\"gateway\",\"x-ms-request-id\":\"0264e216-7f77-4a01-a8a6-7189f360e562\",\"x-ms-routing-request-id\":\"NORTHEUROPE:20200519T180005Z:0264e216-7f77-4a01-a8a6-7189f360e562\"},\"httpStatusCode\":403}","target":"c5a75bcb-7bfb-439a-89e3-ed07dab7000d"}]}


Yes so you user account needs at least Contributor access to create resources and then also the "User Access Adminstrator" to add users/groups to Application Groups


@SteveMiles70 There will be a new "Update" template released in the smae timeframe as when the Sprin Release goes GA

New Contributor

@TomHickling  is the scale down feature will work for spring update (ARM) ? I can't found any article for the same. Fall update Logic App seems that not working. 


@Laxmanranga09 This is currently being updated and will be released before spring uupdate goes GA

Occasional Contributor

Will (and when) the Azure REST API be updated for this new deployment method? Currently when running WVD REST API calls it only returns the Host Pools deployed the original method.

Occasional Visitor

Please share the latest document of windows virtual desktop 2020. Also share the step by step with images , how to configure windows virtual desktop in android client.

Occasional Visitor

As per the instructions given in document, I am unable to connect RDP to Android client. I Follow below steps:-

1.  Installed Remote Desktop(Preview)(Early Access).

2. Add remote Feed URL:-

3. Provide Azure Subscription ID and password.

4. Connection connected.




5. When I click any application, a screen promoted (connected to rd gateway) 

App1.PNG  App2.PNG

6. Typing Azure subscription Id and password  but not accepting. Promoting repeatedly.

 Please help how to connect ( )


Is "Azure Active Directory integration -Native Active Directory (On-Prem)" of Azure Files an storage option for WVD spring 2020?


@Karish1 The two are not directly related. Azure Files AD integration is currently in public preview and due to go GA shortly, watch ot for announcements on this. Azure files currently already supports AAD DS integration. Spring Release for WVD has brought a lot of new capabilities but is seperate to Azure Files although the timing is similar.

Occasional Contributor

@TomHickling - Any news on tooling that can help us migrate existing non-arm deployment?

Senior Member

Any ETA on the migration PS to move to spring?


@chrischambersau @fosselius This is due in Q3 2020 - watch this space.

Version history
Last update:
‎Jun 15 2020 08:42 AM
Updated by: