User account 'me@myorg.com' not found in MSAL cache?

red stone 1

This used to work, but today I get this error when trying to open our company MS Sql server in azure data studio on mac:

User account 'me@myorg.com' not found in MSAL cache, please add linked account or refresh account credentials.

How do I work around this?

I've tried killing/restarting Azure Data studio of course.

User's image

Oury Ba-MSFT 16,731 Reputation points Microsoft Employee

2023-09-25T18:43:55.1233333+00:00

@red stone Thank you for reaching ut.

Do you see the same when using SSMS to connect?

Regards,

Oury
Oury Ba-MSFT 16,731 Reputation points Microsoft Employee

2023-09-26T19:28:03.2933333+00:00

@red stone

Checking if you were able to connect. Please share the status of the issue.

Regards,

Oury
Rick Moore 0 Reputation points

2023-09-29T19:41:49.6533333+00:00

I have the same issue on a new windows 11 pc. I have two accounts and use the run as different user for my admin account. Running SSMS using run as different user will properly authenticate using MFA, but VSCode, Azure Data Studio, Powershell 7 do not work.

Update: run as different user is no longer required on Windows 11 for what I was using it for.

Ho, Eddie 15

having same login problem with data studio for mac, its a fresh token from azure cli login.

Also I can connect to azure monitor logs with same creds, but not MS SQL server

Microsoft.Data.SqlClient.SqlException (0x80131904): User account 'userdetails.blanked' not found in MSAL cache, please add linked account or refresh account credentials. ---> System.Exception: User account 'user.details.blanked' not found in MSAL cache, please add linked account or refresh account credentials.   at Microsoft.SqlTools.Authentication.Authenticator.GetTokenAsync(AuthenticationParams params, CancellationToken cancellationToken) in /_/src/Microsoft.SqlTools.Authentication/Authenticator.cs:line 129   at Microsoft.SqlTools.Authentication.Sql.AuthenticationProvider.AcquireTokenAsync(SqlAuthenticationParameters parameters) in /_/src/Microsoft.SqlTools.Authentication/Sql/AuthenticationProvider.cs:line 90   at Microsoft.Data.SqlClient.SqlInternalConnectionTds.<>c__DisplayClass147_1.<<GetFedAuthToken>b__1>d.MoveNext()--- End of stack trace from previous location ---   at Microsoft.Data.SqlClient.SqlInternalConnectionTds.GetFedAuthToken(SqlFedAuthInfo fedAuthInfo)   at Microsoft.Data.SqlClient.SqlInternalConnectionTds.GetFedAuthToken(SqlFedAuthInfo fedAuthInfo)   at Microsoft.Data.SqlClient.SqlInternalConnectionTds.OnFedAuthInfo(SqlFedAuthInfo fedAuthInfo)   at Microsoft.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)   at Microsoft.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)   at Microsoft.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean enlistOK)   at Microsoft.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, Boolean ignoreSniOpenTimeout, TimeoutTimer timeout, Boolean withFailover)   at Microsoft.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(ServerInfo serverInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString connectionOptions, SqlCredential credential, TimeoutTimer timeout)   at Microsoft.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(TimeoutTimer timeout, SqlConnectionString connectionOptions, SqlCredential credential, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance)   at Microsoft.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, SqlCredential credential, Object providerInfo, String newPassword, SecureString newSecurePassword, Boolean redirectedUserInstance, SqlConnectionString userConnectionOptions, SessionData reconnectSessionData, Boolean applyTransientFaultHandling, String accessToken, DbConnectionPool pool)   at Microsoft.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, DbConnectionPoolKey poolKey, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection, DbConnectionOptions userOptions)   at Microsoft.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnectionPool pool, DbConnection owningObject, DbConnectionOptions options, DbConnectionPoolKey poolKey, DbConnectionOptions userOptions)   at Microsoft.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject, DbConnectionOptions userOptions, DbConnectionInternal oldConnection)   at Microsoft.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject, DbConnectionOptions userOptions, DbConnectionInternal oldConnection)   at Microsoft.Data.ProviderBase.DbConnectionPool.TryGetConnection(DbConnection owningObject, UInt32 waitForMultipleObjectsTimeout, Boolean allowCreate, Boolean onlyOneCheckConnection, DbConnectionOptions userOptions, DbConnectionInternal& connection)   at Microsoft.Data.ProviderBase.DbConnectionPool.WaitForPendingOpen()--- End of stack trace from previous location ---   at Microsoft.Data.SqlClient.SqlRetryLogicProvider.ExecuteAsync(Object sender, Func`1 function, CancellationToken cancellationToken)   at Microsoft.Data.SqlClient.SqlRetryLogicProvider.ExecuteAsync(Object sender, Func`1 function, CancellationToken cancellationToken)   at Microsoft.SqlTools.ServiceLayer.Connection.ReliableConnection.ReliableSqlConnection.<>c__DisplayClass30_0.<<OpenAsync>b__0>d.MoveNext() in /_/src/Microsoft.SqlTools.ManagedBatchParser/ReliableConnection/ReliableSqlConnection.cs:line 323--- End of stack trace from previous location ---   at Microsoft.SqlTools.ServiceLayer.Connection.ConnectionService.TryOpenConnection(ConnectionInfo connectionInfo, ConnectParams connectionParams) in /_/src/Microsoft.SqlTools.ServiceLayer/Connection/ConnectionService.cs:line 748ClientConnectionId:b32310b6-f3ed-45d9-b24e-b502bf883b7a

