How to Deploy AVD in Under 30 Minutes

Azure Virtual Desktop deployment doesn't have to take days. With the right approach and a clear checklist, you can have a working AVD environment in 30 minutes or less.

By David,

Is 30 Minutes Really Achievable?

Yes, with a few prerequisites in place. This guide assumes you have an Azure subscription, the right permissions, and a clear understanding of what you're building. If you're starting completely from scratch, some prerequisite steps such as Entra ID configuration and networking setup will add time. But for organizations with an existing Azure footprint, 30 minutes is a realistic target for a working host pool with a connected session host.

Let's walk through it.

Prerequisites (5 Minutes)

Before you start the deployment, confirm you have:

Azure Permissions:

  • Owner or Contributor on the target Azure subscription
  • User Access Administrator (to assign the Desktop Virtualization role)

Entra ID Configuration:

  • Users must be synced to Entra ID (Azure AD), either cloud-only or hybrid synced from on-premises AD
  • If using Microsoft Entra joined session hosts with no domain controller required, this is all you need
  • If using AD domain join, you need domain credentials and network line-of-sight to a domain controller

Networking:

  • A VNet with an available subnet for session hosts
  • For AD domain join: network connectivity from the subnet to your domain controller
  • Outbound internet access for the session hosts (required for AVD broker connectivity)

Licensing:

  • Microsoft 365 E3/E5, Windows 10/11 Enterprise E3/E5, or equivalent license that grants AVD access rights

New to AVD, or not sure which licenses qualify? What Is Azure Virtual Desktop? explains how host pools, application groups and workspaces fit together, and lists Microsoft's eligible licenses.

Step 1: Create a Host Pool (5 Minutes)

  1. In the Azure Portal, navigate to Azure Virtual Desktop and select Host pools
  2. Click + Create
  3. On the Basics tab:
    • Subscription and Resource Group: select or create the target resource group
    • Host pool name: choose a descriptive name such as avd-pool-prod-eastus
    • Location: select the Azure region closest to your users
    • Host pool type: Pooled (multi-session) for most deployments; Personal for dedicated machines
    • Load balancing algorithm: Breadth-first for best user experience during scale-out
  4. Click Next: Virtual Machines

The same host pool can be created from Atlas AVD instead, without leaving for the Azure portal:

Step 2: Add the First Session Host (10 Minutes)

On the Virtual Machines tab:

  1. Add Azure VMs: Yes
  2. Resource group: use the same as the host pool
  3. Name prefix: e.g., avd-sh-prod
  4. Virtual machine location: match the host pool region
  5. Availability options: no infrastructure redundancy for initial testing; availability zones for production
  6. Image: select Windows 11 Enterprise multi-session, Version 23H2 (recommended starting point)
  7. Size: start with Standard_D4s_v5 (4 vCPU, 16 GB) and adjust based on your workload
  8. Number of VMs: 1 for initial deployment; scale from there
  9. OS disk type: Standard SSD to reduce costs without impacting typical AVD workloads
  10. Virtual network: select your existing VNet and subnet
  11. Domain join type: choose Microsoft Entra ID for cloud-only, or Active Directory if domain joining
  12. Enter domain join credentials if applicable

Click Next: Workspace

Step 3: Create a Workspace (2 Minutes)

On the Workspace tab:

  1. Register desktop app group: Yes
  2. Workspace: create new and name it something like avd-workspace-prod
  3. Review the auto-created Desktop Application Group

A workspace is what users see in the Windows App or browser client. The desktop app group contains the full desktop assignment.

Click Review + Create, then Create.

Deployment time: 5-10 minutes for the session host VM to provision and join the host pool.

Step 4: Assign Users (3 Minutes)

Once deployment completes:

  1. Navigate to your new host pool and select Application groups
  2. Open the Desktop Application Group
  3. Select Assignments and click + Add
  4. Search for and select the users or Entra ID groups who should have access
  5. Click Select

Users assigned to the app group can now see and connect to the desktop.

Step 5: Test the Connection (5 Minutes)

Direct one of the assigned users to connect:

Option A (Windows App, recommended): Install the Windows App from the Microsoft Store, sign in with Microsoft 365 / Entra ID credentials, and the workspace and desktops appear automatically.

Option B (Web browser): Navigate to https://client.wvd.microsoft.com/arm/webclient/ and sign in.

A successful connection shows the full desktop. You're live.

Common Issues in the First 30 Minutes

Session host shows as Unavailable:

  • Wait 2-3 minutes after provisioning for the AVD agent to register
  • Check that the session host VM is running (not deallocated)
  • Verify outbound internet access from the subnet

User sees No resources available:

  • Confirm the user is assigned to the Desktop Application Group, not just the host pool
  • Verify the workspace is registered to the host pool

Domain join fails during provisioning:

  • Confirm the VNet subnet has connectivity to the domain controller
  • Verify the domain join credentials have rights to join machines to the domain

What Comes After 30 Minutes

A working AVD environment is just the beginning. Production readiness requires:

  • FSLogix profile containers: persistent user profiles stored in Azure Files or Azure NetApp Files
  • Golden image management: a repeatable process for building and deploying session host images
  • Scaling automation: policies that power hosts on/off based on demand
  • Monitoring: Log Analytics integration, health alerts, and performance dashboards
  • Backup: user data and profile container backups

Each of these topics deserves its own deep dive, but the foundation you built in 30 minutes gives you everything you need to grow from.

Moving users over from VMware Horizon rather than starting fresh? Migrating from VMware Horizon to Azure Virtual Desktop covers the discovery, pilot pool and department waves that turn this first host pool into a full migration.

Production Readiness Checklist

Before calling an AVD environment production ready:

  • FSLogix profile containers configured and tested, with capacity alerts on the share (common errors and fixes)
  • Golden image built, tested, and version-controlled
  • Scaling automation enabled and validated
  • Azure Hybrid Benefit applied (if eligible)
  • Backup policy applied to profile containers
  • Monitoring alerts configured
  • Conditional access policies reviewed
  • Session timeout and disconnect policies configured
  • Teams calls tested and showing as media optimized (how to set it up)
  • User acceptance testing completed

The 30-minute deployment gets you connected. The checklist above gets you production-ready.