Hi Josh Ashwood,
Thanks for reaching out to Microsoft Q&A.
I don't see any official docs mentioned about this, but I believe you can achieve this. You might need to configure a private endpoint for the Managed Instance and ensure that the synapse workspace is correctly set up to access resources within the same VNet or a peered VNet.
Try the following steps and let me know
After creating private endpoint for your managed Instance...
- configure your custom DNS solution to resolve the private endpoint's FQDN to the private IP address
- Ensure that your Synapse workspace is deployed within the same VNet or a peered VNet where the Managed Instance's private endpoint exists. Configure the Synapse workspace to use the managed private endpoint for communication with the Managed Instance
- In your Synapse workspace, navigate to the "Manage" hub --> security -->select "Managed private endpoints."
- Click on New to create a new managed private endpoint. Follow the wizard to specify the target resource (Managed Instance)
Now use the appropriate connection string in your Synapse notebook, ensuring that the connection string targets the private endpoint's fqdn.
Note: Make sure that the network security groups (NSGs) and firewall rules allow the necessary traffic between Synapse and the Managed Instance.
Please 'Upvote'(Thumbs-up) and 'Accept' as an answer if the reply was helpful. This will benefit other community members who face the same issue.