setting up private endpoint between cosmos db and synapse analytics

Question

hello team,

i want to setup private endpoint for synapse workspace and cosmos db but the "managed virtual network" is set as No. how does it affect the private endpoint connection. please let me know if any way to establish the explicit connection between cosmos db and synapse workspace with above setting as i am getting failures in dataflows which shows request from synapse workspace getting blocked by cosmos db firewall settings.

Answer 1

Hi @ANKIT GHENGE

Greetings & Welcome to the Microsoft Q&A forum! Thank you for sharing your query.

When you're setting up a private endpoint between Azure Synapse Analytics and Azure Cosmos DB, both services generally need to be in the same virtual network or connected through peering to ensure secure communication. The problem you're facing with the "managed virtual network" set to "No" can impact how the private endpoint works and how Synapse and Cosmos DB communicate with each other.

Here are the steps you can follow:

First, make sure you've created a private endpoint for your Cosmos DB. This gives Cosmos DB a private IP address, so it can securely communicate within your virtual network. Don’t forget to update Cosmos DB’s firewall settings to allow traffic from your virtual network or the specific private endpoint you're using.

Since your Managed Virtual Network setting is "No", you’ll need to manually configure a private endpoint for your Synapse workspace. This private endpoint should be in the same virtual network (or a peered one) where your Cosmos DB private endpoint is located. This ensures that Synapse can securely route traffic over the private network to Cosmos DB.

In Cosmos DB’s firewall settings, you need to make sure it's set up to allow traffic from the virtual network that contains your Synapse workspace. You can either whitelist your virtual network’s IP range or allow traffic from the Synapse workspace’s private endpoint specifically.

After setting everything up, ensure that the data flows in Synapse are using the private endpoint to access Cosmos DB. This means traffic should go through the private IP address rather than a public endpoint.

By following these steps, you can establish a secure connection between Synapse and Cosmos DB using private endpoints.

For more details refer to these documentations:

Azure Synapse Analytics managed private endpoints

Azure Synapse Analytics frequently asked questions

Configure Azure Private Link for Azure Cosmos DB analytical store

I hope this information helps.

Kindly consider upvoting the comment if the information provided is helpful. This can assist other community members in resolving similar issues.