Forum Discussion
Microsoft[Announcement] Connectivity issues from synchronized users to VMs joined to AAD DS
Christian_Montoya : A fix has been rolled out to production for this issue.
Christian_Montoya So no workaround for this scenario since the SID check is active now and according to you no ETA too. that's a bit disappointing!
I know the service is currently in preview, but i find the fact that this bug took multiple weeks to identify and acknowledge is a bit worrying for the state/future of AAD DS (that we rarely deployed before WVD).
Are there so few orgs using AAD DS ? Should we drop it and extend on-prem ADs to Azure LAN for WVD instead ?
- Christian_Montoya
ArthurOpenhost : I wouldn't say that no one is using Azure AD DS or that it's not a viable solution. Primarily, understanding this failing scenario is an intersection of where customers are today and how they are piloting Windows Virtual Desktop with just cloud users (before trying to extend this with a full site-to-site on-prem infrastructure).
Between using Azure AD DS or extending existing domain structure to Azure, it depends on your scenarios you're targeting. You have much more flexibility by extending, since you can use Federation, Passthrough Authentication, or password hash (whereas AAD DS only works with password hash). Not sure if you've already seen this comparison article.
Christian_MontoyaThat makes sense, thank you.
Is "Azure AD join" on the roadmap for WVD ? Or will AAD DS continue to be the lightest deployment for our SMB customers ?- Christian_Montoya
ArthurOpenhost : Azure AD Join is in our backlog. We've heard overwhelming interest for this, and we want to align with Azure AD Join/Intune as a means of deploying and managing Windows. We don't have any specific dates on this, but we definitely want to supporting this as a scenario down the road.
