Forum Discussion

Oletho's avatar
Oletho
Copper Contributor
Jun 20, 2019

Mixed licensing for WVD?

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. Rig...
PieterWigleven's avatar
PieterWigleven
Former Employee
Jun 26, 2019
It might be good to wait until we have rolled-out our management plane to New Zealand and we announced AAD support. The first will make sure the traffic isn't routed via the US and enhance performance. The second will remove the requirement for AD in Azure saving costs. It's hard to give timeliness as we are in planning phase but I'm personally expecting somewhere Q1 of next calendar year. Until that, the existing setup is probably best.
sarahpotrick2573's avatar
sarahpotrick2573
Copper Contributor
Jan 27, 2020

Hi PieterWigleven Pieter Wigleven (WINDOWS) 

I have a customer whose previous environment is in RDS and now he is trying out WVD. The customer already has an O365 E3 license and i have deployed a WVD environment for the customer using ADDS, so just wanted to confirm the customer has E3 license, so will he will be still charged for the windows enterprise multi-session that i have deployed for him. Do i need to enable any  client OS Licensing on WVD?And if so how am i suppose  to do it?

  • seanhannah's avatar
    seanhannah
    Copper Contributor
    Mar 27, 2020

    "For Office 365 ProPlus, you need an appropriate license just like on-premises: either Office E3 or higher" or just an Office365 ProPlus licence 😉 

     

    Do you know if Office Standard runs in WVD (presume it does) and would it be licenced in same way as standard VDI solutions i.e. need Software Assurance or SPLA licence?

  • PieterWigleven's avatar
    PieterWigleven
    Former Employee
    Feb 07, 2020

    sarahpotrick2573 Yes, with the note that WVD supports multiple operating systems and depending what you spin up, the requirements are slightly different. 

     

    In essence it's the same as on-premises: 

    - If you spin up a Windows Server, it requires a RDS CAL for the user that connects. 

    - If you spin up a Windows client OS (including multi-session), it requires the user has a Windows E3 Per User license.

     

    For Office 365 ProPlus, you need an appropriate license just like on-premises: either Office E3 or higher.

     

  • sarahpotrick2573's avatar
    sarahpotrick2573
    Copper Contributor
    Feb 07, 2020

    ok got it. As of now  i have a customer who is using office365 E3, so as u said i would need to get Windows enterprise E3 or higher per user for all of the users who will be connecting to WVD?PieterWigleven 

  • AndreReis's avatar
    AndreReis
    Copper Contributor
    Feb 05, 2020

    evasse Could you help with my question above?

  • AndreReis's avatar
    AndreReis
    Copper Contributor
    Feb 04, 2020

    Hi PieterWigleven , I just clear my doubts. I've read the previous questions and still don't have sure on one thing.

     

    If I deploy my Hostpools using the Azure market place using Win 10 multisession  . Am I good to use with as many users i Want? Or will I be charged for the infrastructure plus the total users that uses WVD? 

  • PieterWigleven's avatar
    PieterWigleven
    Former Employee
    Jan 29, 2020

    sarahpotrick2573 as M365 E3 contains both "Windows E3 Per User" and "Office E3 Per User" you are all good assuming you are providing access to a Client SKU.

     

    • Windows E3 Per User covers Windows 10 Enterprise and Windows 10 Enterprise multi-session
    • Office E3 Per Users covers Office usage inside of the VM

    You can run the VMs against linux rates (preventing paying double) using the information provided here 

  • sarahpotrick2573's avatar
    sarahpotrick2573
    Copper Contributor
    Jan 29, 2020

    ok so what if my user has M365 E3? so still my user will be charged for the windows enterprise? or microsoft will automatically manage the licensing stuffPieterWigleven 

  • PieterWigleven's avatar
    PieterWigleven
    Former Employee
    Jan 27, 2020
    sarahpotrick2573 Any user connecting to a Windows client OS in WVD requires a Windows E3 Per User (or higher, like M365 E3/E5 Per User) license. The O365 E3 license you a referring only applies to Office and not Windows, the OS itself requires a valid license in order to be compliant.
    The Windows E3 requirement is trust based, there is nothing for you to enable.

Resources