locked
Using SSMS 2016 and Active Directory Password Authentication RRS feed

  • Question

  • Good afternoon,

    A colleague of mine came to me today with an issue.  He is trying to open SSMS as a different user to test some permissions.

    Historically, we would right click SSMS and "run as different user".  Then enter the domain user and password.  Once SSMS loads, then connect to our SQL Servers using "Windows Authentication".  This worked perfectly.

    Today, the colleague comes to me saying he's getting an error when trying to use a different user.

    He has opened up SSMS as his normal account (rather than doing "run as other user") and then, under the SSMS 2016 dropdown, selected "Active Directory Password Authentication" and entered the user to be impersonated's username and password as opposed to using "Windows Authentication"

    He then gets an error:

    So, my question:

    Is this because he is misinterpreting the meaning of "Active Directory Password Authentication" and this is, in fact, purely for Azure databases or Azure Active directory (neither of which we have)?

    The first article I found suggested as much, but I just want to make sure that I'm undertanding the article before quoting something inaccurate.
    https://docs.microsoft.com/en-us/sql/ssms/f1-help/connect-to-server-database-engine

    regards,

    Andy

    Monday, February 13, 2017 3:58 PM

Answers

  • Yes, the three "new" methods are all for connecting to SQL Server resources in Azure, as the document you found describes.


    Please mark as answer, if this was it. Visit my SQL Server Compact blog http://erikej.blogspot.com

    Monday, February 13, 2017 4:22 PM