[Bug]: Dataverse connections are not working

[kburtram]

Description

The extension should support Dataverse connections.

Steps to Reproduce

According to user feedback on VS Code Marketplace, Dataverse connections are not working. We should investigate to confirm and fix.

For reference, here's the review comment.

Outrageous. They cease support for one of their best applications, Azure Data Studio, in order to replace it with this flimsy extension, and then it doesn't even work WITH THEIR OWN PRODUCTS. We're a few months away from end of support for ADS, and as of today this extension still cannot query Dataverse environments. You should not ship unfinished products, least of all substitute a perfectly functioning one with a butchered minified version just so you can push AI a bit more easily.

Affected 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 affected area

No response

Environment Information

Latest version

Confirmation

• I have searched existing issues and couldn't find a match
• I want to work on this issue

[Benjin]

For anyone encountering issues with Dataverse connections, can you confirm what specific endpoint types you're unable to connect to with MSSQL? I'm particularly interested in any endpoint types that are not *.crm.dynamics.com.

I think this is the same underlying issue as #19602, which should now be fixed in our upstream dependencies (MSSQL -> SQL Tools Service -> SQL Management Objects v180.9.0-preview) and consumed with #20377.