With the upcoming general availability of Microsoft’s Azure-only Windows Virtual Desktop (WVD) service later this year, the most common question we hear from MSPs is how to think through its pricing and the resulting impact on an MSPs’ business. To answer this question, it is important to break WVD down into its sub-components and consider the costs of each as compared to other alternatives, such as utilizing Remote Desktop Services (RDS).
First, it is important to point out that contrary to how some are portraying it in the market, WVD is not a packaged virtual desktop offer from Microsoft. When WVD releases into the market, you won’t be able to purchase a virtual desktop from Microsoft. WVD is a set of Microsoft technologies available to IT departments and cloud service providers to build virtual desktop offers for customers and users. This is an important distinction.
When talking about the costs of WVD, it’s important to consider these three primary building blocks:
1. Azure infrastructure to run the desktops and apps (i.e. WVD session hosts)
2. WVD Management Services (i.e. Control Plane)
3. Software licensing (i.e. Windows 10 Enterprise)
Let’s examine the costs associated with each of these while comparing them to the legacy RDS technology.
Azure infrastructure to run the desktops and apps (i.e. WVD session hosts)
WVD supports two types of desktops:
• Personal (1-to-1 assignment between a user and desktop VM)
• Pooled (many-to-1 assignment between users and desktop VM)
WVD can also be used to deliver individual apps instead of full published desktops. In all of these scenarios (personal, pooled, apps), there are VMs running Windows (typically Windows 10 Enterprise multi-session) that provide this functionality. These session host VMs run inside of a customer’s Azure subscription and require the use of compute, networking and storage resources in Azure.
The consumption cost for Azure resources supporting WVD session hosts VMs will depend on many factors such as:
• Average number of users per vCPU (e.g. 3 users per vCPU)
• Average GB of RAM per user (e.g. 1GB RAM per user)
• Azure VM family (e.g. B, Dsv3, Esv3, NVv2)
• Type of storage used by each VM (e.g. Premium SSD, Standard SSD, Standard HDD)
• OS disk capacity of each VM (e.g. 128GB, 256GB, 1TB)
• Amount of data transferred out of Azure per user (e.g. 25GB/month)
• Other infrastructure services such as backup, replication, VPN, etc.
• Reserved Instance use (e.g. pay-as-you-go, 1-year or 3-year reservations)
The cost of this Azure infrastructure is largely the same if you were using RDS to deliver Windows desktops using “desktop experience” rather than the native Windows 10 look and feel that you get with WVD. From a resource utilization and cost perspective, this component of WVD is very much similar to the cost of Azure infrastructure to run RDS session hosts, rather than WVD session hosts. (Note: this is assuming Windows Server 2016 VMs running RD Session Host roles have Azure Hybrid Usage enabled).
WVD Management Service (i.e. Control Plane)
The job of a control plane is to orchestrate the creation and management of desktop and app session hosts, authenticate users who are logging into their desktops and to determine where to “land” a user’s desktop connection (meaning what desktop VM to patch the user through to). In the RDS world, this was handled through a number of “RDS roles” namely: RD License Server, RD Web, RD Webclient, RD Connection Broker and RD Gateway. With WVD, it is no longer necessary to install and manage any of these roles as they are now part of the WVD Management Service, which is hosted in Azure and operated by Microsoft. It is a PaaS product that can be controlled via RestAPI, PowerShell and soon the Azure admin portal.
This is a key distinction between legacy RDS deployments and WVD. With RDS, IT departments and MSPs had to build one or more domain-joined Windows Server VMs, and then install and configure the RDS roles on those VMs. This meant that additional Azure infrastructure (i.e. cost) was needed to support the control plane. With WVD, Microsoft has taken over the responsibility for the control plane and there is not an incremental cost for this service. Not to say that it is free, but rather that it is included with a software license subscription.
Software licensing (i.e. Windows 10 Enterprise)
WVD Management Service that is hosted and managed by Microsoft in Azure is a benefit that comes at no additional charge with a subscription to Windows 10 Enterprise license. There are multiple ways to purchase a Windows 10 Enterprise subscription. Including:
1. Microsoft 365 (E3, E5, A3, A5, Business)
2. Windows (E3, E5, A3, A5, Business)
3. Windows 10 Enterprise VDA
In the legacy RDS world, you would need to purchase a Windows Server license and an RDS Subscriber Access License to create a desktop deployment in Azure and use additional VMs to run and manage the RDS roles.
Let’s summarize the above with a table that compares RDS virtual desktops in Azure versus WVD using the Windows 10 Enterprise multi-session operating system.
How should an MSP decide on the right path forward?
There are many technical reasons to choose WVD over legacy RDS. Among them are:
• WVD is a new, up-to-date and very exciting technology from Microsoft
• WVD allows for native Windows 10 desktop instead of a Windows 10 “desktop experience” with RDS
• WVD includes profile management technology from FSLogix
• WVD management service is managed by Microsoft and is a PaaS service
• WVD supports OneDrive and indexed search in pooled desktops
Some MSPs may choose to continue using RDS over WVD for the following reasons:
• RDS is a mature, well understood and market tested solution
• Applications that were written for RDS on Server OS may not work in Windows 10 Enterprise multi-session right away
• Customers and service providers may want to retain full ownership of not just the desktop VMs but also the control plane (i.e. RDS roles)
• RDS can be used both on-premise and in Azure while WVD is Azure only
Let’s assume a customer feels indifferent between WVD and RDS based on the technical reasons above. If the primary decision factor is based on cost, then how would they decide? That depends on whether the customer already owns a subscription to Windows 10 Enterprise under any of the Microsoft licensing programs mentioned above.
• Customer already owns Windows 10 Enterprise subscription or is going to be licensing Microsoft 365 anyway
o WVD is the winner on cost
o There is no additional licensing cost for WVD Management Service
o There is no need for any additional Azure VMs to run the control plane
• Customer does not own Windows 10 Enterprise subscription and is not planning on purchasing it for any reason other than potentially using WVD
o RDS and WVD tie on cost
o Incremental cost of a Windows 10 Enterprise subscription is $7 per user/month and the incremental cost of RDS SAL & Server 2016 license is roughly $6 per user/month (assuming CSP Software Subscriptions are used to license RDS and Server OS)
o For sizable deployments, the incremental cost of RDS infrastructure VMs will average out to $1 to $2 per user/month making the true cost WVD and RDS about the same. In small deployments (<25 users), where there aren’t enough users to amortize the cost of RDS infrastructure VMs across, RDS will be slightly more expensive
WVD holds the promise to simplify the licensing and deployment of virtual desktops in Azure. With many organizations moving toward Microsoft 365 and Azure, it is a natural and relatively low-cost way to deploy desktops and applications in the cloud, unlike anything else that is available from other public cloud providers.
At Nerdio, we look forward to continuing to empower MSPs to build successful and profitable cloud practices in Microsoft Azure.