Windows Virtual Desktop (WVD) is the former name for Azure Virtual Desktop (AVD). AVD is Microsoft’s Azure-hosted desktop and application virtualization platform: Microsoft operates the brokering service, while you design and manage session-host virtual machines, identity, networking, profiles, applications, security, and costs. This guide explains the terminology, licensing, architecture, and a practical proof-of-concept deployment path.
What Azure Virtual Desktop is
Azure Virtual Desktop delivers either a complete Windows desktop or individual applications to users on supported devices. The desktop runs on an Azure session-host VM; AVD’s control plane handles brokering, connection services, host-pool management, application publishing, and user assignment. It is therefore more than “a VM you connect to.”
As an Amazon Associate I earn from qualifying purchases.
Users connect with the current Windows App or another supported client for Windows, macOS, iOS, Android, the web, and other platforms. Feature support varies by client operating system and Windows App release; verify the capabilities required for audio, video, peripherals, and authentication in your target client. See Microsoft’s AVD client guidance.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Full desktops and RemoteApp
- Desktop application groups publish a complete Windows desktop.
- RemoteApp application groups publish selected applications that appear to users as if they were local programs.
AVD supports Windows 10/11 Enterprise multi-session, single-session Windows Enterprise editions, and supported Windows Server versions, subject to the operating-system and licensing rules in the prerequisites documentation.
#1 Best Overall
WVD, AVD and “Microsoft VDI” terminology
| Term | Meaning today |
|---|---|
| WVD | Windows Virtual Desktop, the former product name for AVD. |
| AVD | Azure Virtual Desktop, Microsoft’s current product name. Microsoft announced the rename as the service expanded beyond its original Windows-desktop positioning; see the announcement. |
| Microsoft VDI | A broad, informal description of Microsoft virtual desktop infrastructure, not necessarily a separate product. |
| Windows 365 | A separate Cloud PC service with assigned-user provisioning and plan-based pricing; it is not another name for AVD. See Windows 365. |
| Azure Virtual Desktop classic | A legacy management model. Older tutorials may show classic tenants, obsolete portal labels, or old client URLs. New deployments should follow current ARM-based AVD documentation. |
AVD architecture explained
Host pool
A host pool is a logical collection of session-host VMs. A pooled pool lets users share available hosts and is commonly used for scalable multi-session desktops. A personal pool assigns users to individual session hosts for a more dedicated experience. Either model requires capacity planning based on real user workloads.
Session host
The session host is the Azure VM on which the desktop or application runs. It needs a supported image, network and DNS connectivity, an identity or domain-join configuration, AVD agents and registration, installed applications, profile handling, security configuration, and appropriate licensing.
Application group
The application group is the publishing layer. It specifies whether users receive a full desktop or selected RemoteApp programs.
Recommended Free Tools
Workspace
A workspace is the user-facing collection that exposes published desktops and applications to the client.
Identity and connectivity
Session hosts can integrate with Active Directory Domain Services, Microsoft Entra Domain Services, or Microsoft Entra ID in supported designs. Microsoft Entra joined hosts created through supported portal or ARM flows use the AADLoginForWindows VM extension. Users also need the required Azure role assignments and sign-in configuration.
AVD normally uses a reverse connection, so a basic deployment does not require inbound RDP exposed to the internet. Session hosts still need outbound access to Microsoft services, TCP 443, DNS, and directory services where applicable. RDP Shortpath can be evaluated later for suitable managed or public-network scenarios. Review the network prerequisites before deployment.
AVD versus Windows 365, Citrix and traditional VDI
| Option | Operating model | Choose it when | Trade-off |
|---|---|---|---|
| AVD | Customer-managed Azure session hosts, pooled or personal pools, consumption-based infrastructure. | You need host-pool flexibility, RemoteApp, custom images, scaling, or Azure control. | Requires Azure, identity, image, profile, networking, and cost-management expertise. |
| Windows 365 | Assigned Cloud PCs with simpler provisioning and plan-based purchasing. | You want predictable user plans and less direct VM administration. | Less control over host-pool architecture and shared-session optimization. Windows 365 Enterprise’s documented model requires Windows Enterprise, Intune, and Microsoft Entra ID P1 licensing; check current requirements and regional prices. |
| Citrix DaaS for Azure | Citrix cloud management and Workspace capabilities layered over Azure resources. | You already operate Citrix or need its provisioning, gateway, monitoring, and application-delivery features. | An additional platform and license; public documentation does not provide a universal list price. See Citrix DaaS for Azure. |
| On-premises VDI | Customer-operated physical infrastructure and control plane. | Local control, existing datacenter capacity, or requirements that prohibit cloud hosting dominate. | You own hardware lifecycle, capacity, brokering, facilities, and disaster recovery. |
AVD reduces physical infrastructure and some control-plane operations; it does not eliminate application packaging, profile management, image maintenance, identity, capacity planning, security, support, or troubleshooting.
Licensing and the real cost model
AVD has two separate cost dimensions: user access rights and Azure consumption. Eligible licenses may provide access rights or the Windows entitlement, but they do not make Azure compute free. VM runtime, disks, profile storage, networking, backup, monitoring, and other services remain billable. Use the AVD pricing page and Microsoft’s cost-estimation guidance for your region and design.
Common internal-user entitlements
- Microsoft 365 E3/E5, A3/A5, F3, or Business Premium (subject to edition and current Product Terms).
- Windows Enterprise E3/E5, Windows Education A3/A5, or Windows VDA per-user licenses.
- Windows Server session hosts use different rules, such as RDS CAL with Software Assurance or RDS User Subscription Licenses.
Confirm commercial, education, government, development/test, geography, and operating-system conditions before relying on a license. Business Premium does not cover the complete AVD deployment.
External users
External commercial users have separate per-user access pricing and enrollment requirements. Charges are based on distinct users who connect during the billing period and are separate from Azure infrastructure. Windows Server session hosts are not covered by the external-user access pricing model. See external-user enrollment and AVD licensing.
Plan a proof of concept before opening the portal
- Define test users, user personas, applications, and whether you need a full desktop or RemoteApp.
- Choose pooled or personal assignment and document expected concurrency.
- Select an Azure region, resource groups, tags, policy, logging, and a cleanup date.
- Choose AD DS, Microsoft Entra Domain Services, or Microsoft Entra join.
- Specify profile persistence, storage, security, update, and backup requirements.
- Set working hours, an automatic shutdown or scaling schedule, and a cost budget.
- List client devices and the features that must work: printing, clipboard, audio/video, Teams, drives, and peripherals.
Step-by-step AVD proof-of-concept deployment
1. Prepare Azure, identity and networking
- Use an active Azure subscription and an administrator with permission to create AVD resources, VMs, networking, storage, and identity integrations.
- Create or select a resource group and a virtual network with a subnet for session hosts.
- Configure DNS and routing. Confirm reachability to domain controllers or Microsoft Entra Domain Services when used, plus required outbound Microsoft endpoints.
- Decide whether hosts will be domain joined or Microsoft Entra joined. For an Entra-joined design, verify the supported authentication requirements,
AADLoginForWindows, and user sign-in roles. - Ensure the virtual network is in the same Azure region as the session hosts for the documented deployment flow. The detailed prerequisites are at Microsoft Learn.
2. Create the host pool and associated objects
- In the Azure portal, open Azure Virtual Desktop and start a host-pool deployment.
- Select the subscription, resource group, region, and pooled or personal type.
- Select the current management approach appropriate to the deployment.
- Configure the desktop application group, create or associate a workspace, and configure session-host deployment.
- Select a supported Windows image and an initial VM size, then configure naming, administrator credentials, identity, and networking.
- Review registration, licensing, and security settings, then deploy.
The portal can create or associate the host pool, application group, workspace, and session hosts. Microsoft also documents adding hosts later through the portal, Azure CLI, Azure PowerShell, ARM/Bicep, and REST API in Deploy Azure Virtual Desktop and Add session hosts to a host pool.
3. Validate and configure the session host
- Verify the VM is running and appears as available/registered in the host pool.
- Install business applications, updates, security baselines, Microsoft 365 optimization, and Teams components where required.
- Configure FSLogix profile containers when users need roaming or persistent profiles; validate storage permissions, SMB access, capacity, and antivirus exclusions.
- Test printing, audio, video, clipboard, drive redirection, peripherals, reconnect, disconnect, and application compatibility.
- Treat the first manually configured VM as a pilot only. Use an image-management process, such as Azure Compute Gallery, before production.
4. Publish and assign
- Assign a test user or group to the relevant application group.
- For a desktop application group, verify full desktop access; for RemoteApp, publish the required applications.
- Confirm the user has the required VM sign-in RBAC role for the chosen identity model.
- Test with a least-privilege account, not only the deployment administrator.
5. Connect from a client
- Install or open the current Windows App or another supported AVD client.
- Sign in with the assigned test account.
- Subscribe to or open the workspace.
- Launch the desktop or application and test first sign-in, reconnect, disconnect, profile persistence, and session behavior.
Client names and interface labels change, so use the current links in the AVD documentation rather than an old WVD screenshot.
Operate and automate AVD after the pilot
- Enable monitoring, alerting, diagnostic logs, and service-health procedures.
- Use image versions and update rings instead of ad-hoc changes on every host.
- Configure scaling plans and shutdown schedules around actual working hours.
- Protect profile storage and define backup and disaster-recovery objectives.
- Set Azure budgets, cost alerts, tags, policy, and an owner for idle-resource cleanup.
- Document host capacity, concurrency assumptions, support escalation, and recovery steps.
For repeatable deployments, use Bicep or ARM for resource groups, networks, host pools, workspaces, application groups, role assignments, and policies; Azure Compute Gallery for images; and automation for host registration, replacement, scaling, application publishing, tagging, and proof-of-concept teardown. Microsoft exposes cmdlets including New-AzWvdHostPool, but parameters and registration-key workflows vary by management model. Copy current syntax from the selected Microsoft reference instead of reusing an old WVD tutorial.
Troubleshoot the failures that matter
Session hosts do not register
- Check registration-token validity and expiration.
- Verify outbound connectivity, DNS, time synchronization, identity join state, and the host-pool selection.
- Inspect AVD agent and boot-loader installation and any image customization that removed required components.
Microsoft warns that skipping deployment validation commonly produces errors such as EXPIRED_MACHINE_TOKEN and missing-endpoint failures. Start with the validation and deployment checks in the deployment guidance.
The user sees a workspace but cannot launch
Check application-group assignment, workspace association, host availability, VM sign-in RBAC, Conditional Access and MFA, directory authentication, registration status, and licensing eligibility.
Rank #4
Profiles are temporary or non-persistent
Investigate the FSLogix container path, storage permissions, SMB connectivity, locks, identity mismatches, storage latency or capacity, and antivirus configuration. A desktop that loses Outlook state, OneDrive behavior, or application settings is not production-ready.
Performance is poor
Separate VM CPU or memory saturation, storage latency, profile-logon delay, network round-trip time, multimedia redirection, application behavior, and excessive concurrent sessions. There is no universal users-per-VM number; density must be tested with your personas, applications, Teams usage, VM size, storage, and performance target.
Costs exceed the estimate
- VMs remain running outside working hours.
- Hosts are oversized or personal desktops are allocated unnecessarily.
- Premium disks, profile storage, backup, egress, Log Analytics ingestion, or retention were omitted.
- Licensing was mistaken for coverage of Azure infrastructure.
Microsoft separates Azure resource consumption from licensing and notes that networking and related services can add charges; review cost-estimation guidance.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.When AVD is a good or poor fit
Strong fit
- You already use Azure and Microsoft 365.
- Users need Windows desktops or applications from multiple device types.
- Pooled multi-session delivery can improve utilization.
- You need control over images, networking, security, and scaling.
- You can operate identity, profiles, monitoring, and consumption-based infrastructure.
Potentially poor fit
- You require a fixed monthly price with minimal Azure administration.
- Applications depend on specialized peripherals, low-latency local hardware, GPUs, or unsupported drivers.
- You cannot establish dependable DNS, identity, profile storage, monitoring, and network connectivity.
- A small population would require always-on VMs that are rarely used.
Production-readiness checklist
- Identity: documented join method, least-privilege roles, MFA and Conditional Access tested.
- Network: DNS, routing, outbound endpoints, latency, and optional Shortpath design validated.
- Desktop: image pipeline, patch rings, application packaging, Teams optimization, and rollback plan.
- Profiles: FSLogix storage permissions, capacity, backup, locking, and recovery tested.
- Capacity: concurrency and density measured with representative users; no guessed VM ratio.
- Operations: monitoring, alerting, scaling, budgets, tags, support runbooks, and cleanup owners assigned.
- Resilience: regional, profile-storage, image, and identity recovery objectives documented.
- Acceptance: sign-in, reconnect, printing, multimedia, peripherals, line-of-business apps, and least-privilege access approved by pilot users.
Frequently Asked Questions
Is WVD still a separate Microsoft product?
No. Windows Virtual Desktop was renamed Azure Virtual Desktop. WVD usually refers to the same service’s former name; old tutorials may still use legacy terminology.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Is AVD free with Microsoft 365?
Eligible Microsoft 365 or Windows licenses can provide access rights or a Windows entitlement, but Azure VMs, storage, networking, profiles, backup, monitoring, and other resources still incur charges.
Best Value
Can AVD run Windows 11 multi-session?
Yes, supported Windows 10/11 Enterprise multi-session images are available, subject to current Microsoft prerequisites, licensing, and image limitations.
Do I need Active Directory for AVD?
Not universally. Supported designs can use Active Directory Domain Services, Microsoft Entra Domain Services, or Microsoft Entra joined session hosts. The selected design still requires appropriate identity, DNS, authentication, and role configuration.
Can users connect from a Mac or browser?
Supported clients include Windows, macOS, iOS, Android, the web, and other experiences, but protocol features vary by client and Windows App release.
How much does AVD cost?
There is no universal per-user price for internal deployments. Total cost combines eligible access licensing with Azure compute, storage, networking, profiles, monitoring, backup, and usage. Estimate it for your region and schedule using Microsoft’s pricing and cost guides.
The Bottom Line
Use the current name—Azure Virtual Desktop—and treat WVD as historical terminology. AVD is a strong choice when you need Azure-controlled, pooled or RemoteApp delivery and can operate the identity, profile, image, networking, security, and cost layers around the service. A small proof of concept should validate those dependencies before you commit to production.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
