I have three on-prem Access/Terminal servers and one Broker Server set up to balance traffic among them using DNS round-robin. Our users connect to the Terminal servers via a DNS alias rather than by their individual hostnames, using their network logins formatted like "domainnetworkaccount". Everything has been working smoothly until we switched to Windows Hello, which means our users now need to log in with their Entra accounts. The issue is that while they can RDP successfully using their Entra accounts with the individual hostnames, they can't connect using the DNS alias; they receive an error that the 'DNS alias doesn't exist in our Azure Tenant.' It sounds like we might need to register this alias in Azure to make it functional, but we haven't figured out how to do that yet. Any ideas?
1 Answer
What error exactly are you seeing when you try to connect? I use Azure Virtual Desktop as a front end for my RDS servers, and it's set up as a jump host with SSO for connecting to the RDS servers. Might be able to help more if we know the specifics!
The error says something about the DNS alias not being found in our Azure tenant. Do you have any setup instructions for your configuration?