That vNet needs access to Active Directory, that can either be located in Azure or on-premises as long as there is connectivity.

The Virtual Machines all need to be located on a Virtual Network.

Azure AD Connect is the tool that will provision accounts from AD to AAD to enable 1.

When launching published Desktops and Applications – Windows still requires Active Directory authentication.

The Azure Active Directory is your identity provider in the cloud and users authenticate against AAD to get access to the Windows Virtual Desktop service.

An Azure subscription and its associated ID.

An Azure Virtual Network updated with your DNS server, with line of sight of your AD DC’s.

Use this in conjunction with the existing deployment guide from Microsoft docs.įrom a high level you will require the following items before you can deploy Windows Virtual Desktop

In this guide you will either create and record or if already existing just record the information needed in the WVD deployment process and keep it in one place in Notepad to use later in the full deployment. This guide will enable to collect all the relevant pieces of prerequisite information and have them all in one place that you can then put back into the Azure portal at deployment time.

This is not a full deployment guide, there is already existing full deployment instructions available. This is to ensure the deployment process will complete successfully. Hence this will clearly explain what prerequisites are required to be in place and where to get the relevant information and then where to exactly put these details into the Windows Virtual Desktop HostPool creation process in the Azure portal. There are a few pieces of information you need and it is possible to get this wrong.

Hence this simple guide is designed to save you some time by avoiding common errors in the deployment process. However we have seen a large number of failures of the Azure Resource Manager deployment from a set of customers, all for very similar quite simple errors entered into the Azure portal deployment process, things like incorrect accounts, or lack of name resolution. It went into public preview in March of 2019, with many successful deployments for testing purposes having been completed. Windows Virtual Desktop is a newly announced capability for managing VDI and RDSH as a service from Azure.

Mac wvd client