How to enable concurrent users in Azure Virtual Desktop and allow multiple users to connect to the same virtual machine simultaneously.

Pramod Singh Tariyal 90 Reputation points
2025-03-25T15:45:03.8+00:00

Hello Team

I have created a host pool with pooled and while creating a host pool I created a user called "boxarr". In this host pool I used windows 10 multi session window.

User's image

Microsoft entra ID

User's image

In the application group, I have added 2 users called "pramod" & "eryk". but I'm not able to take a remove session desktop using these 2 users. I logged into windows 10 and created a local user called "pummy". Now boxarr and pummy users can take session desktop but not the users which are in my Azure portal.

User's image

Session desktop

User's image

How can I allow Pramod and Eryk users to login?

Azure Virtual Desktop
Azure Virtual Desktop
A Microsoft desktop and app virtualization service that runs on Azure. Previously known as Windows Virtual Desktop.
{count} votes

Answer accepted by question author
  1. Nikhil Duserla 9,280 Reputation points Microsoft External Staff Moderator
    2025-03-28T11:02:02.72+00:00

    Hi @Pramod Singh Tariyal,

    Thank you for your availability on call.

    User was not granted Virtual Machine User Login or Virtual Machine Administrator Login role

    In Azure portal go to WVD VM > Select Access control (IAM) > Select Role Assignments > Confirm the User account has

    been granted Virtual Machine User Login or Virtual Machine Administrator Login

    Checked have the necessary licenses to allow multiple users to connect to the virtual machine.

    Ensure RDP property targetisaadjoined:i:1 was added to the AVD host pool. So, add going through. Navigate to Azure portal > select host pool configured for Azure AD Joined > select RDP Properties blade > Select Advanced Tab > added- targetisaadjoined:i:1

    May have "per user MFA" enabled - which does not work with AVD, disable it. as per:  Log in to a Windows virtual machine in Azure by using Microsoft Entra ID - Microsoft Entra | Microsoft Learn

    I have provided more details, hope it helps. If it does, I would request you to kindly please consider accepting it as an answer and do a thumbs up at “Was it helpful”. This in turn will benefit other community members with similar scenario navigate better to right solutionUser's image

    3 people found this answer helpful.

1 additional answer

Sort by: Most helpful
  1. Alex Burlachenko 18,575 Reputation points Volunteer Moderator
    2025-03-26T11:20:06.33+00:00

    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

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.