I'm trying to set up a Windows 11 Pro VM and I'm facing a problem while logging in. I created a resource group, assigned the Virtual Machine Administrator login role to my Azure AD account, and then proceeded to create the VM in the East US region, using the D2sv3 size. I made sure to enable Entra ID in the management tab during the setup, and everything seemed to deploy just fine. However, when I try to connect via RDP, using the public IP and the username format AzureAD along with my password, I keep getting a 'logon attempt failed' error. I even tried entering my credentials again after clicking 'use another account' but still no luck.
Here are some of the things I've tried that haven't worked:
1) Reinstalling the extension.
2) Modifying the RDP file to disable NLP and adding parameters like 'enablerdsaadauth:i:1' and 'authentication level:i:2'.
3) Checking the dsregcmd output to confirm AzureADjoined status is 'Yes'.
4) Verifying my role as Virtual Machine Admin login.
3 Answers
Are you trying to connect via Bastion or directly? I've found that makes a difference in how you authenticate. It might be worth exploring that route, especially if you've got MFA enabled for your account.
I've been down a similar road before, and I discovered that you can only RDP into an Entra joined device from another Entra joined device. I had to set up a kind of jump box where I logged in with a local user first, then used my Entra credentials to access the VM. It's a bit of a hassle, but that's how it worked for me!
Looks like you've hit a wall there. The solution for me was realizing that my account had multi-factor authentication (MFA) enabled. Unfortunately, Entra VMs don't easily connect with MFA accounts. If possible, try to access it with an account that doesn't have MFA for now.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures