Unable to login to AVD session - Error Code: 0x3000047

Hi @Alex Burlachenko

Thank you for your detailed feedback.

I have successfully logged into the virtual machine using RDP and local admin credentials. To enable this, I modified the NSG to allow RDP connections from any source to any destination.

However, I observed that the virtual machine is not joined to Entra ID but is instead part of a WORKGROUP. This configuration may be preventing login with Entra ID credentials.

Could you please provide further guidance on the steps needed to resolve this issue and enable Entra ID-based authentication for the AVD?

Tariq Ghouri great news ... and thank you for your update. I’m really glad you were able to access the virtual machine via RDP, and I understand that the VM being in a WORKGROUP instead of Microsoft Entra ID (formerly Azure Active Directory) is likely causing the login issues for Azure Virtual Desktop (AVD). So step by step

Step 1: Join the Virtual Machine to Microsoft Entra ID

for AVD to work properly, the session host (your VM) must be joined to Microsoft Entra ID.

1. Log in to the VM using RDP (as you already did).
2. Open PowerShell as Administrator and run the following command to join the VM to Microsoft Entra ID:

dsregcmd /leave  

(This ensures any previous domain registrations are cleared.)

Next, run

Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Force  
Install-Script -Name Register-AzVMForWVD -Force  
Register-AzVMForWVD -TenantId "your-tenant-id" -SubscriptionId "your-subscription-id" -ResourceGroupName "your-resource-group" -VMName "your-vm-name"  

(Replace the placeholders with your actual Azure details.)

Step 2: Verify Microsoft Entra ID Join Status

After running the script, confirm the VM is successfully joined:

Open Settings -> Accounts -> Access work or school.

Check if it shows Connected to [Your Tenant’s] Microsoft Entra ID.

or you can use PS as well

dsregcmd /status  

Look for AzureAdJoined: YES in the output.

Step 3: Assign Required Roles in Azure

Even after joining Microsoft Entra ID, users still need proper role assignments:

Go to the Azure Portal -> Virtual Machines -> Select your AVD VM.

Under Access Control (IAM), ensure users have

Desktop Virtualization User

Virtual Machine User Login (Reference: Assign AVD roles in Azure)

Step 4: Restart the VM and Test AVD Login

After completing these steps:

Restart the VM to apply changes.

Have a user attempt to log in via the AVD client again.

Troubleshooting if Login Still Fails

Check Event Viewer on the VM (Windows Logs > Application) for AVD-related errors.

Ensure network security groups (NSGs) allow outbound connections to Azure services (ports 443, 80).

If using Conditional Access, verify no policies block AVD logins.

So... thats all... I really hope that would help. Let me to know if so

rgds,

Alex

p.s. hate to write from smartphone :((((

Hi @Alex Burlachenko

Thank you so much for the detailed response.

I attempted to run the Install-Script -Name Register-AzVMForWVD -Force command as suggested, but it failed with the following error:

No match was found for the specified search criteria and script name 'Register-AzVMForWVD'.

It looks like the script is no longer available in the PowerShell Gallery. Even after installing the required NuGet provider, the command still fails.

Additionally, when I try to run Register-AzVMForWVD directly, PowerShell returns:

The term 'Register-AzVMForWVD' is not recognized as the name of a cmdlet, function, script file, or operable program.

From what I’ve gathered, this script appears to be deprecated and is no longer used in modern Azure Virtual Desktop (AVD) deployments. Could you confirm if this is the case? If so, I’d appreciate guidance on the updated method to register a VM with AVD.

Tariq Ghouri Ah yes, the old Register-AzVMForWVD script… you’re spot on that it’s been deprecated (Microsoft’s docs don’t even mention it anymore). These days, joining a VM to Microsoft Entra ID for Azure Virtual Desktop is way simpler. let’s get that VM properly joined to Microsoft Entra ID. Since you’re already logged in via RDP, just open Settings > Accounts > Access work or school and click “Connect.” Choose the option to join it to Microsoft Entra ID it’ll guide you through signing in with your admin credentials. A quick restart after should do the trick.

If you prefer PowerShell (or need to automate this later), you can use dsregcmd /leave to clean up any old joins, then run Add-Computer with your Entra ID domain. Just don’t forget to restart!

Once the VM shows as “AzureAdJoined: YES” (check with dsregcmd /status), hop over to the Azure portal. Navigate to your Azure Virtual Desktop host pool and manually add this VM as a session host. The portal will handle the registration behind the scenes no more deprecated scripts needed.

and about those roles please double-check that users have both Desktop Virtualization User and Virtual Machine User Login assigned in the VM’s IAM settings. Sometimes the Azure portal is slow to reflect changes, so a 10-minute coffee break might help before testing logins again.

If users still hit snags, peek at the VM’s Event Viewer under Windows Logs > Application for AVD-related errors. and maybe triple-check that NSG it’s easy to overlook a stray rule blocking traffic.

rgds,

Alex

p.s. just in cases if you would like to join via PowerShell

# Install the Azure AD module (if not already present)
Install-Module -Name AzureAD -Force -AllowClobber

# Connect to Azure AD (authenticate with an Entra ID admin account)
Connect-AzureAD

# Join the VM to Entra ID
Add-Computer -DomainName "yourdomain.onmicrosoft.com" -Credential (Get-Credential) -Restart

just replace yourdomain.onmicrosoft.com with your Entra ID tenant domain.

and check

dsregcmd /status

look for AzureAdJoined: YES if still NO the join failed check network/firewall permissions.

BTW as I find "the Register-AzVMForWVD script is deprecated and is no longer supported in modern Azure Virtual Desktop (AVD) deployments. This script was part of the classic Windows Virtual Desktop (WVD) model, which has been replaced by the Azure Resource Manager (ARM)-based AVD. The ARM-based AVD offers better integration with Azure services and improved management capabilities. Microsoft has been transitioning users to this newer model, and as a result, older scripts like Register-AzVMForWVD are no longer maintained or recommended for use"

Hi @Alex Burlachenko

Thanks a lot for your continous effort in supporting. Below is my response,

1. I couldn't find the option here, Settings > Accounts > Access work or school and click “Connect.”
2. It worked sregcmd /leave
3. I tried to run the powershell commands you provided but they also didn't work, instead I ran
   Install-Module Microsoft.Graph -Scope CurrentUser
Import-Module Microsoft.Graph
4. But still unable the error persist on joining the Entra ID.
5. What I have found on internet is that my OS Windows 11 Enterprise multi-session, does not support full Entra ID Join. But if I switch to Single session then it will join the Entra ID but obviously won't achieve the goal of AVD.

Now, what could be the possible solution for this.