Azure Windows Virtual Desktop Spring 2020 Release – Part 1

The Azure Windows Virtual Desktop (WVD) next version is now in public preview with new features. This next version knows as “WVDv2” and “Spring Release” and there are more changes in the first release back in 2019 Mid of WVD. The previous release is tenant-based and the new version is subscription-based and supported management UI, Azure AD group applications assign, Role-Based Control (RBAC) with Log Analytics Workspace.

Login to Azure Portal – Select Subscription – Resource Providers – Search  – Desktop

Microsoft.Desktop.Virtualization is NotRegistered – Select Register

Different between Non-ARM and ARM WVD model.

Requirements for Deploying Windows Virtual Desktop

Azure infrastructure Component

  • Azure Active Directory
  • A Windows Server Active Directory in sync with Azure Active Directory.

Licenses

OS Required license
Windows 10 Enterprise multi-session or Windows 10 Enterprise Microsoft 365 E3, E5, A3, A5, F3, Business
Windows E3, E5, A3, A5
Windows 7 Enterprise Microsoft 365 E3, E5, A3, A5, F3, Business
Windows E3, E5, A3, A5
Windows Server 2012 R2, 2016, 2019 RDS Client Access License (CAL) with Software Assurance

Supported virtual machine OS images

Windows Virtual Desktop supports the following x64 operating system images:

  • Windows 10 Enterprise multi-session, version 1809 or later
  • Windows 10 Enterprise, version 1809 or later
  • Windows 7 Enterprise
  • Windows Server 2019
  • Windows Server 2016
  • Windows Server 2012 R2

Supported Remote Desktop clients

Remote Desktop clients support Windows Virtual Desktop:

  • Windows Desktop
  • Web
  • macOS
  • iOS
  • Android (Preview)

Network Ports and URLs Allowed Windows Virtual Desktop

Address Outbound TCP port Purpose Service Tag
*.wvd.microsoft.com 443 Service traffic WindowsVirtualDesktop
mrsglobalsteus2prod.blob.core.windows.net 443 Agent and SXS stack updates AzureCloud
*.core.windows.net 443 Agent traffic AzureCloud
*.servicebus.windows.net 443 Agent traffic AzureCloud
prod.warmpath.msftcloudes.com 443 Agent traffic AzureCloud
catalogartifact.azureedge.net 443 Azure Marketplace AzureCloud
kms.core.windows.net 1688 Windows activation Internet
wvdportalstorageblob.blob.core.windows.net 443 Azure portal support AzureCloud

Lists optional URLs that your Azure virtual machines can have access to:

Address Outbound TCP port Purpose Service Tag
*.microsoftonline.com 443 Authentication to MS Online Services None
*.events.data.microsoft.com 443 Telemetry Service None
www.msftconnecttest.com 443 Detects if the OS is connected to the internet None
*.prod.do.dsp.mp.microsoft.com 443 Windows Update None
login.windows.net 443 Login to MS Online Services, Office 365 None
*.sfx.ms 443 Updates for OneDrive client software None
*.digicert.com 443 Certificate revocation check None

 

Remote Desktop clients must have access to the following URLs:

Address Outbound TCP port Purpose Client(s)
*.wvd.microsoft.com 443 Service traffic All
*.servicebus.windows.net 443 Troubleshooting data All
go.microsoft.com 443 Microsoft FWLinks All
aka.ms 443 Microsoft URL shortener All
docs.microsoft.com 443 Documentation All
privacy.microsoft.com 443 Privacy statement All
query.prod.cms.rt.microsoft.com 443 Client updates Windows Desktop

 

Deploy Windows Virtual Desktop Step by Step

Search Resources – Windows Virtual Desktop – Create a Host Pool

To start creating your new host pool:

  1. Enter a unique name for your host pool.
  2. In the Location select the region where you want to create the host pool from the drop-down menu.

(Azure geography associated with the regions you selected is where the metadata for this host pool and its related objects will be stored.)

  1. Under Host pool type, select whether your host pool will be Personal or Pooled.
  2. Host Pool Type:

For the Host pool type, select Pooled (user will login to random available VM in the hostpool every time) or Personal (dedicated assigned VM for user).

Eenter the following information:

  • For Max session limit, enter the maximum number of users you want load-balanced to a single session host.
  • For Load balancing algorithm, choose either breadth-first or depth-first, based on your usage pattern.
  1. Select Next: VM details.

 

Virtual machine details

  1. Choose the resource group where you want to create virtual machines.
  2. Choose the Virtual machine region where you want to create the virtual machines.
  3. Next, choose the size of the virtual machine you want to create
  4. Under Number of VMs, provide the number of VMs you want to create for your host pool.
  5. provide a Name prefix to name the virtual machines the setup process creates. The suffix will be – with numbers starting from 0.
  6. Next, choose the image that needs to be used to create a virtual machine. You can choose either Gallery or Storage Blob.
  • If you choose Gallery, select one of the recommended images from the drop-down menu:
  • Windows 10 Enterprise multi-session, Version 1909 + Office 365 ProPlus – Gen 1
  • Windows 10 Enterprise multi-session, Version 1909 – Gen 1
  • Windows Server 2019 Datacenter – Gen1
  1. Choose what kind of OS disks
  2. Under Network and security, select the virtual network and subnet where you want to put the virtual machines you create.
  3. Select what kind of security group you want: Basic, Advanced, or None.
  4. select whether you want the virtual machines to be joined to a specific domain and organizational unit.
  5. Under Administrator account, enter the credentials for the Active Directory Domain admin of the virtual network you selected.

Select Workspace or Create New Workspace – Click Next

Optionally you can add Tags – Click Next

Click Next: Review + Create