Azure Virtual Desktop Licensing Options and Costs Explained

Azure Virtual Desktop licensing options can be a bit overwhelming at first, but don't worry, I've got you covered.

There are two main licensing options: Microsoft 365 and Windows Virtual Desktop.

Azure Virtual Desktop is a cost-effective solution, with a pay-as-you-go pricing model that allows you to only pay for what you use.

With Azure Virtual Desktop, you can choose from a range of Windows 10 and Windows 11 versions, including Windows 10 Enterprise and Windows 11 Enterprise.

The cost of Azure Virtual Desktop is determined by the number of sessions, with a base price of $7 per session per month.

Azure Virtual Desktop pricing can be complex, but understanding the different components can help you estimate costs accurately.

Per-user access pricing for external commercial purposes is available, where you pay for access rights for external users through your enrolled Azure subscription. You only pay for users who actually used the service, and charges are determined automatically each billing cycle.

There are two price tiers for Azure Virtual Desktop per-user access pricing: Apps and Desktops + apps. Charges are flat per-user access charges, regardless of how many hours a user used the service during that billing cycle.

You can also incur charges for users with separate assigned licenses that otherwise entitle them to Azure Virtual Desktop access. To avoid effectively paying twice for internal users, it's recommended to give them access through a separate subscription that isn't enrolled in per-user access pricing.

Azure Virtual Desktop issues at most one access charge for a given user in a given billing period, even if the user accesses Azure Virtual Desktop resources across multiple subscriptions in the same tenant.

Azure Virtual Desktop pricing consists of several components, including Virtual Machine (VM) Costs and User Access Licenses (CALs). VM costs depend on factors such as VM type, region, scalability, and VM size and performance capabilities.

User Access Licenses (CALs) are required to access AVD, and come in two types: per-user and per-device CALs. Per-user CALs allow users to access their virtual desktops from any device, while per-device CALs enable multiple users to share a single device.

To leverage Azure Virtual Desktop, certain Microsoft licenses are required, including Windows 10 Enterprise Multi-Session, Microsoft 365 E3/E5, Remote Desktop Services (RDS) CALs, and Microsoft Azure Hybrid Benefit.

Azure infrastructure costs, such as Storage Costs and Network Costs, should also be considered when using Azure Virtual Desktop. Storage costs depend on factors such as capacity, redundancy options, and data transfer, while network egress charges may apply when users access data or applications from the AVD environment.

Here are the primary license types required for Azure Virtual Desktop:

Azure Virtual Desktop offers two types of licenses, each with its own set of features and pricing. The first type of license is eligible for internal purposes only, meaning it doesn't grant permission for external commercial purposes, even if you create identities in your own Microsoft Entra tenant.

You can choose between licensing channels for billing, which is a fixed cost per user each month regardless of user behavior. Alternatively, you can opt for pay-as-you-go through an Azure meter, billed to an Azure subscription, which depends on user behavior.

Here's a summary of the two types of licenses in a table:

Azure Virtual Desktop requires a supported operating system, such as Windows 10 or 11 Enterprise, and the right licenses.

When choosing a licensing option for Azure Virtual Desktop, it's essential to consider the type of access you need. You can choose between two types of licenses.

One key difference between the two licenses is that the first one is only eligible for internal purposes, which means it's not suitable for external commercial use. This license grants permission for users within your own organization, but not for external contractors or partners.

The other license is specifically designed for external commercial purposes, but it doesn't grant access to members of your own organization or contractors for internal business purposes.

In terms of billing, the first license is typically billed through licensing channels, while the second license is billed on a pay-as-you-go basis through an Azure meter.

Your user behavior also plays a role in the cost, as the first license has a fixed cost per user each month regardless of user behavior. In contrast, the second license charges per user based on their behavior.

If you're considering other products, it's worth noting that the first license is dependent on the type of license you choose, while the second license only includes access rights to Azure Virtual Desktop and FSlogix.

Here's a comparison of the two licenses:

The new Management portal integration is completely built on ARM, which means that permissions can be managed via role-based access control (RBAC).

All the deployment objects of WVD, such as host pools and workspaces, are objects within your Azure subscription, making it easier to manage and automate your environment.

The biggest difference between WVD non-ARM and ARM is the management and automation capabilities.

With ARM, you can manage all deployment objects within your Azure subscription, but with WVD non-ARM, it's a different story.

In WVD non-ARM, deployment objects are not objects within your Azure subscription, making it harder to manage and automate your environment.

The 2020 spring release of WVD ARM brings a lot of changes and improvements over the current WVD non-ARM.

One of the most important differences is the ability to manage permissions via role-based access control (RBAC).

Azure Virtual Desktop offers full device support, allowing employees to access virtual desktops and applications from any device. Whether it's a PC, Mac, or mobile device, the experience is seamless.

Running in the Azure cloud environment, AVD works with all existing applications and devices. This means you can use your organization's existing infrastructure without any issues.

Mobile support is available for Android and iOS devices, so employees can access virtual desktops on their personal phones or tablets. HTML 5 support is also available, enabling access to remote desktop environments and applications from any modern web browser.

The experience is the same regardless of the device used, with apps looking and feeling like local apps. This means employees can pin apps to the taskbar or access them from the Start menu just like they would with local apps.

Azure Active Directory plays a crucial role in Azure Virtual Desktop by enabling users to connect to a session host.

You can connect to a session host through an Azure AD tenant, which is a convenient option for many users.

Azure AD tenants offer a high level of security and scalability, making them an attractive choice for organizations of all sizes.

Azure Virtual Desktop also allows users to connect to a session host through an Active Directory domain, which can be enabled using Active Directory Domain Services.

Virtual App Delivery has opened up new possibilities for organizations looking to provide their people with access to all their apps on any device.

Recent advancements in Virtual App Delivery (VAD) have made it possible to access all applications remotely from any device, regardless of the operating system.

This approach eliminates the need for an entire virtual desktop infrastructure, offering increased flexibility and reduced complexity.

Users can access all of their applications, including Windows, Linux, SaaS, and internal web apps, from any device.

A dramatic reduction in cost is also a significant benefit of Virtual App Delivery.

VAD allows users to access their applications on any device, regardless of the operating system, eliminating the need for an entire virtual desktop infrastructure.

To use Azure Virtual Desktop, you'll need a supported operating system and licenses. Windows 10 or 11 Enterprise, or Windows Server, are all compatible options.

A virtual network is required for a successful connection to Azure Virtual Desktop, which must be in the same Azure region as the session host. Additionally, the virtual network needs to be able to connect to domain controllers and DNS servers if you're using AD DS or Azure AD DS.

Session hosts and users must also be able to connect to the Azure Virtual Desktop service, which uses TCP on port 443 to a specific list of URLs. These URLs can be found in the required URL list.

To access Azure Virtual Desktop, you'll need a remote desktop client, which is available for various operating systems and devices, including Windows, macOS, iOS, and iPad.

Here are the eligible licenses to use Azure Virtual Desktop:

Microsoft licenses are required to use Azure Virtual Desktop, and these licenses determine the pricing structure. The primary license types are Windows 10 Enterprise Multi-Session, Microsoft 365 E3/E5, Remote Desktop Services (RDS) CALs, and Microsoft Azure Hybrid Benefit.

Azure Virtual Desktop offers two deployment options: persistent and non-persistent virtual desktops. These options have significant implications on pricing.

Persistent virtual desktops retain user-specific settings, applications, and data across sessions. They're ideal for users who require a personalized experience.

Non-persistent virtual desktops do not retain user-specific changes between sessions. They offer a fresh desktop experience with each login.

Non-persistent desktops are more cost-effective in terms of storage, as they utilize shared images and require less disk space per user. This can be a significant advantage for organizations with a large number of users.

Here's a quick comparison of the two options:

Understanding these options is crucial for making informed choices and effectively managing expenses. Remember to consult with Microsoft documentation and licensing experts for the most accurate and up-to-date information on Azure Virtual Desktop pricing and licensing policies.