WVD Licensing

%3CLINGO-SUB%20id%3D%22lingo-sub-1469469%22%20slang%3D%22en-US%22%3EWVD%20Licensing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1469469%22%20slang%3D%22en-US%22%3E%3CP%3EHi%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECan%20someone%20please%20try%20and%20answer%20this%20query%20as%20we%20seem%20to%20be%20having%20no%20luck%20with%20reseller%20about%20clarification%20on%20this%20matter.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EScenario%3A%3C%2FP%3E%3CP%3EAs%20MSP%20we%20want%20to%20deploy%20all%20WVD%20Resources%20including%20Azure%20AD%2C%20AD%20DS%20in%20our%20tenant%20-%20call%20it%20MSP%20Tenant.%20This%20is%20where%20all%20workspace%2C%20session%20hosts%20etc%20will%20live.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20then%20have%20Customer%201%2C%20Customer%202%20etc%20-%20they%20have%20their%20own%20Microsoft%20365%20tenants%20and%20we%20have%20licensed%20the%20users%20with%20Microsoft%20365%20Business%20Premium.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENow%20to%20connect%20to%20WVD%20we%20create%20user%20accounts%20in%20our%20tenant%20AD%20-%20say%20%3CA%20href%3D%22mailto%3Auser1%40msptenant.com%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Euser1%40msptenant.com%3C%2FA%3E%3C%2FP%3E%3CP%3EBecause%20WVD%20does%20not%20allow%20connectivity%20for%20guest%20accounts%20yet%20-%20much%20needed%20feature%20to%20solve%20this%20shenanigan!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EUser1%20also%20in%20their%20own%20Microsoft%20365%20tenant%20has%20Microsoft%20365%20Business%20Premium%20license%20-%20say%20%3CA%20href%3D%22mailto%3Auser1%40customer1.com%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Euser1%40customer1.com%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EUser1%20is%20now%20able%20to%20connect%20to%20our%20WVD%20resources%20using%20%3CA%20href%3D%22mailto%3Auser1%40msptenant.com%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Euser1%40msptenant.com%3C%2FA%3E%26nbsp%3Baccount%20and%20all%20is%20working%20ok.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20User1%20meeting%20the%20license%20requirements%20for%20WVD%3F%20OR%20will%20we%20need%20to%20double%20up%20on%20license%20for%20his%20%3CA%20href%3D%22mailto%3Auser1%40msptenant.com%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Euser1%40msptenant.com%3C%2FA%3E%26nbsp%3Baccount%20too%20despite%20him%20already%20having%20appropriate%20license%20on%20%3CA%20href%3D%22mailto%3Auser1%40customer1.com%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Euser1%40customer1.com%20%3C%2FA%3Eaccount%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1482536%22%20slang%3D%22en-US%22%3ERE%3A%20WVD%20Licensing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1482536%22%20slang%3D%22en-US%22%3ECan%20someone%20at%20Microsoft%20please%20answer%20this%20-%20strange%20how%20no%20one%20(not%20even%20our%20Distributor)%20has%20an%20answer%20for%20this%20-%20numerous%20tickets%20raised%20about%20this%20and%20yet%20no%20answer!%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1487617%22%20slang%3D%22en-US%22%3ERe%3A%20WVD%20Licensing%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1487617%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F694817%22%20target%3D%22_blank%22%3E%40limaecho%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20did%20get%20a%20response%20from%20our%20distributor%20(Ingram%20Micro)%20and%20from%20Microsoft%20Belgium%20directly.%20The%20technical%20architecture%20you%20outlined%20does%20function%20(Tested%20this%20myself)%20but%20according%20to%20them%20does%20not%20adhere%20to%20licensing%20requirements.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EEven%20a%20setup%20where%20you%20would%20double-up%20on%20licences%20is%20not%20allowed.%20Sad%2C%20but%20true.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20impact%20is%20you%20need%20to%20deploy%20a%20domain%20controller%20per%20tenant.%20I%20suggest%20B2S%20(21-25%E2%82%AC)%20unless%20if%20your%20domain%20controller%20needs%20to%20double%20as%20an%20applicationserver%20for%20something%20other%20then%20DC.%20It%20also%20means%20that%20for%20smaller%20deployments%20you%20might%20need%20to%20scale%20down%20sufficiently.%20I%20suggest%20B4MS%20or%20even%20B2MS%20servers%20for%20such%20deployments.%20It%20makes%20things%20a%20bit%20less%20efficient%20then%20lobbing%20everything%20into%20one%20big%20MSP%20tenant%20but%20you%20should%20be%20able%20to%20build%20a%20cost-efficient%20infrastructure%20none%20the%20less.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Contributor

Hi

 

Can someone please try and answer this query as we seem to be having no luck with reseller about clarification on this matter.

 

Scenario:

As MSP we want to deploy all WVD Resources including Azure AD, AD DS in our tenant - call it MSP Tenant. This is where all workspace, session hosts etc will live.

 

We then have Customer 1, Customer 2 etc - they have their own Microsoft 365 tenants and we have licensed the users with Microsoft 365 Business Premium.

 

Now to connect to WVD we create user accounts in our tenant AD - say user1@msptenant.com

Because WVD does not allow connectivity for guest accounts yet - much needed feature to solve this shenanigan!

 

User1 also in their own Microsoft 365 tenant has Microsoft 365 Business Premium license - say user1@customer1.com

 

User1 is now able to connect to our WVD resources using user1@msptenant.com account and all is working ok.

 

Is User1 meeting the license requirements for WVD? OR will we need to double up on license for his user1@msptenant.com account too despite him already having appropriate license on user1@customer1.com account?

2 Replies
Can someone at Microsoft please answer this - strange how no one (not even our Distributor) has an answer for this - numerous tickets raised about this and yet no answer!

@limaecho 

 

We did get a response from our distributor (Ingram Micro) and from Microsoft Belgium directly. The technical architecture you outlined does function (Tested this myself) but according to them does not adhere to licensing requirements. 

 

Even a setup where you would double-up on licences is not allowed. Sad, but true. 

 

The impact is you need to deploy a domain controller per tenant. I suggest B2S (21-25€) unless if your domain controller needs to double as an applicationserver for something other then DC. It also means that for smaller deployments you might need to scale down sufficiently. I suggest B4MS or even B2MS servers for such deployments. It makes things a bit less efficient then lobbing everything into one big MSP tenant but you should be able to build a cost-efficient infrastructure none the less.