Conceptual breakdown of the WVD QuickStart

To understand how the WVD QuickStart works, this page will walk you through a conceptual overview. In addition to the overview on this page, the links below provide a more in-depth walkthrough of certain components of the solution, which can be very helpful in case you want to understand the code behind the solution or when you want to more advanced customizations.

Conceptual Deployment Overview

As stated in the overview, the WVD QuickStart takes much of the WVD deployment complexity away, simplifying and automating the process, making the platform more accessible to non-expert users. As a WVD-centric end-to-end solution, the quickstart addressess reported pain points, challenges and feature gaps, empowering IT professionals to get started with WVD in a matter of clicks. This page will help you answer how exactly the QuickStart achieves that. The diagram below shows a high-level conceptual overview of the deployment with the WVD QuickStart: Deployment overview In short, the QuickStart requires you to have some prerequisites - From which it will, in a fully automated way using Azure DevOps, deploy a functional WVD environment with two virtual machines running Windows 10 Enterprise Multi-Session, build 2004, with Office 365 and Microsoft Teams installed. Additionally, the virtual machines will be configured with FSLogix for user profile management. Upon completion, a test user can login to the environment and experience the best of what WVD has to offer.


In short, the deployment with the WVD QuickStart consists of two main parts:

After clicking the “Deploy to Azure” button, the first of the two can be kicked off after providing some limited user input. Following that deployment, the DevOps pipeline will automatically start and deploy a WVD environment for you. The diagram below gives a good overview of all components of the QuickStart, as well as all the resources that are deployed in the process.

Deployment overview

As can be seen in the image, the DevOps automation will deploy a host pool, a desktop application group, a workspace and virtual machines, that upon completion of the pipeline will be ready for use. By default, the virtual machines will utilize a gallery OS image of Windows 10 Enterprise Multi-Session, build 2004, with Office 365 and Microsoft Teams installed and FSLogix configured. This can be customized, if desired, to be a different gallery image or a custom image using the Shared Image Gallery.

Microsoft Support is not handling issues for any published tools in this repository. These tools are published as is with no implied support. However, we would like to welcome you to open issues using GitHub issues to collaborate and improve these tools. You can open an issue here.