Hi @Stefan Kießig ,
The reason is quite simple: the Sessionhost still needs a Windows Token :smiling_face_with_smiling_eyes:
To clarify, for the user to be able to sign-in into the WVD client, that user needs to exist in Azure AD.
But when the user connects to the Sessionhost, the Windows Token is required.
So the same user needs to exist in an Windows AD
To solve that, you can choose between
- Create 1 (or more) Azure VMs, install & config the Windows AD role and install & configure Azure AD Connect to sync to Azure AD
- Use Azure AD DS, which will handle both the Windows AD & the sync to Azure AD.
