WVD Deployment Guide - Existing AD Supplemental

VDS Setup has the ability to connect a new deployment to an existing AD structure. These instruction cover that option in detail.
This article does not stand-alone, rather it is a detailed explanation of an alternative to the New AD option covered in the WVD Deployment Guide

The next section defines to make is the Active Directory deployment type for the VDS deployment. In this guide we will select Existing Windows Server Active Directory, which will leverage an AD structure that already exists.

VDS Setup will display a list of vNets that could represent the connection between the existing AD structure and Azure AD. The vNet that you select should have the an Azure-hosted DC that you have configured in Azure. In addition, the vNet will have Custom DNS settings pointed at the Azure-hosted DC.

Enter the existing domain name that will be used. Note: you do not want to use the domain that is found in the Azure Portal under the Active Directory module, as it can cause DNS issues. The primary example of this is that users will not be able to access the that website (<yourdomain>.com, for example) from inside their desktop.

There are three ways to provide the credentials necessary to facilitate a deployment using an existing AD structure.

This article covers the unique steps to deploy into an existing AD environment. With these steps complete, you can return to the standard deployment guide here.