Forum Discussion
ghonyme
Jun 11, 2019Brass Contributor
Add guest user to Windows Virtual Desktop app pool
Hello, I'm trying to add guest user to my App pool but I always get the following error: The identity provider for Tenant 'xxxxxxxxxx' did not recognize User '≤xxxxxxxxxx≥'. Is there any res...
- Jun 12, 2019
ghonyme : Yes, unfortunately we do not support guest users yet in Windows Virtual Desktops. Users must be sourced from the Azure AD that you specify for your Windows Virtual Desktop tenant.
Florian Adler
May 27, 2021Copper Contributor
Exactly this feature do we need too.
There are several customers which like to work "modern". That means: WVD as first place of contact. To reduce costs and maintenance effort, we thought about building one big WVD environment instead of several small ones.
Therefore the clients will have either a Business Standard/Premium oder M365 E3, licenses are given and it should be fine from this perspective.
Unfortunately the current stage of WVD seems a little "old fashioned" regarding the architecture. Why is there still the need to connect to either an onPrem AD or AADDS? With end user devices it is possible since ages to manage them "cloud only". I know this feature (Azuer AD Hybrid Join) is in pipeline right now but why so late? Didn't it make more sense to implement ist as the spring update came along?
There are several customers which like to work "modern". That means: WVD as first place of contact. To reduce costs and maintenance effort, we thought about building one big WVD environment instead of several small ones.
Therefore the clients will have either a Business Standard/Premium oder M365 E3, licenses are given and it should be fine from this perspective.
Unfortunately the current stage of WVD seems a little "old fashioned" regarding the architecture. Why is there still the need to connect to either an onPrem AD or AADDS? With end user devices it is possible since ages to manage them "cloud only". I know this feature (Azuer AD Hybrid Join) is in pipeline right now but why so late? Didn't it make more sense to implement ist as the spring update came along?