Forum Discussion
Christian_Montoya
Microsoft
Microsoft[Announcement] Connectivity issues from synchronized users to VMs joined to AAD DS
Hi everyone, thanks for the continued testing of WVD. We’ve seen multiple connection errors with UPN when connecting to VMs joined to Azure AD Domain Services. We’ve done some preliminary investigati...
Christian_Montoya : A fix has been rolled out to production for this issue.
Christian_Montoya Any update on this ? As others have reported we are at a stand still.
Synced from on-premise aren't working. I have tried validation pools and still no luck with Sync accounts.
- Seems like we’re in store for a repeat of Azure RemoteApp.
- Christian_Montoya
jeffb8 : Just to get more clarity, is it primarily this issue that you think will make it the next Azure RemoteApp? Is there other functionality that we're missing, should be focusing on, or should be fixing?
- Christian_Montoya
This issue specifically is **extremely** concerning - because this isn’t an edge case; this is a fundamental architecture/database design problem in how you uniquely identify users.
You don’t need to get AAD Domain Services or any other complicated scenario in the mix to reproduce this problem. All you need to do is delete **any** user in **any** kind of environment and then create a new one with the same upn. And bam, that user is screwed...forever.
Deleting and recreating the tenant doesn’t help any, which tells me that user registration data is stored independently of tenant data. This will lead down an avenue of problems with no end. There are alternative architectural approaches that would likely be more reliable.
