Having intermittent issue with logging into Azure Managed instance using SSMS

Question

Having intermittent issue with logging into Azure Managed instance using SSMS

Hajkowski, Michael 0

Developers are having intermittent issues logging into SQL Managed instance in Azure.

They are using SQL Server Management Studio. Diagnostics returned the following:

We ran diagnostics between 2025-03-14 13:49 UTC and 2025-03-18 13:50 UTC and were able to detect connections to managed instance sssssssss-sss-smi-sql using a JDBC driver version that is below version 6.4.0, the minimal recommended version for connections to SQL Managed Instance.

Database 'samplicity-host-sit-db' using driver 'Microsoft JDBC Driver 6.1', from 'Microsoft JDBC Driver for SQL Server' application name on IP Address '10.21.5.x'- Database 'samplicity-Check228Alloc-db' using driver 'Microsoft JDBC Driver 6.1', from 'Microsoft JDBC Driver for SQL Server' application name on IP Address '10.21.5.x'- Database 'samplicity-xxxxx-db' using driver 'Microsoft JDBC Driver 6.1', from 'Microsoft JDBC Driver for SQL Server' application name on IP Address '10.21.5.x'- Database 'samplicity-nnnnnn-db' using driver 'Microsoft JDBC Driver 6.1', from 'Microsoft JDBC Driver for SQL Server' application name on IP Address '10.21.5.x'- Database 'Samplicity-commercial-aaaaa-sit-db' using driver 'Microsoft JDBC Driver 6.1', from 'Microsoft JDBC Driver for SQL Server' application name on IP Address '10.21.5.x'

As far as I know, SSMS does not use JDBC, this message is spurious at best. Sometimes it will connect for the developer, other times it will give the following error:

unable to connect to sql manged instance, below are the error for sql user and entra user:

sqluser---Login failed for user '-----'. Reason: Failed to open the explicitly specified database 'SSISDB'. [CLIENT: 10.253.202.239]

Message Login failed for user '<token-identified principal>'. Reason: Could not find a login matching the name provided. [CLIENT: 10.253.202.239]

Erland Sommarskog 121.8K Reputation points MVP Volunteer Moderator

2025-03-18T22:15:59.53+00:00

I am not sure that I understand the relevance of the JDBC messages here.

As for the first error message about SSISDB, is there an SSISDB on the instance? And does the user in question have access to it?

I take it, that the second error message about token-identified principal only appears with Entra auth? But there is more than one way to select Entra. Is the developer using the option he/she is supposed to use?
Prasad Chaganti 770 Reputation points Microsoft External Staff Moderator

2025-03-19T23:56:44.7533333+00:00

Hi Hajkowski, Michael,

Just checking in to see if the below answer provided by Alberto Morillo.

If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.

1 answer

Your answer

Erland Sommarskog 121.8K Reputation points MVP Volunteer Moderator

2025-03-18T22:15:59.53+00:00

I am not sure that I understand the relevance of the JDBC messages here.

As for the first error message about SSISDB, is there an SSISDB on the instance? And does the user in question have access to it?

I take it, that the second error message about token-identified principal only appears with Entra auth? But there is more than one way to select Entra. Is the developer using the option he/she is supposed to use?
Prasad Chaganti 770 Reputation points Microsoft External Staff Moderator

2025-03-19T23:56:44.7533333+00:00

Hi Hajkowski, Michael,

Just checking in to see if the below answer provided by Alberto Morillo.

If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.

Answer 1

Alberto Morillo 34,671 MVP Volunteer Moderator

That JDBC error message makes me think that those developers are not only using SSMS but also using Azure Data Studio (that does use a JDBC driver) to connect to Azure SQL MI. Azure Data Studio is a deprecated tool.

Please consider reviewing the configuration steps outlined here, in case a step is missing. If those developer are associated to a group login, please consider these limitations and workarounds for Azure SQL MI.

Prasad Chaganti 770 Reputation points Microsoft External Staff Moderator

2025-03-20T22:59:24.7233333+00:00

Hi Alberto Morillo,

Following up to see if the above answer was helpful. If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.

Share via

Having intermittent issue with logging into Azure Managed instance using SSMS

1 answer

Your answer