How to connect Azure Synapse Notebook to Mongodb compass.

Hi @Rahul Kumar ,

Quick clarification: Compass is only a GUI. Your Synapse notebook connects directly to the MongoDB server, not to Compass. The error "ServerSelectionTimeout: name or service not known" means the Spark pool cannot resolve the MongoDB hostname over DNS. Nothing is wrong on the MongoDB side, the request never reached it. Common causes: - Hostname only resolves from your laptop (localhost / private IP / on-prem DNS). - MongoDB firewall / NSG / Atlas Network Access does not allow Azure outbound IPs. - Synapse workspace has Managed VNet enabled but no Private Endpoint to Mongo.

Fix:

1. Test DNS from the notebook itself: import socket socket.gethostbyname("<mongo-host>") If this fails, it is a network/DNS issue, not code.
2. Use the correct connection string from the Mongo service: - Cosmos DB for MongoDB -> Portal > Connection strings - Atlas -> whitelist Azure IPs (or use Private Link) and use the mongodb+srv URI - Self-hosted on Azure VM -> NSG allow 27017 from Synapse, bind mongod to 0.0.0.0 - On-prem MongoDB -> requires Self-hosted IR or ExpressRoute/VPN + private DNS
3. Working sample: %pip install pymongo dnspython from pymongo import MongoClient client = MongoClient("<uri>", serverSelectionTimeoutMS=15000) print(client.server_info())
   Follow steps 1 and 2 based on where your MongoDB is hosted and the connection will succeed.

Hello Rahul Kumar,

Welcome to the Microsoft Q&A and thank you for posting your questions here.

I understand that you would like to know how to connect Azure Synapse Notebook to Mongodb compass.

Try to understand that Azure Synapse Spark Notebooks run on Microsoft-managed Spark compute and do not support direct connectivity to third-party Private Link services such as MongoDB Atlas Private Endpoints. So, configuring Private Endpoints, DNS, firewall rules, or Synapse outbound IP addresses will not enable this scenario.

The supported resolution is to either deploy your compute within the same virtual network as the MongoDB Atlas Private Endpoint (for example, Azure Databricks with VNet injection, Azure Virtual Machine, or AKS), use a Self-hosted Integration Runtime (SHIR) where applicable, or expose MongoDB Atlas through a public endpoint secured with IP allow lists, TLS, and authentication.

Use the following official resources for additional guidance:

• Azure Synapse Managed Virtual Network and Managed Private Endpoints
• Azure Synapse Networking and Security Concepts
  https://learn.microsoft.com/azure/synapse-analytics/security/synapse-workspace-network-security
• Azure Data Factory/Synapse MongoDB Connector
  https://learn.microsoft.com/azure/data-factory/connector-mongodb
• MongoDB Atlas Private Endpoints for Azure
  https://www.mongodb.com/docs/atlas/security-private-endpoint/

I hope this is helpful. Please! Do not hesitate to let me know if you have any other questions, steps or clarifications.

Please do not close the thread by upvoting and accepting the answer if any part of it is helpful.