Microsoft Azure

Fixing the Microsoft Azure AD Connect User Name or Password is Incorrect Error


I was setting up a new Microsoft Azure AD subscription for someone and came across this issue. Whenever I tried to sign into Azure AD Connect with a Global Administrator account it kept saying the below error message even though I verified the user ID and password were correct:

The user name or password is incorrect. Verify your user name, and then type your password again.

The solution to this problem is very simple. Often times when an Azure Administrator for a company sets up their Azure subscription they do it using their Microsoft account (the one), in this example let’s say [email protected] When you setup Azure AD you have to verify the domain with a TXT record and then the next step is usually to install and setup Azure AD Connect. The problem is that Azure AD requires the Global Administrator account it uses to be unique. What is happening is that there is an account already existing in the on premises AD with the same account name as the one being used by the Microsoft account for the subscription, in this example [email protected], and this is throwing things off as Azure AD Connect attempts to bridge the on premises AD with Azure AD.

You can verify this by going to and then going to your Default Directory. Go under Users and groups – All Users and find the login you are using to login to the portal with. You can see it will say the source is “Microsoft Account”:

To get around this problem, just create a sync account for Azure AD with the Global Administrator role that is unique and not in the on premises Active Directory.

1. Log into and go to Azure Active Directory.

2. Click on Users and groups

3. Click All Users

4. Click Add

5. Give it a Name and User Name, in this example it is [email protected] which I know does not exist in my on premises AD.

6. Click on Directory Role and change it to Global Administrator, then press OK at the bottom.

7. Now hit Create to create the account.

8. Now if you check the profile for this newly created account you will see it’s Source is “Azure Active Directory”.

9. Now go back to AD Connect and type in your new credentials and hit Next

10. You’ll see login is successful and it will enumerate Azure AD

11. Then the next step is to connect to Active Directory Domain Services using your on premises Enterprise Admin credentials and completing the AD Connect setup. You should have no problem going forward now.

Hope this helps if you come across this issue! Please leave a comment if this helped or if you have any questions.

About Jason Samuel

Jason Samuel lives in Houston, TX with a primary focus on strategic advisory and architecture of end-user computing, security, enterprise mobility, virtualization, and cloud technologies from Citrix, Microsoft, & VMware. He also has an extensive background in web architecture and networking over his 20+ year career in IT. He is an Author, Speaker, and Local User Group Community Leader. He is certified in several technologies and is 1 of 63 people globally that is a recipient of the prestigious Citrix Technology Professional (CTP) award. He is 1 of 42 people in the world that has been awarded as a VMware EUC Champion and VMware vExpert. He is a featured author on DABCC which provides the latest IT Community News on Cloud, Data Center, Desktop, Mobility, Security, Storage, & Virtualization. In his spare time Jason enjoys writing how-to articles and evangelizing the technologies he works with. Disclaimer: The content and opinions expressed in articles and posts are his own and are by no means associated with his employer.

Recommended for you


  1. Naaman Campbell

    October 1, 2017 at 6:15 AM

    Great article.. Very helpful for first-time Azure users.
    Helps resolve the “The user name or password is incorrect. Verify your user name, and then type your password again.” error.

  2. Lee Mckeown

    July 7, 2020 at 10:14 AM

    or you could just login to

    then change your password through that. 🙂

    hope that helps

  3. Mac Smith

    August 6, 2020 at 10:57 AM

    Nice job here!

    The error message is misleading. Your article helped me and I am sure several others on this issue. Thank you!

Leave a Reply

Your email address will not be published. Required fields are marked *