Unable to connect Azure SQL database using ActiveDirectory Integrated Authentication RRS feed

  • General discussion

  • Open SQL Server 2016 CTP 2 Management Studio (Microsoft SQL Server Management Studio 13.0.600.65)

    Provide the Azure SQL database name.

    Choose ActiveDirectory Integrated Authentication as the authentication mode.

    Click on "Connect".

    Error :

    TITLE: Connect to Server

    Cannot connect to <<database_name>>.database.secure.windows.net.


    A connection was successfully established with the server, but then an error occurred during the login process. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.) (Microsoft SQL Server, Error: 10054)

    For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%20SQL%20Server&EvtSrc=MSSQLServer&EvtID=10054&LinkId=20476


    An existing connection was forcibly closed by the remote host




    Wednesday, October 7, 2015 6:38 AM

All replies

  • Hello,

    AFAIK AD Authentification for SQL Azure is currently only available as preview, have you setup this preview Option? Otherwise you can only use SQL Authentications, see Azure SQL Database security guidelines and limitations => Authentication.

    Olaf Helper

    [ Blog] [ Xing] [ MVP]

    Wednesday, October 7, 2015 6:52 AM
  • Two additional authentication options were added to SSMS for authentication to Azure SQL databases: Active Directory Integrated Authentication, and Active Directory Password Authentication.

    1. Active Directory Integrated Authentication: This provides the most seamless login option and uses your Windows login credentials to access your Azure SQL database. This option requires a bit of setup and an administrator with the right permissions to federate user logins from your on-premises domain to Azure. You can learn more about how to use Azure AD Connect to federate your user logins here.

    2. Active Directory Password Authentication: This option is used if the user login of your client machine has not been federated to Azure. Essentially it boils down to creating a user login/identity on Azure, adding that user (or a group the user belongs to) as an Active directory administrator for your intended Azure SQL database, then logging in to SSMS using the credentials you created. You can learn more about creating and populating an Azure Active Directory here.

    Hope this helps, others as well who are interested in this information.

    Tuesday, November 24, 2015 9:15 PM