Understand and estimate costs for Azure Virtual Desktop
Azure Virtual Desktop costs come from two sources: underlying Azure resource consumption and licensing. Azure Virtual Desktop costs are charged to the organization that owns the Azure Virtual Desktop deployment, not the end-users accessing the deployment resources. Some licensing charges must be paid in advance. Azure meters track other licenses and the underlying resource consumption charges based on your usage.
The organization who pays for Azure Virtual Desktop is responsible for handling the resource management and costs. If the owner no longer needs resources connected to their Azure Virtual Desktop deployment, they should ensure those resources are properly removed. For more information, see How to manage Azure resources by using the Azure portal.
This article explains consumption and licensing costs, and how to estimate service costs before deploying Azure Virtual Desktop.
Azure resource consumption costs
Azure resource consumption costs are the sum of all Azure resource usage charges that provide users desktops or apps from Azure Virtual Desktop. These charges come from the session host virtual machines (VMs), plus resources shared by other products across Azure that require running more infrastructure to keep the service available, such as storage accounts, network data egress, and identity management systems.
Session host costs
Session hosts are based on virtual machines (VMs), so the same Azure Compute charges and billing mechanisms as VMs apply. These charges include the following components:
- Virtual machine instance.
- Storage for managed disks for the operating system and any extra data disks.
- Network bandwidth.
Of the charges for these components, virtual machine instances usually cost the most. To mitigate compute costs and optimize resource demand with availability, you can also use Azure savings plans.
Identity provider costs
You have a choice of identity provider to use for Azure Virtual Desktop, from Microsoft Entra ID only, or Microsoft Entra ID in conjunction with Active Directory Domain Services (AD DS) or Microsoft Entra Domain Services. The following table shows the components that are charged for each identity provider:
| Identity provider | Components charged |
|---|---|
| Microsoft Entra ID only | Free tier available, licensed tiers for some features, such as conditional access. |
| Microsoft Entra ID + AD DS | Microsoft Entra ID and domain controller VM costs, including compute, storage, and networking. |
| Microsoft Entra ID + Microsoft Entra Domain Services | Microsoft Entra ID and Microsoft Entra Domain Services, |
Accompanying service costs
Depending on which features your use for Azure Virtual Desktop, you have to pay for the associated costs of those features. Some examples might include:
| Feature | Associated costs |
|---|---|
| Azure Virtual Desktop Insights | Log data in Azure Monitor. For more information, see Estimate Azure Virtual Desktop Insights costs. |
| App attach | Application storage, such as Azure Files or Azure NetApp Files. |
| FSLogix profile container | User profile storage, such as Azure Files or Azure NetApp Files. |
Licensing costs
In the context of providing virtualized infrastructure with Azure Virtual Desktop, internal users (for internal commercial purposes) refers to people who are members of your own organization, such as employees of a business or students of a school, including external vendors or contractors. External users (for external commercial purposes) aren't members of your organization, but your customers where you might provide a Software-as-a-Service (SaaS) application using Azure Virtual Desktop.
Licensing Azure Virtual Desktop works differently for internal and external commercial purposes:
If you're providing Azure Virtual Desktop access to internal commercial purposes, you must purchase an eligible license for each user that accesses Azure Virtual Desktop.
If you're providing Azure Virtual Desktop access external commercial purposes, per-user access pricing lets you pay for Azure Virtual Desktop access rights on behalf of external users. You must enroll in per-user access pricing to build a compliant deployment for external users. You pay for per-user access pricing through an Azure subscription.
To learn more about the different options, see License Azure Virtual Desktop.
View costs after deploying Azure Virtual Desktop
Once you deploy Azure Virtual Desktop, you can use Microsoft Cost Management to view your billing invoices. Users in your organization like billing admins can use cost analysis tools and find Azure billing invoices through Microsoft Cost Management to track monthly Azure Virtual Desktop consumption costs under your Azure subscription or subscriptions. You can also Tag Azure Virtual Desktop resources to manage costs.
If you're using per-user access pricing, costs appear each billing cycle on the Azure billing invoice for any enrolled subscription, alongside consumption costs and other Azure charges.
If you Use Azure Virtual Desktop Insights, you can gain a detailed understanding of how Azure Virtual Desktop is being used in your organization. You can use this information to help you optimize your Azure Virtual Desktop deployment and reduce costs.