Azure Virtual Desktop Pricing Explained (2026)

Azure Virtual Desktop (AVD) is often marketed as "the free VDI control plane" — and technically, the control plane is free. But the control plane is not where the cost lives. This article breaks down the real total cost of ownership for AVD, with worked examples at 100 and 500 users.

Looking for a quick pricing comparison instead? See our AVD pricing breakdown with worked cost examples and a comparison table.

How AVD Pricing Works

AVD pricing has three components. Microsoft charges nothing for the AVD service itself — the brokering, load balancing, and management are included at no additional cost. Your costs come entirely from Azure infrastructure: the virtual machines that host desktops, the storage that holds user profiles and disk images, and the networking that connects users to their desktops.

This sounds like it should be cheap. In practice, the cost depends entirely on how you configure the infrastructure, how many hours per day users are connected, and how much compute and storage each user requires.

The Three Cost Components

Component 1: Windows Licensing

AVD requires Windows licenses that support multi-session. This is the most commonly misunderstood cost.

• Windows 10/11 Enterprise multi-session: This edition is available only through Azure (or via AVD with appropriate Microsoft 365 licensing). It is not available for purchase as a standalone retail or volume license. You need an eligible license: Microsoft 365 E3/E5, Microsoft 365 A3/A5, or Windows 10/11 Enterprise E3/E5 with Software Assurance.
• Windows Server 2022: If you use Windows Server as the VDA OS (common for task-worker scenarios), you need Windows Server licensing plus RDS CALs. This is cheaper than Windows 10/11 multi-session licensing but provides a server-style desktop experience.
• Existing licenses: If your organisation already has Microsoft 365 E3/E5 or Windows Enterprise with Software Assurance, you may already have the licensing required for AVD at no additional cost. This is the single biggest factor in whether AVD is cost-effective for your organisation.

Component 2: Compute (Azure VMs)

This is typically 60-80% of your total AVD cost. The VM size you choose directly determines your per-user cost.

Common VM families for AVD:

• B-series (Burstable): Cheapest option. B2s (~$15/mo), B2ms (~$30/mo). Suitable for task workers (Office, web browsing, line-of-business apps). Not suitable for power users or GPU workloads.
• D-series (General Purpose): D2s_v5 (~$70/mo), D4s_v5 (~$140/mo). Good balance of CPU and memory. Suitable for most knowledge workers. D2s_v5 supports 2-3 concurrent AVD users; D4s_v5 supports 4-6.
• E-series (Memory Optimised): E2s_v5 (~$90/mo), E4s_v5 (~$180/mo). For users who need more RAM (developers, data analysts).
• N-series (GPU): NC6 (~$220/mo), NV6 (~$270/mo). For graphics-intensive workloads (CAD, video editing). GPU VMs are expensive and should only be used for users who genuinely need them.

Azure offers pay-as-you-go, 1-year reserved, and 3-year reserved pricing. Reserved instances reduce compute costs by 30-50% but require a 1 or 3 year commitment.

Component 3: Storage and Networking

Storage costs are smaller than compute but not negligible:

• OS Disk: Each AVD VM needs an OS disk. Premium SSD P10 (128 GB) costs ~$6/month. Most deployments use 128-256 GB per VM.
• User Profiles (FSLogix): User profile containers (VHDX files) are stored on Azure Files or Azure NetApp Files. A 10 GB profile on Azure Files Premium costs ~$1.50/month per user. Azure NetApp Files is faster but more expensive.
• FSLogix Overflow: If profiles exceed the container size, overflow data goes to a file share. This adds storage cost and can degrade performance.
• Egress: Data leaving Azure (users downloading files, accessing the internet through the AVD session) incurs egress charges. This varies by region and volume but is typically $0.087/GB for the first 10 TB.

Networking costs are minimal for internal Azure traffic but can add up for users connecting from outside Azure (which is most users).

Worked Example: 100 Users

Assumptions: 100 knowledge workers, Microsoft 365 E3 licenses (Windows licensing already covered), D2s_v5 VMs (2 vCPU, 8 GB RAM), 3-year reserved instances, standard 8-hour workday, single Azure region, Azure Files Premium for profiles.

• Compute: ~35 D2s_v5 VMs (3:1 user-to-VM ratio for 8-hour usage). D2s_v5 3-year reserved: ~$49/mo. 35 VMs × $49 = $1,715/mo
• Storage (OS Disks): 35 VMs × 128 GB Premium SSD = ~$210/mo
• Storage (Profiles): 100 users × 10 GB × $0.15/GB = ~$150/mo
• Networking/Egress: ~$50-100/mo (varies by usage)
• Backup: ~$50/mo (Azure Backup for VM snapshots)
• Total: ~$2,175-2,225/mo → ~$22/user/month

