*.privatelink.documents.azure.com resolution not working in vscode

So I can get twingate ip for my cosmosdb resource in azure (verified with nslookup) but as soon as I use vscode it hits the public ip interface instead where we have firewall running. What am I missing? I have defined both main domain and privatelink domain as well as private ip (all three) as resources inside twingate. I can curl the resource and resolve to the twingate ip, but vscode fails.

I also know that my privatelink setup is good cuz this all works from a vm inside the env.

I’ve been informed this is a known issue… and this post was also ref’ed: Failing to connect to resources outside of the browser, ie cli and dev tools - #2 by Arthur