You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Azure Databases VS Code Extension operates within your local VS Code environment and uses your machine’s network settings to connect to the database. If your machine is already part of the private Azure VNET, it should be able to resolve <someserver>.privatelink.postgres.database.azure.com and connect without issues.
If your machine isn’t in the VNET, accessing a Private Link endpoint can be challenging since traffic stays isolated. Typically, solutions involve setting up a VPN, ExpressRoute, etc. within the VNET to act as an intermediary.
Out of curiosity, are you able to connect to the database server using other tools or software running on the same machine as VS Code? If so, how are you configuring the connection? This could help us understand how best to approach this scenario.
Issue:
Connections that are attempted by the
Azure Databases
extension seem to be ONLY attempted over public connections.Use Case:
All public access is disabled and the only way to connect to the databases is from a private Azure VNET
Request:
Support resolving connections that require
<someserver>.privatelink.postgres.database.azure.com
DNS resolution.The text was updated successfully, but these errors were encountered: