Windows Virtual Desktop proof of concept

Before the Contoso cloud adoption team deploys its end-user desktops, it validates the configuration of the Azure landing zone and end-user network capacity by completing and testing a proof of concept.

The following approach to the migration process is simplified to outline a proof-of-concept implementation.

  1. Assess: the team deploys host pools by using the default virtual machine (VM) sizes. Assessment data helps the team identify the expected number of concurrent user sessions and the number of VMs required to support those concurrent sessions.
  2. Deploy: the team creates a host pool for pooled desktops by using a Windows 10 gallery image from Azure Marketplace and the sizing from assessment step 1.
  3. Deploy: the team creates RemoteApp application groups for workloads that it has already migrated.
  4. Deploy: the team creates an FSLogix profile container to store user profiles.
  5. Release: the team tests the performance and latency of application groups and deployed desktops for a sampling of users.
  6. Release: the team onboards its end users to teach them how to connect through Windows desktop client, web client, Android client, macOS client, or iOS client.


The proof of concept approach could meet some production needs, but it's built on a number of assumptions.

It's unlikely that all the following assumptions will prove to be true for any enterprise migration of Windows Virtual Desktop. The adoption team should assume that the production deployment will require a separate deployment that more closely aligns to the production requirements that it identifies during the Windows Virtual Desktop assessment. The assumptions are:

  • End users have a low-latency connection to the assigned landing zone in Azure.
  • All users can work from a shared pool of desktops.
  • All users can use the Windows¬†10 Enterprise multi-session image from Azure Marketplace.
  • All user profiles will be migrated to either Azure Files, Azure NetApp Files, or a VM-based storage service for the FSLogix profile containers.
  • All users can be described by a common persona with a density of six users per virtual central processing unit (vCPU) and 4¬†gigabytes (GB) of RAM, as per the VM sizing recommendations.
  • All workloads are compatible with Windows¬†10 Enterprise multi-session.
  • Latency between the virtual desktops and application groups is acceptable for production usage.

To calculate the cost of the Windows Virtual Desktop scenario based on the proof-of-concept configuration reference, the team uses the pricing calculator for East US, West Europe, or Southeast Asia.


These examples all use Azure Files as the storage service for user profiles.

Next steps

For guidance on specific elements of the cloud adoption journey, see: