Windows 10 DaaS licensing (non WVD)

%3CLINGO-SUB%20id%3D%22lingo-sub-2098195%22%20slang%3D%22en-US%22%3EWindows%2010%20DaaS%20licensing%20(non%20WVD)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2098195%22%20slang%3D%22en-US%22%3E%3CDIV%3E%3CP%3EAs%20part%20of%20our%20Services%20Strategy%20(we%20are%20an%20MSP)%2C%20we%20are%20looking%20to%20build%20a%20hosted%20W10%20DaaS%20on%20behalf%20of%20our%20customers%20and%20offer%20as%20an%20annuity%20service%2C%20but%20for%20an%20on-premise%20solution%20(not%20on%20Azure%20with%20WVD).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAs%20the%20platform%20is%20%3CU%3ENOT%20customer%20owned%3C%2FU%3E%20and%20provided%20%22as%20a%20service%22%20then%20License%20requirements%20and%20agreements%20become%20unclear%20around%20compliance%20specifically%20around%20Windows%2010.%3C%2FP%3E%3C%2FDIV%3E%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%3EThere%20are%20two%20options%20in%20my%20head%20which%20may%20or%20may%20not%20be%20possible%20or%20correct.%3C%2FDIV%3E%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%3EBYO%20licensing%20from%20a%20M365%20SKU%20%E2%80%93%20if%20this%20works%20with%20a%20hosted%20%E2%80%9Cas%20a%20service%E2%80%9D%20solution%20(e.g.%20not%20customer%20owned)%3C%2FDIV%3E%3CDIV%3EOr%3C%2FDIV%3E%3CDIV%3ESPLA%20licensing%E2%80%A6%20in%20which%20case%20the%20supplier%20(me)%20needs%20to%20provide%20all%20licensing.%20I%20need%20to%20ensure%20I%20have%20the%20correct%20agreements%20built%20into%20the%20contracts%20(or%20SPLA%20agreements%20in%20place)%20-%20to%20ensure%20compliance.%3C%2FDIV%3E%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%3E%3CP%3EHowever%2C%20there%20doesnt%20appear%20to%20be%20any%20specific%20related%20to%20using%20M365%20e3%2F5%20licnesing%20on%20a%20non-owned%20platform%20and%20SPLA%20only%20seems%20to%20refer%20to%20Windows%20Server%20OS%20and%20%22Windows%20Desktop%20Experience%22.%3C%2FP%3E%3C%2FDIV%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

As part of our Services Strategy (we are an MSP), we are looking to build a hosted W10 DaaS on behalf of our customers and offer as an annuity service, but for an on-premise solution (not on Azure with WVD).

 

As the platform is NOT customer owned and provided "as a service" then License requirements and agreements become unclear around compliance specifically around Windows 10.

 
There are two options in my head which may or may not be possible or correct.
 
BYO licensing from a M365 SKU – if this works with a hosted “as a service” solution (e.g. not customer owned)
Or
SPLA licensing… in which case the supplier (me) needs to provide all licensing. I need to ensure I have the correct agreements built into the contracts (or SPLA agreements in place) - to ensure compliance.
 

However, there doesnt appear to be any specific related to using M365 e3/5 licnesing on a non-owned platform and SPLA only seems to refer to Windows Server OS and "Windows Desktop Experience".

 

4 Replies
Hi,
if you want to have DaaS (data as a service) and don't want to use Azure and Windows Virtual Desktop, you want to virtualize your own Windows 10 machines on-premise, with physical server hardware,

maybe this will help:
https://download.microsoft.com/download/9/8/d/98d6a56c-4d79-40f4-8462-da3ecba2dc2c/licensing_windows...

@HotCakeX Thanks for reply

 

Our solution is based upon using a third party to host Windows client virtual machines on servers (Bare Metal) dedicated to the customer (not multi-tenanted). So Virtualization Rights seems to apply?

 

 

I think so yeah, because you are virtualizing them in the end,
there is a License advisory website but it has an old layout and elements don't load properly,
https://mla.microsoft.com/