Study guide

2.5 Azure Virtual Desktop

Microsoft Azure Fundamentals AZ-900

Track your progress as you read

Finished sections get a check mark.

1 Introduction

About the Microsoft Azure Fundamentals (AZ-900) Exam Study Strategies and Exam Tips

2 Domain 1: Cloud Concepts (25-30%)

1.1 What Is Cloud Computing? 1.2 Cloud Service Models (IaaS, PaaS, SaaS) 1.3 Cloud Deployment Models (Public, Private, Hybrid) 1.4 The Consumption-Based Model

3 Domain 2A: Azure Architecture Components

2.1 Azure Regions and Availability Zones 2.2 Azure Resource Hierarchy (Management Groups, Subscriptions, Resource Groups) 2.3 Azure Resource Manager (ARM) Overview

4 Domain 2B: Azure Compute Services

2.3 Azure Virtual Machines 2.4 Azure App Service, Containers, and Serverless 2.5 Azure Virtual Desktop

5 Domain 2C: Azure Networking Services

2.6 Azure Virtual Networks (VNet) 2.7 Azure VPN Gateway and ExpressRoute 2.8 Azure Load Balancing and Content Delivery

6 Domain 2D: Azure Storage Services

2.9 Azure Storage Accounts and Services 2.10 Azure Database Services 2.11 Azure Data Services and Analytics

7 Domain 2E: Azure Identity, Access, and Security

2.11 Microsoft Entra ID (Azure Active Directory) 2.12 Azure RBAC, Zero Trust, and Defense in Depth 2.13 Azure Security Services

8 Domain 3A: Azure Cost Management

3.1 Factors That Affect Azure Costs 3.2 Azure Pricing Calculator and Cost Management 3.3 Using Tags for Cost Management and Organization

9 Domain 3B: Azure Governance and Compliance

3.3 Azure Policy 3.4 Resource Locks and Tags 3.5 Azure Blueprints, ARM Templates, and Bicep 3.6 Azure Governance Features: Putting It All Together

10 Domain 3C: Azure Monitoring and Management Tools

3.6 Azure Monitor and Service Health 3.7 Azure Compliance, Privacy, and Trust 3.8 Azure Activity Log, Diagnostics, and Resource Health

11 Additional Azure Services and Exam Review

Azure AI and Machine Learning Services Azure IoT and DevOps Services AZ-900 Exam Review: Key Concepts Summary Common AZ-900 Exam Scenarios and Practice

12 Advanced Azure Topics and Service Deep Dives

Azure Migration Services and Tools High Availability and Disaster Recovery in Azure Azure Networking: Private Link, Service Endpoints, and Bastion Azure Management Tools: Portal, CLI, PowerShell, and Cloud Shell Azure SLAs, Service Lifecycle, and Support Plans

2.5 Azure Virtual Desktop

Key Takeaways Explain This Topic AI

Azure Virtual Desktop (AVD), formerly Windows Virtual Desktop, is a cloud-hosted desktop and application virtualization service running on Azure VMs.

Windows 11 and Windows 10 Enterprise multi-session is UNIQUE to AVD — multiple users share one VM, a capability not licensed for on-premises Hyper-V.

AVD supports full pooled or personal (persistent) desktops and RemoteApp publishing of individual applications, accessible from any device with the AVD client or a browser.

Security comes from Microsoft Entra ID authentication, MFA, Conditional Access, RBAC, and reverse connect — no inbound ports are opened and only screen pixels reach the device.

AVD cuts cost through multi-session density (fewer VMs per user) and is the managed answer for remote/hybrid work, BYOD, and contractor access.

Last updated: October 2026

Quick Answer: Azure Virtual Desktop (AVD) is a managed Virtual Desktop Infrastructure (VDI) service. It streams full Windows desktops or individual apps from Azure VMs to any device. Its signature feature is Windows 11/10 Enterprise multi-session , letting many users share one VM — a capability available only on Azure.

What Is Azure Virtual Desktop?

