Okay Pramod, sorry for delay... long term write...
So... Verify VM Azure AD Join Status
Run this command in PowerShell on the session host
dsregcmd /status
Check:
- AzureAdJoined shows "YES"
- DomainJoined shows "YES" (if hybrid)
- WorkplaceJoined shows "NO"
Re-register the Session Host with AVD
Import-Module RemoteDesktop
Set-RdsContext -TenantId "YOUR_TENANT_ID"
Get-RdsSessionHost -TenantName "YOUR_TENANT" -HostPoolName "YOUR_POOL" | Restart-SessionHost
Check AVD Agent Status
Get-Service -Name RDAgentBootLoader, RemoteDesktopAgent
Both services should be "Running"
Validate User Assignments in Azure Portal
Go to Azure Virtual Desktop > Application Groups Select your application group
Under Assignments, confirm both users are explicitly listed or part of an assigned group
Force Token Refresh (For Testing)
On the session host do next:
Reset-AzVMADDomainExtension -ResourceGroupName "YOUR_RG" -VMName "YOUR_VM_NAME"
Check Event Logs for Errors
Get-WinEvent -LogName 'Microsoft-Windows-TerminalServices-RemoteConnectionManager/Operational' | Where-Object {$_.LevelDisplayName -eq "Error"}
Critical Configuration Often Missed
Azure AD Device Settings:
Azure Portal > Azure Active Directory > Devices > Device settings. Ensure "Users may join devices to Azure AD" is set to All
RDP Properties:
On the session host, run:
Set-ItemProperty -Path 'HKLM:\SYSTEM\CurrentControlSet\Control\Terminal Server' -Name "fDenyTSConnections" -Value 0
Set-ItemProperty -Path 'HKLM:\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp' -Name "UserAuthentication" -Value 1
Network Level Authentication
Ensure NLA is enabled in System Properties > Remote tab _ Azure NSG rules allow 3389
After making these changes
Have Pramod attempt connection via Official AVD client (not MSTSC)
Using exact Azure AD UPN (******@bosarr.com)
During connection, they should see Azure AD login prompt
Monitor connection attempts in:
Azure Portal > AVD > Host Pools > Monitoring
Session host Event Viewer > Applications and Services Logs > Microsoft > Windows > TerminalServices
_And last one Remove local users (they bypass AVD security and licensing)
Focus on Azure AD users only for proper management. if issues persist, consider recreating the host pool with next fresh Windows 10 Multi-session image. Proper Azure AD join during deployment. I'm pretty sure this approach ensures proper Azure AD authentication flow rather than local authentication which is currently working but not the recommended approach for AVD.
rgds,
Alex.
p.s. let me to know if its help