I’ve written a few posts already on WVD. This post is to make sure that all of them are in a single overview for you to view, and to give you a short description of which article you need:

If you are new to WVD and you would like to deploy it in a simple manner you probably want to take a look at:
This post explains how it works in high-level, deploys it using full admin credentials and gives you an overview of how to assign applications or desktops to users

If you are deploying it in production and do not have full administrative permissions you might want to take a look at:
This post explains and shows you the rights required to deploy a delegated WVD environment where the deployment credentials do not have full administrative rights to Azure AD / AD.

Now that you have your pool deployed and you want users to be able to access the applications/desktops, you might want to take a look at the group sync script that assigns WVD access to users based on AD groups:

If you are still building your template, you first might want to take a look at profile management
which explains how to deal with user profiles in a multi-VM backend system where a user could land on any VM but perhaps you do want them to maintain their profile

And before you rebuild your template VM, you might also want to re-use your old one to continue building on top of the other version:

If you’ve updated your template (with new software or patches) or if you need to expand the pool of available hosts you can follow the following link:

Once you deployed it, you probably want to lock down internet usage on those corporate devices:

And if you happen to use ADFS for your AAD, why not use the SSO options available:

Tagged ,