Azure Virtual Desktop
Azure Virtual Desktop is a desktop and app virtualization service on Azure. Microsoft runs the broker and gateway; you run the session host VMs and images in your subscription, with Windows 11 or 10 Enterprise multi-session, full desktops or single apps (RemoteApp), and session hosts in Azure or on Azure Local.1
Also known as AVD, Windows Virtual Desktop (former name), Azure Virtual Desktop for Azure Local, Azure Virtual Desktop Hybrid
- Intended for
- Virtualization and end-user computing teams, Organizations replacing Remote Desktop Services or other VDI, Software vendors delivering Windows apps to their customers, Teams with on-premises desktop requirements (Azure Local)
- Runs on
- Azure public regions (session hosts in any Azure region), On-premises on Azure Local, Azure Virtual Desktop Hybrid on other on-premises infrastructure, Sovereign clouds: Azure for US Government and Azure operated by 21Vianet2
At a glance
- What is it?
- Azure Virtual Desktop (AVD), formerly Windows Virtual Desktop, delivers Windows desktops and applications from virtual machines. Microsoft operates the service components such as the connection broker and gateway, while you deploy and manage the session host VMs, images and host pools in your own Azure subscription. It supports Windows 11, Windows 10 and Windows Server session hosts, single-session or multi-session, full desktops or individual apps through RemoteApp. Session hosts can also run on-premises on Azure Local. The older AVD classic (non-Azure Resource Manager) service retired on 30 September 2026.1
- What does it do?
- AVD lets you create host pools, application groups and workspaces, assign users and publish desktops or apps through the portal, CLI, PowerShell or REST API. It offers Windows 11 and Windows 10 Enterprise multi-session (exclusive to AVD) to put several users on one VM, personal persistent desktops, autoscale by schedule or demand, custom image templates, FSLogix profile containers, AVD Insights for monitoring, and reverse-connect transport so no inbound ports are opened, with RDP Shortpath for direct UDP connections. Users connect with Windows App, the Remote Desktop client or an HTML5 web client.12
- Who needs it?
- Organizations that want to control VM sizes, images and costs for large numbers of users, especially shared task-worker desktops where multi-session lowers VM counts; teams replacing Remote Desktop Services farms; software vendors that deliver Windows apps to external customers through per-user access pricing; and organizations that need desktops close to users or data on-premises through Azure Local.1
- What does it need?2
- An Azure subscription with the Microsoft.DesktopVirtualization resource provider registered
- User accounts in Microsoft Entra ID (hybrid identities if session hosts join AD DS or Entra Domain Services)
- Eligible licenses: Microsoft 365 E3, E5, A3, A5, F3, Business Premium or Windows Enterprise E3/E5, Education A3/A5 or VDA per user for Windows clients; RDS CALs with Software Assurance for Windows Ser
- A virtual network in the session host region that reaches domain controllers and DNS, and required URLs allowed outbound
- Round-trip latency from users to the Azure region below 150 ms is recommended
- What it is not
- AVD is not a fixed-price, fully managed Cloud PC: you design host pools, size and patch VMs, manage images and pay Azure consumption, unlike Windows 365. It is not AVD classic, which retired on 30 September 2026; connections to classic resources are blocked after retirement. AVD on Azure Local is not an Arc-enabled service: host pools and brokering stay in Azure, so it needs connectivity to Azure and does not run as a standalone or multicloud service.3
Availability and licensing. Generally available (checked 26 October 2026). Azure Virtual Desktop classic retired on 30 September 2026, and connections to classic resources are blocked after retirement. Billing: Azure consumption for VMs, storage and networking, with user access through eligible licenses; per-user access pricing for external users; AVD for Azure Local adds a per-active-vCPU service fee. The product page announces Azure Virtual Desktop Hybrid as generally available. AVD on Azure Local for Azure Government is in preview.4
The problem it solves
Running Remote Desktop Services or third-party VDI means operating gateways, brokers, licensing servers and load balancers in addition to the desktops themselves, and scaling that infrastructure for peaks.
AVD moves those infrastructure roles to a Microsoft-managed service and leaves you with the parts that differ per organization: images, session host VMs, scaling rules and user assignments, billed through Azure consumption.
How it works
AVD separates service components from session hosts:
- Microsoft-managed: broker, gateway and other infrastructure roles, plus host pool, workspace and application group metadata stored in an Azure region you choose.
- Customer-managed: session host VMs in your subscription (or on Azure Local), images from Azure Marketplace, an Azure Compute Gallery or custom image templates, the virtual network and connectivity to domain controllers, and FSLogix profile storage on Azure Files or Azure NetApp Files.
Users authenticate with Microsoft Entra ID. Session hosts join Entra ID or an Active Directory domain (AD DS or Microsoft Entra Domain Services). Session hosts open an outbound reverse connection to the service on TCP 443, so no inbound ports are needed; RDP Shortpath can add direct UDP transport.2
Diagram as a list
Copilot & business apps
- Windows App, Remote Desktop client or web clientUsers connect to desktops and appsConnects to AVD service (broker, gateway), Microsoft-managed
Data & analytics
- FSLogix profile containers (Azure Files, Azure NetApp Files or SMB share)Store user profiles across sessions
Developer tools
- Images (Azure Marketplace, Compute Gallery, custom image templates)Base for session host VMsConnects to Session host VMs in your Azure subscription
Security, identity & governance
- Microsoft Entra IDAuthenticates every userConnects to AVD service (broker, gateway), Microsoft-managed
Cloud & hybrid infrastructure
- AVD service (broker, gateway), Microsoft-managedAuthenticates, brokers and relays sessionsConnects to Host pools, application groups and workspaces
- Host pools, application groups and workspacesDefine what is published to which users
- Session host VMs in your Azure subscriptionRun single-session or multi-session Windows and appsConnects to FSLogix profile containers (Azure Files, Azure NetApp Files or SMB share)
- Session hosts on Azure Local (optional)On-premises session hosts managed from the same serviceConnects to FSLogix profile containers (Azure Files, Azure NetApp Files or SMB share)
Capabilities
Windows multi-session1
Windows 11 and Windows 10 Enterprise multi-session, exclusive to AVD, allow several concurrent users per VM.
Why it matters: Fewer VMs and less OS overhead for shared desktops.
Limits: Users share VM resources; sizing and monitoring are your responsibility.
Full desktops or RemoteApp1
Publish a full desktop or individual applications from a host pool through application groups.
Why it matters: Deliver only the apps users need, including line-of-business Win32, MSIX and Appx apps.
Limits: App compatibility with multi-session must be tested.
Managed infrastructure roles1
Microsoft runs the gateway and broker; you manage only session host VMs and images.
Why it matters: No gateway servers to deploy, unlike Remote Desktop Services.
Limits: You still own image patching, scaling rules and VM costs.
Autoscale1
Increase or decrease capacity by time of day, day of week or demand.
Why it matters: Helps control Azure compute costs.
Limits: Savings depend on scaling plans matching real usage.
Session hosts on Azure Local3
Run session hosts on-premises on Azure Local 23H2 or later, while service components stay in Azure.
Why it matters: Better performance near users and data locality for app and user data.
Limits: Adds a per-active-vCPU service fee; cannot mix Azure and Azure Local hosts in one host pool; requires Azure connectivity; AVD on Azure Local for Azure Government is in preview.
Per-user access pricing for external users7
Pay through an Azure subscription for external customers who use your app or desktop, in Apps or Desktops plus apps tiers.
Why it matters: Software vendors can deliver Windows apps without customers holding Microsoft 365 licenses.
Limits: Only for external commercial purposes; not available for Windows Server session hosts; does not include Office.
Secure connectivity2
Reverse connections over TCP 443 with no inbound ports, optional RDP Shortpath, and Entra ID authentication.
Why it matters: Reduces exposure of session hosts to the internet.
Limits: Required URLs must be allowed through firewalls.
Practical use cases
A call center needs hundreds of identical desktops that are used in shifts.
- Approach
- Run a pooled host pool with Windows 11 Enterprise multi-session and autoscale by shift schedule.
- Role of Azure Virtual Desktop
- AVD brokers users onto shared session hosts.
- Data, infrastructure and skills
- Eligible licenses, a golden image, FSLogix storage.
- Type of benefit
- Lower cost per user
- Caveats
- Requires image management and sizing work.
- First step
- Pilot one host pool with a scaling plan for a single shift.
A software vendor wants to deliver its Windows application to customers without a rewrite.
- Approach
- Publish the app with RemoteApp and enroll the subscription in per-user access pricing.
- Role of Azure Virtual Desktop
- AVD hosts and streams the app; per-user pricing covers access rights.
- Data, infrastructure and skills
- An enrolled Azure subscription and identities for external users.
- Type of benefit
- New delivery channel
- Caveats
- Per-user access pricing excludes Office and Windows Server hosts.
- First step
- Publish the app to a test customer group under the Apps price tier.
Engineers at a remote plant need desktops with low latency to local systems.
- Approach
- Deploy AVD session hosts on Azure Local at the site.
- Role of Azure Virtual Desktop
- AVD manages the desktops; Azure Local hosts them locally.
- Data, infrastructure and skills
- Azure Local 23H2 or later, AD DS join, Azure connectivity.
- Type of benefit
- Performance and data locality
- Caveats
- Extra per-vCPU AVD for Azure Local fee and Azure Local host fees apply.
- First step
- Create a small host pool on the local instance and compare latency.
Works with
Requires
- Microsoft EntraMicrosoft Entra ID is always used to authenticate AVD users.
Optional integration
- Azure LocalAVD session hosts can run on-premises on Azure Local.
- Microsoft IntuneSession hosts can be managed with Intune when Entra joined or hybrid joined (Windows client OS).
Complementary tools
- Windows 11 and Copilot+ PCsRecall filters Azure Virtual Desktop sessions, and AVD offers screen capture protection.
Alternative approaches
- Windows 365Both deliver Windows desktops from the cloud; Windows 365 Enterprise itself uses Azure Virtual Desktop technology for connectivity, while AVD offers multi-session and consumption billing.
Optional integration for
- Azure LocalAzure Virtual Desktop session hosts can run on Azure Local.
Relationship labels follow Microsoft's documentation. "Alternative approaches" does not mean one is better: each profile says when it fits.
Compared with
Getting started
Check licensing and identity
Confirm users hold an eligible license (or plan per-user access pricing for external users) and choose an identity model: Entra-only, AD DS or Entra Domain Services.
Check: Every pilot user has an eligible license and an Entra ID account.
Prepare the subscription and network
Register the Microsoft.DesktopVirtualization resource provider and create a virtual network in the region closest to users that can reach domain controllers if needed.
Check: The resource provider shows Registered and the network reaches DNS and required URLs.
Create a host pool
Create a pooled host pool with Windows 11 Enterprise multi-session session hosts from the Marketplace, an application group and a workspace.
Check: Session hosts show as Available in the host pool.
Connect and tune
Assign pilot users, connect with Windows App, configure FSLogix profiles and an autoscale plan.
Check: Users can sign in, profiles persist between sessions and idle hosts scale down.
Official resources
Deciding whether you need it?
Three free tools apply Microsoft's own published guidance to your situation, and say when Azure Virtual Desktop or any new technology is not needed.
Sources
Each statement above links to the source it comes from. Labels say who reported it.
- What is Azure Virtual Desktop? (opens in a new tab)
- Prerequisites for Azure Virtual Desktop (opens in a new tab)
- Azure Virtual Desktop on Azure Local (opens in a new tab)
- Azure Virtual Desktop product page (opens in a new tab)
- What is Windows 365? (opens in a new tab)
- What is Windows 365 Enterprise? (opens in a new tab)
- Licensing Azure Virtual Desktop (opens in a new tab)
Thank you. Your correction was sent.
The editors check it against the sources. If you left an email address, they may reply about it.