5 answers

Erin Stellato 486 Reputation points Microsoft Employee

2023-11-05T17:12:57.34+00:00

Folks - for anyone still having this issue can you please try with the latest Insider build (https://github.com/microsoft/azuredatastudio#try-out-the-latest-insiders-build-from-main-branch) and after installing, go to the command palette (Ctrl/Cmd + Shift + P) and run Clear Azure Account Token Cache.

If this does not address the issue, please comment on this GitHub issue: https://github.com/microsoft/azuredatastudio/issues/24104
Please sign in to rate this answer.

11 people found this answer helpful.
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Mike Floyd 0 Reputation points

2023-12-04T16:06:55.24+00:00

Thank you Erin!

Brandonn Guevara 0 Reputation points

2024-03-08T01:17:33.62+00:00

Thanks for this!

Mike Petrak 5 Reputation points

2024-04-29T20:49:59.4233333+00:00

Thanks, @Erin Stellato . This tip worked for me just now to resolve the error when connecting with Azure Data Studio to Azure SQL MI.
Sign in to comment
Erin Stellato 486 Reputation points Microsoft Employee

2023-10-02T18:50:15.21+00:00

Hi @Red stone Can you try clearing the token cache (go to Ctrl/Cmd + Shift + P) and then entering Azure Accounts: Clear Token Cache and running the command? You'll then need to restart ADS. If this continues, can you please share OS Platform and ADS version? The latest version of ADS is 1.46.
Please sign in to rate this answer.

5 people found this answer helpful.
Oury Ba-MSFT 16,731 Reputation points Microsoft Employee

2023-10-02T20:37:30.9133333+00:00

red stone, Rick Moore Please check above answer from @Erin Stellato and let us know if that helps.

Regards,

Oury

Ho, Eddie 15 Reputation points

2023-10-11T11:18:07.12+00:00

Having same problem with data studio on a mac

Oury Ba-MSFT 16,731 Reputation points Microsoft Employee

2023-10-11T18:05:26.98+00:00

Ho, Eddie

Have you tried the same workaround provided above.?

Regards,

Oury

Bevan 0 Reputation points

2023-10-13T05:44:54.5+00:00

Hi @Erin Stellato

I am having the same issue - I can connect using MFA via SSMS but not Azure Data Studio with message - User account 'xx@xxx' not found in MSAL cache, please add linked account or refresh account credentials.

I cleared the token cache and retested but get same error.

The VM Server OS is Windows Server 2022 Datacenter v 21h2 and Data Studio is version - 1.46.1

Rick Moore 0 Reputation points

2023-10-13T12:08:58.5366667+00:00

Hi. The only way that I've been able to get this working is to add both accounts as my regular user and switching between the two accounts instead of using run as. As far as the comment below about adding user to both SQL roles, I'm an owner of my subscription with my admin account so those roles shouldn't have to be directly granted.

Suraj Iyer 0 Reputation points Microsoft Employee

2023-11-05T05:15:36.1833333+00:00

I havent been able to get this to working for a while now. Account token clear also didnt work.

Erin Stellato 486 Reputation points Microsoft Employee

2023-11-05T17:12:17.3333333+00:00

Suraj Iyer Can you please try with the latest Insider build (https://github.com/microsoft/azuredatastudio#try-out-the-latest-insiders-build-from-main-branch) and after installing, go to the command palette (Ctrl/Cmd + Shift + P) and run Clear Azure Account Token Cache.

Suraj Iyer 0 Reputation points Microsoft Employee

2023-11-05T18:21:06.29+00:00

This worked, Erin. I am able to access SQL DBs successfully with this insider build.

Erin Stellato 486 Reputation points Microsoft Employee

2023-11-06T01:02:44.4833333+00:00

Suraj Iyer Great news, thank you for letting me know!

David Wolf 5 Reputation points

2024-05-08T20:40:39.3033333+00:00

That got me past "User account 'me@myorg.com' not found in MSAL cache" error, which is great, but now I get "Login failed for user '<token-identified principal>'" error, which I also get from SQL Server Management Studio.

I'm able to access same database using Synapse Analytics, so issue is not database access. And issue is not with my client/computer as I get same "Login failed for user '<token-identified principal>'" error using computer of colleague who has no problem connecting on his own.

Thanks in advance for any advice.

Erin Stellato 486 Reputation points Microsoft Employee

2024-05-09T14:13:36.1366667+00:00

David Wolf when you're connecting in SSMS or ADS, make sure you are selecting the database in the connection dialog (in SSMS this is on the Connection Properties of the login dialog, in ADS it's on the main page).

David Wolf 5 Reputation points

2024-05-13T14:22:30.33+00:00

Thanks, Erin! It was not possible to select database without connecting. I had tried that previously. But manually typing database name did the trick!
Sign in to comment
Ho, Eddie 15 Reputation points

2023-10-13T11:08:26.62+00:00

I have got it working by adding my AD user to the following roles on Azure MS SQL Server:

SQL DB Contributor & SQL Server Contributor

and add in the networking to allow my client public IP.
Please sign in to rate this answer.

2 people found this answer helpful.
Oury Ba-MSFT 16,731 Reputation points Microsoft Employee

2023-10-13T19:50:40.44+00:00

Ho, Eddie

I'm glad also that you were able to resolve your issue and thank you for posting your solution so that others experiencing the same thing can easily reference this! Since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others", I'll repost your solution in case you'd like to "Accept" the answer.

Jeywin Lizy Rani Thangiah 20 Reputation points

2023-11-14T23:40:54.2366667+00:00

Yes this is the one that resolved my issue.
I assigned roles in the Azure portal under "Subscriptions > Access control (IAM)
for the Db Admin User for the role SQL DB Contributor
Sign in to comment
Oury Ba-MSFT 16,731 Reputation points Microsoft Employee

2023-10-13T19:52:15.07+00:00

@red stone

Problem:

This used to work, but today I get this error when trying to open our company MS Sql server in azure data studio on mac:

User account 'me@myorg.com' not found in MSAL cache, please add linked account or refresh account credentials.

How do I work around this?

I've tried killing/restarting Azure Data studio of course.

Solution:

Adding my AD user to the following roles on Azure MS SQL Server fixed the issue:

SQL DB Contributor & SQL Server Contributor

and add in the networking to allow my client public IP.

Regards,

Oury
Please sign in to rate this answer.

1 person found this answer helpful.

0 comments No comments
Sign in to comment
Erin Stellato 486 Reputation points Microsoft Employee

2023-10-13T19:59:00.2933333+00:00

Hi all (Rick Moore and @red stone) - I've confirmed with engineering this is not entirely resolved, and what worked in one scenario may not work for everyone. We are actively investigating, you can find the open issue here: https://github.com/microsoft/azuredatastudio/issues/24104

I would encourage you to add your details/info there if you are able, as that may provide more detail to engineering to help resolve the issue. Thank you for your patience as we work to resolve this issue.
Please sign in to rate this answer.

1 person found this answer helpful.

0 comments No comments
Sign in to comment

Share via

User account 'me@myorg.com' not found in MSAL cache?

5 answers