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

Question

User account '******@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 '******@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 21,156 Reputation points Microsoft Employee Moderator

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 21,156 Reputation points Microsoft Employee Moderator

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 25

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

6 answers

Your answer

Oury Ba-MSFT 21,156 Reputation points Microsoft Employee Moderator

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 21,156 Reputation points Microsoft Employee Moderator

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.

Answer 1

MG KYAING 1

It fixed and worked correctly after doing as following:

Command palette (Ctrl/Cmd + Shift + P) and run Clear Azure Account Token Cache
Restart Azure Data Studio
Login with SSO

0 comments

Answer 2

Erin Stellato 746 Microsoft Employee

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

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.
Qreatiq Support 10 Reputation points

2024-08-09T03:06:20.2+00:00

This command still working in 2024 for anyone who facing the same issue. Just type "Clear Azure Account Token Cache"
Lang, Ann (New York) 0 Reputation points

2025-01-06T21:05:04.24+00:00

Thanks--that worked for me! I really needed to use Azure Data studio right now and this saved me.
Zerrle, Martin SF/HZA-ZC2P 0 Reputation points

2025-05-26T07:41:18.5733333+00:00
Thank you!

In my case the error message could be fixed with only

Command palette (Ctrl/Cmd + Shift + P) and run Clear Azure Account Token Cache

Restart Azure Data Studio

Login with SSO
MG KYAING 1 Reputation point

2025-07-24T04:58:10.1733333+00:00

It worked for me by doing, go to the command palette (Ctrl/Cmd + Shift + P) and run Clear Azure Account Token Cache.
Thanks

Answer 3

Erin Stellato 746 Microsoft Employee

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.

0 comments

Answer 4

Oury Ba-MSFT 21,156 Microsoft Employee Moderator

@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 '******@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

0 comments

Answer 5

Ho, Eddie 25

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.

Oury Ba-MSFT 21,156 Reputation points Microsoft Employee Moderator

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 40 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