To create an Azure Virtual Desktop (AVD) host pool that uses either Active Directory or Microsoft Entra ID (formerly Azure AD), the directory choice is configured when adding session hosts (VMs) to the host pool, not on the host pool object itself.
Below is a concise end‑to‑end outline using the Azure portal; the same host pool works with either directory type depending on how the session hosts are joined.
- Create the host pool (standard management)
- Sign in to the Azure portal and search for Azure Virtual Desktop.
- Select Host pools → Create.
- On the Basics tab:
- Subscription / Resource group: Select or create.
- Host pool name: e.g.
hp01.
- Location: Choose the Azure region.
- Preferred app group type: Desktop or RemoteApp.
- Host pool type:
- Pooled or Personal.
- If Pooled, configure Load balancing algorithm and Max session limit.
- If Personal, configure Assignment type (Automatic/Direct) and optional multiple desktops per user.
- Continue to Next: Virtual machines if session hosts should be created now; otherwise go straight to Review + create and create only the host pool.
This creates the host pool; directory integration is defined on the Virtual machines tab.
- Add session hosts joined to Microsoft Entra ID
Prerequisites: For Microsoft Entra joined session hosts, only the AADLoginForWindows VM extension is supported; it is added automatically when using the Azure portal or ARM template with the AVD service.
On the Virtual machines tab while creating or expanding the host pool:
- Choose to add session hosts on Azure.
- Configure VM size, image, number of VMs, etc.
- Under Domain to join / Select which directory you would like to join, choose Microsoft Entra ID.
- Provide the required Entra configuration (tenant, identity, etc.). The portal will automatically add and configure the
AADLoginForWindows extension.
- Configure Virtual Machine Administrator account (local admin username and password) according to Windows VM requirements.
- Complete networking (VNet, subnet, NSG, no public inbound ports recommended) and finish the wizard.
Once deployment completes, the host pool will have Microsoft Entra joined session hosts.
- Add session hosts joined to Active Directory
There are two main patterns depending on whether using standard management or the preview “session host configuration” approach.
A. Standard management (Virtual machines tab)
On the Virtual machines tab while creating or updating the host pool:
- Choose to add session hosts on Azure.
- Configure VM size, image, count, etc.
- Under Domain to join / Select which directory you would like to join, choose Active Directory.
- Provide domain join details (domain name, OU if needed) and domain credentials.
- Configure Virtual Machine Administrator account for the local admin.
- Finish networking and create.
B. Session host configuration (preview)
If using the preview “session host configuration” management approach:
- Create a pooled host pool with
ManagementType = 'Automated' via PowerShell, for example:
$parameters = @{
Name = '<HostPoolName>'
ResourceGroupName = '<ResourceGroupName>'
ManagementType = 'Automated'
HostPoolType = 'Pooled'
PreferredAppGroupType = 'Desktop'
LoadBalancerType = 'BreadthFirst'
MaxSessionLimit = '<value>'
Location = '<AzureRegion>'
IdentityType = 'SystemAssigned'
}
New-AzWvdHostPool @parameters
- Create a session host configuration with
New-AzWvdSessionHostConfiguration, specifying a custom image or marketplace image and Active Directory join.
- In the portal, when configuring the session host configuration, under Select which directory you would like to join, choose Active Directory, then:
- Select the key vault that contains the secrets for the domain join account (username/password).
- Optionally specify domain name and OU path.
- For Virtual Machine Administrator account, select key vault secrets for the local admin account.
- Create a session host management policy with
New-AzWvdSessionHostManagement to control update behavior.
- Workspace and app group
After the host pool and session hosts are configured:
- On the Workspace tab (optional during creation):
- Set Register desktop app group to Yes.
- Choose an existing workspace or Create new (e.g.
ws01).
- Complete Advanced (diagnostic settings) and Tags, then Review + create.
- Post‑deployment
- Ensure licensing is applied correctly to session hosts as described in the licensing section.
- Assign users or groups to the application group so they can access desktops/apps.
If previous attempts with Windows Active Directory or Microsoft Entra ID failed, verify specifically on the Virtual machines (or session host configuration) step that the correct Select which directory you would like to join option is chosen and that domain/tenant credentials, networking (VNet/subnet reachability to domain controllers or Entra endpoints), and required extensions (AADLoginForWindows for Entra) are correctly configured.
References: