"Remote machine is AAD" but "The logon attempt failed"

Question

I setup Remote Desktop Connection and the computer says: AzureAD\username already has access:

Very good, let's try to connect using AzureAD\username:

Unfortunately it says:

Your credential did not work. Remote machine is AAD joined. If you are signing in to your work account, try using your work email address.

Of course it didn't work. Any idea?

Answer 1

To successfully connect to an AzureAD joined computer using Remote Desktop, you will need to first save your connection settings to a .rdp file.

To do this, open the Remote Desktop Connection program, enter the IP Address or computer name, then click the "Save As" button at the bottom of the screen. Save it someplace convenient, since we'll need to edit this file by hand.

Next, Right-Click the saved .rdp file and open with Notepad.

Go to the very bottom of the file, add the following lines:

enablecredsspsupport:i:0
authentication level:i:2

Save the file and close.

Now, try double clicking the modified .rdp file and login using the format:

AzureAD\YourFullUsername

Screenshots, original information and credit go to bradleyschacht.com

Answer 2

from your window, it doesn't seem like you logged in with an azuread account, try with [email protected] as a username?

as per here:https://learn.microsoft.com/en-us/windows/client-management/connect-to-remote-aadj-pc

When you connect to the remote PC, enter your account name in this format: AzureAD UPN. The local PC must either be domain-joined or Azure AD-joined. The local PC and remote PC must be in the same Azure AD tenant.

Answer 3

As long as RDP is enabled on the remote machine and the user you are trying to logon is with authorized, it should work.

The Azure Active Directory username is not exactly clear though.

Joined computer via '[email protected]', an Azure Active Directory domain account.

Computer shows 'AzureAD\FirstNameLastName' as authorized for RDP since it's an administrator account.

Must use 'AzureAD\[email protected]' for RDP username.

No other settings changes needed, no manual editing of RDP file just had to get the username right.