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, May 21, 2015 4:35 PM
Hi
I have just created a new Azure VM using the Windows 10 Enterprise Insider Preview image and I am able to connect using RDP using the local account created when setting up the VM.
I have added my Microsoft account but it does not let me connect over RDP using this account even though it has Admin rights and also added to RDP access (even though this should not be required).
When I try to connect I keep getting an error saying the logon attempt failed. The login details are correct and work on other machines.
I have seen that other people have had this issue but not seen a resolution.
Thanks
Gary
Gary
All replies (8)
Monday, May 25, 2015 10:51 AM ✅Answered
Hi Gary:
Connectivity to a VM with a Microsoft Account to a VM is not possible.
This is only used for sync process.
When you sighn in the VM should needs to be authenitacted to communicate with a Domain Controller.
Regards;
Prasant
Friday, May 22, 2015 3:26 AM
Hi Gary;
How about other VMs?
I assume that you got the error "your credentials did not work", right?
In these scenario, please make sure that the you use the DNS name of the cloud service with the name of the user you created when creating the VM (xxx.cloudapp.net\username) as the user name to connect, and the correct password.
I test in my environment, the remote desktop setting is configured by default:
So, it’s just like the credential does not work. For example, I would use following format credential to access the VM
User name: v-cloud3.cloudapp.net\username
Friday, May 22, 2015 8:51 AM
Hi
Thanks for the reply. The Local account created when the VM was first created works when using xxx.cloudapp.net\username or .\username.
My issue is after adding a Microsoft Account to sign in with it does not work. I have tried .\MicrosoftUsername, MicrosoftAccount\MicrosoftUsername, xxx.cloudapp.net\username but none of these have authenticated. This account works find on other Windows 8 installations.
Thanks
Gary
Gary
Wednesday, July 1, 2015 8:42 PM
Connectivity to a VM with Microsoft Account is possible wint Win 8.1, please refere to http://www.mutzl.com/2014/05/win81-azure-vm-2/
What I looking for, and I suppose Gary also, is to be able to do the same with Win 10
Thanks,
Joorge Levy
Tuesday, August 4, 2015 2:15 PM
Hi,
I did the exact same scenario, but got lightly further:
My original purpose was to use Azure AD Account (from Office 365) to authenticate to the Windows 10 VM. Everything was working fine on the exact same VM locally. After moving the VM to Azure here is what I noticed:
- Microsoft Accounts are working fine. BUT not new ones, they had to previously be provisionned in the VM and initiated to work.
- Microsoft Azure AD account are not working. And I found several references online reporting this issue.
- Local account are working BUT you have to specify machine name as the domain to get them to work: machinename\localaccount.
My current option is to create local account, then ask the user to bind it to his/her Azure AD account, then eventually to his/her Microsoft Account.
I had to tweak the firewall to get this to work with the local VM, and I did not tweak this back before moving to Azure.
Monday, March 21, 2016 11:21 AM | 2 votes
Ok, so this may be a bit late, but I've found an easy solution for this.
- RDP to your Windows 10 VM using the local account credentials provided in the Azure portal.
- Launch the Store app
- Install any free app
This will prompt you for your Microsoft account credential and ask if you want to use that to log in to Windows
- Type your Windows account credentials
- Sign out
- Sign in again using "MicrosoftAccount\youremailaddress"
- PROFIT!
Thursday, April 7, 2016 5:49 PM
Money! Thanks Fabien. Easiest method I've found so far.
Wednesday, April 10, 2019 5:47 PM
Hi, had same with a couple machines linked to MicrosoftAccount\user from installation, remembered my previous installs started with a local account and were later linked to my Microsoft account an that worked fine.
Decided to change my Account so to sign in with a local account, tested RDP and that worked fine, decided to "re-link" my Microsoft account... tested again and it was still working without issues.Not sure exactly what causes the issue but it seems that creating a local account fixes the behavior, likely reg keys or gpedit settings not correctly configured with the MS account.
Further to the above, believe (from later found articles) that if the user signs in with the MS account password at least once rather than the PIN the issue may also be fixed.