[Bug]: Connect to Database select wrong DNS when select via browse azure

[JanBigalke]

Description

The database that the plugin should connect to is synapse dedicated SQL DB. DNS XXX..sql.azuresynapse.net
The connection dialog select instead: XXX..database.windows.net. With this DNS entry the private endpoint that is
XXX.privatelink.sql.azuresynapse.net will not be resolved and the connection fails because public access is denied.

Steps to Reproduce

1. Browse Azure for the DB connection in the connection dialog.
2. Select a synapse dedicated SQL Pool
3. check the connection String : is not with XXX..sql.azuresynapse.net it contains XXX..database.windows.net and private DNS can't be found.
4. This works well for Azure Data Studio

Affected Area

• Connection dialog
• Query results panel
• Query editor
• Object Explorer
• Table Designer
• Schema Compare
• Schema Designer
• Local container
• GitHub Copilot integration
• Query Plan Visualizer
• Other (please describe below)

If you selected "Other", please describe the affected area

We are trying to transition from Azure Data Studio to VS Code , this migration is right now not working

Environment Information

Version: 1.101.1 (user setup)
Commit: 18e3a1ec544e6907be1e944a94c496e302073435
Date: 2025-06-18T13:35:12.605Z
Electron: 35.5.1
ElectronBuildId: 11727614
Chromium: 134.0.6998.205
Node.js: 22.15.1
V8: 13.4.114.21-electron.0
OS: Windows_NT x64 10.0.22631

Confirmation

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

[JanBigalke]

please let me know if there is a way to generate logs for this issue