Azure SQL MI Login with Azure AD (preview) issues.

  • akristiansen

    Grasshopper

    Points: 16

    Hi. 

    We have setup an MI with an Azure AAD group as owner. We can login to the sql instance with normal sql user.   However when we try to login from the same jumpbox with Azure AD user we get this errors: 

    On the sql studio login windows after we have verified 2 factor: 
    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.) (.Net SqlClient Data Provider)

    We goto log in sql and see this: 

    Length specified in network packet payload did not match number of bytes read; theconnection has been closed. Please contact the vendor of the client library

    We have verified that the needed client libraries is installed.   Any advice here would be much appriciated. 

    To summary: 
    Login with Azure AD user to  SQL MI using universal with mfa support option. ( we tried to define the tenant also)

  • Eirikur Eiriksson

    SSC Guru

    Points: 182347

    akristiansen - Monday, February 11, 2019 6:55 AM

    Hi. 

    We have setup an MI with an Azure AAD group as owner. We can login to the sql instance with normal sql user.   However when we try to login from the same jumpbox with Azure AD user we get this errors: 

    On the sql studio login windows after we have verified 2 factor: 
    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.) (.Net SqlClient Data Provider)

    We goto log in sql and see this: 

    Length specified in network packet payload did not match number of bytes read; theconnection has been closed. Please contact the vendor of the client library

    We have verified that the needed client libraries is installed.   Any advice here would be much appriciated. 

    To summary: 
    Login with Azure AD user to  SQL MI using universal with mfa support option. ( we tried to define the tenant also)

    Pinged this over to Microsoft, let's see what they come back with 😉
    😎

Viewing 2 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply