通过

"Your credentials did not work" error when connecting to Windows Azure VM's

  • 项目

Below specified is the error that might occur while connecting to Windows Azure VM’s via remote desktop (mstsc).

 

One very common reason that all of us are aware for this issue is “wrong password”. However, I often come across situations where users are definitely specifying correct username, password and still the issue seem to occur. I have worked with multiple customers regarding this very issue and investigation revealed that “invalid” username value is causing the issue. Let me explain!

While configuring remote desktop credentials via “Configure Remote Desktop Connections” option that is available in Publish wizard, Windows Azure tools does a pretty good job of validating the password, confirm password fields. However it does not validate username field. In below example, I have configured invalid values for both username, password. Notice that explanation mark highlighted below with circle appeared next to password field. But, there is no warning message appeared for username field.  

 

 

Since, validation is not performed by Windows Azure Tools for username field, one needs to be cautious about what value that is being configured. What really happens behind the scenes is, Windows Azure creates a specified user on the VM and grants permissions required for Remote Desktop access. So, generic username requirements/guidelines are applicable here as well.

Some of standard requirements

  1. Username should not match with existing user accounts. Few user accounts that are already presented on the Windows Azure VM’s are “Administrator”, “Guest”. Hence, do not use these names while configuring remote desktop access.
  2. Names may not consist entirely of periods and/or spaces, or contain these characters: \ / " [ ] : | < > + = ; , ? * @
  3. Length of username should be <=20
  4. Username should not be null
  5. Password cannot contain the username or part of username

 

Quick test you can perform to reduce errors is to create a user in local machine with specified username, password and proceed with remote desktop configuration only after local test succeeds!

How to connect to VM using Remote Desktop(RDP) on Windows Azure (Cloud)
https://blogs.msdn.com/b/narahari/archive/2010/12/01/how-to-connect-to-vm-on-windows-azure.aspx

Comments

  • Anonymous
    January 27, 2013
    nice catch mate... after 100 new certificates, reboots, uploads... came across this explanation. In my experience, I had an instance on staging and defined the user name as "Admin", then wanted to upload a solution to production with the same UserId and same encryption certificate... I was getting the same error over and over again until I changed the username to admin@<somethingarbitrary> for the production instance. Thanks again...

  • Anonymous
    January 28, 2013
    I'm glad this helped Can Bilgin.

  • Anonymous
    February 20, 2013
    Thanks so much, this is very helpful!

  • Anonymous
    February 20, 2013
    You are welcome Joy.

  • Anonymous
    June 21, 2013
    where i can find publish wizard..............

  • Anonymous
    June 23, 2013
    Hi Himanshu, In Visual Studio, If you right click on the cloud service, you should see "Publish" option. Clicking on the publish option will bring publish wizard. If you do not see that publish option, ensure latest Windows Azure SDK is installed. Thanks, Hari.

  • Anonymous
    August 06, 2013
    With the thread "Connect to VM using Azure cloud" is it able to be used with other Remote destinations?

  • Anonymous
    August 07, 2013
    Hi John, I'm not what you meant by "Other Remote Destinations". Blog Post blogs.msdn.com/.../how-to-connect-to-vm-on-windows-azure.aspx is meant for connecting to VMs hosted in Azure. Thanks, Hari

  • Anonymous
    December 23, 2013
    I'm not using the Publisher -- just creating machines and users manually. After adding users to the Azure Active Directory Domain, (e.g. smith@mydomain.onmicorosft.com), I tried logging in as one of those users, but got "Your credentials did not work." After some trial and error, I found that I had to add the users (e.g. smith) as local users on the VMs. Once I did that, and assigned, passwords, the users could RDP in.

  • Anonymous
    June 01, 2014
    Thanks it helped. In my case it was "-" which caused the issue. You can mention this as well in your list.

  • Anonymous
    September 08, 2015

  1. select use another account
  2. enter username as :  "domainusername"   (instead of simple username)
  3. enter pswd
  4. OK ITS WORKING
  • Anonymous
    September 15, 2015
    jinso please give me screenshoot.