Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Thursday, July 23, 2015 9:27 PM | 1 vote
Hi,
Our organization has recently switched to using AzureAD credentials for PC sign-on using Widnows 10 Pro. Since making the switch, I can no longer RDP to my PC either on the local LAN or from home when using the AzureAD Credential. Attempting to use either a local account or Microsoft Account works fine so I wonder what I could be doing wrong.
I've tried the following forms: AzureAD\UserName, AzureAD\[email protected], [email protected], etc. but none work.
Can anyone suggest why this doesn't work?
Thanks,
Andrew
All replies (22)
Tuesday, August 11, 2015 11:00 PM ✅Answered
According to this blog maybe this functionality is no yet available...
Best Regards
Pablo F.
Wednesday, August 12, 2015 12:30 AM ✅Answered | 3 votes
Remote Desktop is not currently supported with Azure AD credentials.
Friday, November 20, 2015 11:53 PM ✅Answered | 5 votes
i know it is an old post but RDP works to Windows 10 computers with AzureAd when you use disable credsupport in the rdp file.
enablecredsspsupport:i:0
Friday, July 24, 2015 8:44 AM
Hi Andrew,
Our organization has recently switched to using AzureAD credentials for PC sign-on using Widnows 10 Pro. Since making the switch, I can no longer RDP to my PC either on the local LAN or from home when using the AzureAD Credential.
Would you please tell us how did you switched to using AzureAD crdentails?
Seems like that the issue is more Azure related, please refer to Azure forum to get more professional support:
Azure Active Directory Forum
Best Regards,
Amy
Please remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected].
Friday, July 24, 2015 2:50 PM | 1 vote
Hi Amy,
The PC was originally joined to a local domain and we were using domain accounts for logon, etc. I then removed my PC from the domain, and then joined our Company's organization using my AzureAD credentials. I then was able to logon to my PC using the AzureAD credentials from that point on. After making the switch, I found that I could not remote desktop using those credentials.
Does Remote Desktop allow login using AzureAD credentials?
Thanks,
Andrew
Tuesday, July 28, 2015 9:00 PM
I am experiencing the identical issue
Wednesday, July 29, 2015 9:13 AM
Hi Andrew,
I then was able to logon to my PC using the AzureAD credentials from that point on. After making the switch, I found that I could not remote desktop using those credentials.
So, you are able to log onto the PC locally using Azure AD credentials, but couldn’t log onto the PC remotely using Azure AD credentials, is that correct?
Would you please tell us from which machine you have tried to remotely connect to the PC?
Which error message was displayed when you failed to connect?
Since you have joined the PC to a new domain, please ensure that a trust relationship exists between the machine where you tried RDP on and the PC.
Best Regards,
Amy
Please remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected].
Friday, July 31, 2015 12:40 PM
Same issue!
How establish a trust relationship between the RDP machine and the PC?
Regards
Pablo F.
Monday, August 3, 2015 2:47 AM
Hi Pablo,
How establish a trust relationship between the RDP machine and the PC?
I was talking about trust between domains instead of machines, sorry about the confusion.
Best Regards,
Amy
Please remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected].
Thursday, August 6, 2015 2:23 PM
Hi Amy, thank you. Do you have information about how to establish a trust relationship between Azure Domain and AD Domain?
Best Regards
Pablo F.
Friday, August 7, 2015 8:37 PM | 1 vote
I too see this problem.
More info:
- AzureAD setup, created, and managed via a business Office 365 set of subscriptions (we have Lync, SharePoint, etc. all hooked up via the O365 functionality). (There is no on-premise Active Directory server this is tied into - completely within the confines of what Office 365 sets up itself.)
- Clean Windows 10 Pro 64-bit install, fully activated.
- During the Windows 10 OOBE setup, we selected that the computer is "Owned by my company" (whatever the exact wording is) and chose to join it to an Azure domain.
- Upon logging in, I entered my AzureAD credentials (created within Office 365 setup that we have had for 1.5 years).
- At this point, all is good.
- Next, I have enabled remote access, opened firewalls, and all that jazz.
- Next, I go to another machine on the same network and attempt to remote in.
- The MSTSC client sees the machine respond to the attempt and prompts me for my credentials.
At this point, I too don't know what to login with for my username nor password. I have tried an exhaustive combination of the following possibilities (assuming my AzureAD account is [email protected]):
Username:
- AzureAD\FName.LName
- AzureAD\FNameLName
- FName.LName@AzureAD
- FNameLName@AzureAD
- [email protected]
- [email protected]
- Domain\FName.LName
- Domain\FNameLName
- .\FName.LName
- .\FNameLName
Password:
- My actual password
- My PIN
- My current Azure Authenticator code
- My PIN followed by my current Azure Authenticator code
Every possible combination tells me that either my username or my password is incorrect. I don't know what else to try.
EDIT: Creating a temporary local admin account allows me to remotely access the Windows 10 machine. However, I still have no clue how to access it via the AzureAD account.
Saturday, August 8, 2015 8:21 PM
Same Problem and temporary local admin works also for the Moment.
Tuesday, August 11, 2015 9:20 PM
Hi Amy, any news about it?
Best Regards
Pablo F.
Monday, November 30, 2015 6:51 PM
That's awesome! Unbelievable that this still doesn't work "Out of the Box", but this solves the issue for me. Thanks heaps vdboots!
Tuesday, January 5, 2016 7:59 PM | 2 votes
i know it is an old post but RDP works to Windows 10 computers with AzureAd when you use disable credsupport in the rdp file.
enablecredsspsupport:i:0
vdboots, Thank you!
If anyone reads this but doesn't know what to do: put the line above in the actual .RDP file with something like notepad. Also the remote host will need the box unchecked that requires Network Level Authentication in System Properties/Remote tab.
Wednesday, September 6, 2017 4:16 AM
Karl, this still doesn't work for me. edited the rdp file, cleared the checkbox on the Windows 10 host, and I get to the complete log in screen, but regardless of the combination I use (as shown by Shane above) I get a message stating that the password is invalid.
Any other ideas of what may be causing?
Wednesday, September 6, 2017 5:26 AM
From a working .RDP file I had. The first two I'm just including in case it helps and only because they were in the file I had used before - over a year ago now - but it was working then.
prompt for credentials:i:0
authentication level:i:2
enablecredsspsupport:i:0
username:s:AzureAD\[email protected]
Monday, October 2, 2017 5:53 PM
It is worth noting that these workarounds prevent the pre-authentication that keeps an unauthenticated user from viewing the Login/Lock screen.
Put another way - an anonymous user can see the graphical login screen along with pictures of users to click on - so this might be appropriate for jumping between boxes at home or between lab PCs.
It's been awhile since I tried and it wasn't working for me either while testing 16299 - It required editing local group policy this time on the host.
I would love to figure how to pre-authenticate/firewall another way. Thinking of trying IPSEC policy between machines.
Screenshot of Local Group Policy Editor opened to Remote Desktop, Security, Require user authentication for remote connections by using Network Level Authentication - Disabled
Wednesday, June 20, 2018 5:38 PM
I have a related problem - if I connect to my azureAD joined laptop it asks for password, but I have only PIN and finger print! Is there a possibility to use PIN for RDP? When I tried to change password it got me to a MS Azure website but after logging in with my company credentials I got a message that my company does not allow us to change password...
Friday, December 7, 2018 1:57 PM | 1 vote
USER:
.\azuread\[email protected]
PASS:
yourpassword
If you need to SAVE credentails on your RDP:
Click "OTHER user"
.\azuread\[email protected]
your_password
CONNECT
You will receive The password is incorrect.
Click on EDIT under saved user/password and then OtherUser.
Repeat username and password and SAVE, then CONNECT.
The credentials will be OK.
Friday, December 7, 2018 1:58 PM
https://docs.microsoft.com/en-us/windows/client-management/connect-to-remote-aadj-pc
Monday, October 28, 2019 3:03 PM
This works for me
\AzureAD\[email protected]