As far as I understand there are two ways of licensing a WVD user, either giving the user a M365 license or pointing the Windows 10 multisession host at a TS licensing host the old-fashioned way. Right? How about mixed mode, where some users have the M365 license and others only a O365 E3 license? Will using a M365 license get rid of the "host not licensed" message? I really would like documentation that explains how this scenario works.

Hi Oletho, It's very similar to how licensing works on-premises. If you are using Windows Server RDSH, you need a RDS CAL for every user that connects. If you are using a Windows Client OS, you are covered with your Windows E3 (or better) Per User licensing. O365 licensing is not sufficient for Windows 10 multi-session, it needs to be for a Windows OS. Since, from a licensing perspective, Windows 10 Multi-session is considered a client OS - you don't need an RDS CAL and there is no need to configure a TS licensing host. Now you might be getting pop-ups about a grace period, that's something we are fixing. For 1903 builds that should go away in a couple of weeks. For 1809 builds it will take longer and the best workaround is using the latest image from the gallery which has a grace period of 800 days. Thanks, Pieter

Windows Virtual Desktop (WVD) is a combination of licensing entitlements (e.g free Windows 7 ESU) and net-new technology which includes the management plane featuring things like AAD support, reverse connect, broker, gateway. licensing etc. All of this is included with Windows 10 Enterprise E3 Per User” licenses or better (e.g. Windows 10 Enterprise E5 or Microsoft 365 E3, E5, F1, or Business) or RDS CALs. From that point on, WVD supports multiple operating systems as RDSH including Windows Client and Windows Server. You will need Per User Windows licenses for a client OS and RDS CALs for a Server OS. Hope this clarifies.

So for my O365 E3 users I need to configure a TS licensing server on the Windows multisession host, which makes good sense. And on this same host a Windows E3 user will not occupy a TS license? Just want to be sure how this mixed license scenario works. Thanks.

You cannot use Windows 10 Enterprise multi-session if a user is only licensed for Office. They need to be licensed for Windows. Either through E3, E5, Business, F1 or M365 E3/E5 Per User. What endpoints are you using? Is that Windows? If so, switching to Windows Per User licensing for everyone might be the best option.

So TS/RDS CALs is not an option? Now I am confused. According to your blog “Getting started with Windows Virtual Desktop”: Organizations with “Windows 10 Enterprise E3 Per User” licenses or better (e.g. Windows 10 Enterprise E5 or Microsoft 365 E3, E5, F1, or Business) or RDS CALs can use Windows Virtual Desktop for no additional charge apart from Azure compute/storage and network usage billing In my POC tenant I have Windows 10, Mac and iOS endpoints. Some of my customers have M365 licenses, most have O365 and then some have mixed.

Mixed licensing for WVD? | Microsoft Community Hub

PieterWigleven
Microsoft
Jun 20, 2019
Hi Oletho, It's very similar to how licensing works on-premises. If you are using Windows Server RDSH, you need a RDS CAL for every user that connects. If you are using a Windows Client OS, you are covered with your Windows E3 (or better) Per User licensing. O365 licensing is not sufficient for Windows 10 multi-session, it needs to be for a Windows OS. Since, from a licensing perspective, Windows 10 Multi-session is considered a client OS - you don't need an RDS CAL and there is no need to configure a TS licensing host. Now you might be getting pop-ups about a grace period, that's something we are fixing. For 1903 builds that should go away in a couple of weeks. For 1809 builds it will take longer and the best workaround is using the latest image from the gallery which has a grace period of 800 days. Thanks, Pieter
- Oletho
  Copper Contributor
  Jun 20, 2019
  
  So for my O365 E3 users I need to configure a TS licensing server on the Windows multisession host, which makes good sense.
  
  And on this same host a Windows E3 user will not occupy a TS license?
  
  Just want to be sure how this mixed license scenario works. Thanks.
  - PieterWigleven
    Microsoft
    Jun 20, 2019
    You cannot use Windows 10 Enterprise multi-session if a user is only licensed for Office. They need to be licensed for Windows. Either through E3, E5, Business, F1 or M365 E3/E5 Per User. What endpoints are you using? Is that Windows? If so, switching to Windows Per User licensing for everyone might be the best option.

Forum Discussion

Mixed licensing for WVD?

Share

Resources