[Feature Request]: Purging the Entra ID token cache

[skurik]

Feature Description

I would like the MSSQL extension to allow purging the Entra ID token cache.

Problem and Motivation

We use Privileged Identity Management (PIM) in Entra ID for getting access to our databases.

However, this does not play nicely with the mssql extension. Often times, after I activate a PIM (granting my Entra ID identity an access to an Azure SQL Database), I still cannot connect to the database, getting

mssql: Connection error: Login failed for '<token identified principal>'.

At the same moment, if I open SSMS, I can successfully connect there using the same identity.

Then, going back to VS Code, I still cannot connect.

I believe it's caused by some kind of Entra ID token cache and it would be great if it were possible to purge it via the extension so that fresh tokens are acquired.

Related Area

• Connection dialog (SQL Server | Azure browse/Fabric browse)
• Query results panel
• Query editor
• Object Explorer
• Table Designer
• Schema Compare
• Schema Designer
• Local SQL Server Container provisioning
• SQL database in Fabric provisioning
• GitHub Copilot integration
• Query Plan Visualizer
• Other (please describe below)

If you selected "Other", please describe the area

No response

Confirmation

• I have searched existing feature requests and couldn't find a match
• I want to help implement this feature

[aasimkhan30]

@skurik , we do provide a command to clear token cache. Please let us know if this works for your use case.