In the past year or so, I've been knee-deep in Azure Synapse. I have to say, it's been a super popular platform in Azure. Many clients are either migrating to Azure Synapse from SQL Server, data ware...
your blog post from previously this year have helped my understanding of the setup - thanks for the same!
I'm working on a typical hub-spoke company setup where part of the infrastructure is on prem and the resources would need to be discoverable across networks.
For this to work you need to also setup a (redundant/resiliant) DNS forwarder (on the hub) and on the on prem existing DNS selectively forward some DNS queries to this DNS forwarder. In addition you would need to add Azure Private Zone to the private links and keep those associated to the VNET/VNETs that should be able to talk to Synapse.
The typical setup is described here: https://docs.microsoft.com/en-us/azure/private-link/private-endpoint-dns(picture below pulled from there), and to complete the setup as you suggested the private zones required would be
privatelink.sql.azuresynapse.net
privatelink.dev.azuresynapse.net
privatelink.web.azuresynapse.net
privatelink.dfs.core.windows.net
privatelink.blob.core.windows.net
Could you add information around this to your blog?