Windows 10: How to connect to an AzureAD joined computer with Remote Desktop

When trying to connect using Remote Desktop Connection (RDP) to a computer which is AzureAD joined, one will not be successful as it will fail to connect. To successfully connect, one should first open the Remote Desktop Connection, enter the details of the devices and save the save your connection settings to a .rdp file.

To do this, follow the instructions below.

Open the Remote Desktop Connection program.
Enter the IP Address or computer name to connect to.
Click the Save As button at the bottom of the screen.
Save it someplace convenient as we need to edit it.

In the next part we will be editing the .rdp file we saved using notepad or any text editor.

Go to the end of the file, add the following lines:

enablecredsspsupport:i:0
authentication level:i:2

Save the file and close.

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

AzureAD\YourFullUsername

You will be able to remote connect to the machine.

read more...

 

Windows 10 AzureAD joined device different login questions

Hi there -

I have remote offices all over the world where we're trying to slim down on the footprint but not having local domain controllers or any physical servers. I have AzureAD setup and I can join machines to it remotely over the internet. It seems that when this
is joined to AAD the user that registered it is the only one that is allowed to login to it. I had another forum question for this where they suggested we use AzureAD\UPN to login as a different user but that didn't seem to work.

Is this possible? Could I have remote machines that are not joined to an On-Prem DC, that can authenticate different users logging in locally (eg not RDP they're just sitting at a destkop)?

Thanks,

Ward

 

Cannot establish remote connection to PC with user set up as an Office 365 / AzureAD user

Hi Microsoft Community,

After following the advice from https://docs.microsoft.com/en-us/windows/client-management/connect-to-remote-aadj-pc (as best as I can), I have tried the following -

1. Enabled Network Level Authentication.

2. Added my user AzureAD\ to the list of Remote Desktop Users.

However, whenever I try to remote connect to my PC using my iPad (either using Jump Desktop or Microsoft Remote Desktop) the connection fails. I'm using the credentials as follows -

Username: AzureAD\ <as per the Remote Desktop Users screen>

Password: <Office 365 password, i.e. the one that allows me to log in on the PC>

I have checked the logs and the common error is that the user credentials are failing.

I have created a Local User Account as a test and am able to remote connect without any problems, so there is no firewall or security settings blocking a remote connection to the PC itself, but I cannot connect to the user account setup using Office 354
/ AzureAD.

Am I doing something wrong? Is there a way to get this to work?

Thank you,

Tim

 

Remote Desktop Connection problems


Have you tried Remote Desktop Connection, to connect from your Windows 10 laptop to your Windows 7 desktop? Try it first, post back and tell how it went.

Some additional help because you mentioned you are a remote newbie *Wink. The windows 7 related tutorials from our sister site the Seven Forums:

1. On Windows 7 desktop, set network location to either Home or Work (I recommend Work):
   • Network Location - Set as Home, Work, or Public Network - Windows 7 Help Forums
2. On Windows 7 desktop, allow incoming remote connections:
   • Remote Desktop Connection (RDC) - Network - Windows 7 Help Forums
3. On Windows 7 desktop, find out its IP address:
   • IP Address - Locate and Find for Your Computer - Windows 7 Help Forums
4. On Windows 10 laptop, start the Remote Desktop application and connect to the Windows 7 desktop using the IP address from step 3 above (see Part Three in the tutorial):
   • RDC - Connect Remotely to your Windows 10 PC - Windows 10 Forums
   • Notice that although the tutorial is written for Windows 10, it also applies to Windows 7

Try the above, post back how it went.