Azure Virtual Desktop (AVD) — formerly Windows Virtual Desktop (WVD) — is a desktop and application virtualization service running entirely in Azure. Instead of giving each employee a physical PC, the desktop runs on Azure VMs and the user connects from a laptop, tablet, thin client, Mac, or web browser using the AVD client.

AVD is a form of Virtual Desktop Infrastructure (VDI) : the operating system, applications, and data live in the cloud, and the endpoint device only displays the session. Because Microsoft manages the brokering, gateway, and web-access components, AVD is a managed VDI — you supply and size the session-host VMs, and Azure runs the control plane around them.

Core Architecture (high level)

  • Component Role
  • Host pool A collection of identical session-host VMs that users connect to
  • Session host An Azure VM running Windows multi-session or single-session that hosts user sessions
  • Application group What is published to users — a full Desktop group or a RemoteApp group of individual apps
  • Workspace A logical container that groups application groups for users to discover
  • Control plane Microsoft-managed gateway, connection broker, and diagnostics
  • Key Capabilities

Feature Description

Multi-session Windows Run Windows 11 or Windows 10 Enterprise multi-session so many users share one VM — unique to Azure

  • Full desktop Deliver a complete Windows desktop experience
  • RemoteApp Publish individual applications (e.g., one line-of-business app) instead of a whole desktop
  • Microsoft 365 integration Optimized delivery of Microsoft 365 Apps including Word, Excel, and Teams

Pooled or personal Pooled (users share session hosts) for density, or personal/persistent (one dedicated VM per user)

On the Exam: Windows 11/10 Enterprise multi-session is the headline differentiator. Standard Windows client licensing allows only one interactive session; multi-session lets several users log in to a single VM, and it is offered only through Azure Virtual Desktop.

Why Organizations Choose AVD

Work from anywhere — the desktop follows the user to any internet-connected device, supporting remote and hybrid work.

Bring Your Own Device (BYOD) — contractors and staff use personal hardware without corporate data ever landing on it.

Centralized management — IT images, patches, and governs every desktop from the Azure portal instead of touring physical machines.

Fast onboarding/offboarding — spin up a new user's desktop in minutes; revoke access instantly when they leave.

Cost optimization — multi-session density packs many users onto fewer VMs, and host pools can scale down or power off outside business hours.

FSLogix profile containers — user profiles roam between session hosts in a pooled pool, so a user keeps their settings even when assigned a different VM each login.

Security Model

AVD's security design keeps data off endpoints.

  • Control What it does
  • Microsoft Entra ID Authenticates users (formerly Azure Active Directory)
  • Multi-factor authentication (MFA) Adds a second verification factor
  • Conditional Access Enforces sign-in rules by device, location, or risk
  • Role-based access control (RBAC) Limits who can manage host pools and resources
  • Reverse connect Session hosts open no inbound ports to the internet; the host reaches out to the AVD gateway
  • Pixel-only streaming Only screen images, keystrokes, and mouse moves traverse the wire; files stay in Azure

Because of reverse connect , you never expose Remote Desktop Protocol (RDP) ports such as 3389 to the public internet, eliminating a huge attack surface that traditional RDP servers carry.

Worked Scenario

A consulting firm hires 50 seasonal analysts who use their own laptops. The firm needs them to run a sensitive financial app for three months without that data ever residing on personal devices. AVD with a pooled host pool and RemoteApp publishes just the financial app; reverse connect avoids open ports, Conditional Access plus MFA gates sign-in, and at contract end IT removes the users — no data was ever copied to a laptop because only pixels were streamed.

Common Traps

AVD does not virtualize Linux desktops; it delivers Windows desktops and apps.

Multi-session is the only feature truly unique to Azure — remote desktop, app virtualization, and full desktops also exist elsewhere, so a question asking what is unique should be answered with multi-session.

Pooled (shared, non-persistent) saves the most money; personal/persistent gives each user a dedicated VM but costs more — match the choice to whether users need to keep their own customizations.

On the Exam: Tie AVD to managed VDI for remote/BYOD work , remember reverse connect = no inbound ports , and recall that data stays in Azure while only pixels stream to the device.