Worked Example: 500 Users

Same assumptions as above, scaled to 500 users.

• Compute: ~175 D2s_v5 VMs. 175 × $49 = $8,575/mo
• Storage (OS Disks): 175 × $6 = ~$1,050/mo
• Storage (Profiles): 500 × $1.50 = ~$750/mo
• Networking/Egress: ~$200-400/mo
• Backup: ~$200/mo
• Total: ~$10,775-10,975/mo → ~$22/user/month

The per-user cost stays roughly constant at scale because the cost structure is linear. The key lever is the VM size and user-to-VM ratio, not economies of scale.

Hidden Costs Most People Miss

• Azure Monitor / Log Analytics: Diagnostic logging and monitoring are not free. Log Analytics ingestion costs ~$2.30/GB after the first 5 GB/month free tier. A 500-user deployment can easily generate 50-100 GB/month of diagnostic logs.
• Azure Active Directory (Entra ID) P1/P2: If you need conditional access, MFA, or identity protection for AVD, you need Entra ID P1 ($6/user/mo) or P2 ($9/user/mo). Many organisations already have this through Microsoft 365.
• FSLogix profile management overhead: Managing profile containers requires monitoring for growth, capacity planning, and periodic cleanup. Profiles that grow beyond expectations can increase storage costs significantly.
• Operational staff: AVD requires Azure-skilled administrators. Unlike Citrix or Horizon where the vendor provides a management console, AVD management is done through the Azure portal, ARM templates, or PowerShell. The learning curve for teams new to Azure is real.
• Multi-region redundancy: If you need disaster recovery or geographic redundancy, you are doubling (or tripling) your compute and storage costs.

AVD vs Citrix: Cost Comparison

For the same 100-user deployment described above:

• AVD: ~$22/user/month (control plane free, compute + storage)
• Citrix Cloud + Azure: ~$45-65/user/month (Citrix licensing $15-30/user/mo + Azure compute $20-35/user/mo + Citrix ADC ~$3-5/user/mo)
• Citrix on-premises: Higher upfront CapEx, lower ongoing OpEx at scale. 3-year TCO can be competitive with AVD for large deployments.

AVD is cheaper on a per-user basis when Windows licensing is already covered. Citrix provides more management features, better protocol performance, and a more mature cloud control plane. The cost gap narrows as you add Citrix-like features to AVD (third-party profile management, monitoring, gateway services).

How to Reduce AVD Costs

1. Use reserved instances. 1-year reservations save ~30%; 3-year reservations save ~50% versus pay-as-you-go. If you are committed to AVD for 3+ years, this is the single biggest cost lever.
2. Right-size your VMs. Most task workers do not need D4s_v5. Profile your actual usage and use the smallest VM that meets your requirements.
3. Implement auto-shutdown. Shut down VMs outside business hours. Azure Automation can schedule shutdown/startup for a few dollars per month.
4. Use B-series for task workers. B2ms provides burstable performance at 1/3 the cost of D-series. Sufficient for Office, web, and light LOB applications.
5. Optimise FSLogix profiles. Set profile size limits, exclude non-essential folders (AppData\Local\Temp, browser caches), and use Azure Files Standard instead of Premium where latency is not critical.
6. Leverage existing licenses. Ensure you are using your Microsoft 365 E3/E5 or Windows Enterprise licenses for AVD rather than paying separately.

Is AVD Right for Your Budget?

AVD is cost-effective when:

• You already have Microsoft 365 E3/E5 or Windows Enterprise licensing (eliminates the biggest cost variable).
• Your workloads are standard Office and LOB applications (no GPU or high-compute requirements).
• You have Azure-skilled staff or are willing to invest in training.
• You want a cloud-native solution without on-premises infrastructure.

AVD may not be the cheapest option when:

• You do not have existing Microsoft licensing — the Windows licensing cost can double your total.
• Your users need GPU acceleration — Azure GPU VMs are expensive.
• You need advanced VDI features (app layering, granular policy, session recording) that require third-party add-ons.

For a head-to-head comparison with Citrix and other alternatives, see our AVD vs Citrix guide, our complete platform comparison, or our VDI cost comparison. For a lower-cost remote access alternative, see our Splashtop pricing guide.

Related Articles

• AVD vs Citrix
• Application Virtualization vs VDI
• VMware Horizon Alternatives