Azure Virtual Desktop (AVD) is a comprehensive cloud-based desktop and application virtualization service from Microsoft Azure. To set up and run AVD, certain prerequisites need to be fulfilled, covering licensing, infrastructure, networking, and security.

1. Azure Subscription

• Azure Active Subscription: You need an active Azure account and subscription.
• Licensing: Users must have a valid Windows 10 or Windows 11 license. Common options include:
  • Microsoft 365 E3/E5
  • Windows 10 Enterprise E3/E5
  • Windows 10 Education A3/A5
  • Windows 10 VDA (Virtual Desktop Access)

2. Azure Active Directory (Azure AD)

• Azure AD Domain Services: AVD requires Azure AD to manage users and security.
• Azure AD Join: For Windows 10 multi-session and personal desktops.
• Hybrid Identity: If you’re integrating on-premises AD, use Azure AD Connect for synchronization.

3. Virtual Network

• Azure Virtual Network (VNet): Required to connect the virtual machines (VMs) that host the AVD desktops and applications to the rest of your infrastructure.
  • Ensure the virtual network has adequate DNS configuration to resolve your domain.
  • Use subnets with proper IP addressing to support AVD traffic.

4. Active Directory

• On-Premises or Azure AD DS:
  • Users can authenticate using either Azure AD DS or on-premises Active Directory synced with Azure AD using Azure AD Connect.

5. Domain Controller

• A domain controller (DC) is required if you are using an on-premises AD for authentication, either by:
  • Azure AD Domain Services (managed domain)
  • On-premises AD with VPN or Azure AD Connect

6. Virtual Machine Requirements

• Supported OS: Windows 10/11 Enterprise multi-session, Windows 10/11 Enterprise, Windows Server 2012 R2 and above.
• VM Size: Choose an appropriate Azure VM size based on the workloads and user concurrency.
  • E.g., D-series or NV-series VMs for typical desktop usage or graphics-intensive workloads.

7. Storage Configuration

• FSLogix Profiles: For user profile containers, use FSLogix to provide a consistent user experience.
  • Azure Files or Azure NetApp Files: These are often used to store FSLogix profile containers.

8. Networking

• VPN or ExpressRoute: If integrating with an on-premises network, ensure you have a VPN gateway or ExpressRoute connection.
• RDP Access: Ensure TCP port 3389 (for RDP access) is open in your NSGs (Network Security Groups) and firewalls.
• Public IPs: Not required unless you are accessing the VMs directly over the internet.

9. Client Device Requirements

• Supported Devices: AVD clients can run on Windows, macOS, iOS, Android, and web browsers.
• Microsoft Remote Desktop App: Users need the Microsoft Remote Desktop app installed for connecting to AVD.

10. Azure Resource Management (ARM) Role-Based Access Control (RBAC)

• Grant required permissions for managing AVD resources using ARM-based roles like:
  • Virtual Machine Contributor
  • Desktop Virtualization Administrator

By ensuring these prerequisites are in place, you can set up and manage Azure Virtual Desktop effectively.