https://community.databricks.com/t5/administration-architecture/integration-of-mongodb-and-databricks-serverless/m-p/162159#M5402 <P>What you are experiencing with the connection request not appearing in MongoDB Atlas when establishing a private link is common due to the issues given below.</P><H3><FONT size="3">You can follow below</FONT></H3><UL><LI><P><FONT size="3"><STRONG>If the connection request is missing from the MongoDB Atlas console,&nbsp;</STRONG>you can verify the Principal Allowlist. Navigate to the MongoDB Atlas project's Private Endpoint settings and ensure the Databricks Serverless IAM role is allowed. For AWS commercial regions, the required principal format is like&nbsp;</FONT>arn:aws:iam::565502421330:role/private-connectivity-role-us-east-1</P></LI><LI><P><FONT size="3"><STRONG>If the principal is allowlisted but the request is still pending generation,</STRONG> then check the Network Connectivity Configuration (NCC). In the Databricks Account Console under Security, select the NCC and verify the Private endpoint rules. Ensure you enter the same VPC endpoint service name from MongoDB Atlas and that the FQDNs exactly match your MongoDB connection string format </FONT>like*.mongodb.net<FONT size="3">.</FONT></P></LI><LI><P><FONT size="3"><STRONG>If NCC configuration is accurate,</STRONG> then review your MongoDB Atlas Endpoint Service settings. Ensure that <STRONG>Acceptance required</STRONG> is enabled, that the consumer region (Databricks workspace region) is added to the configuration and that the endpoint service spans at least two Availability Zones if this is a cross-region setup.</FONT></P></LI><LI><P><FONT size="3"><STRONG>If you have just deployed the NCC rule and verified other points,</STRONG> then <STRONG>allow for propagation time</STRONG>. It can take several minutes for the network request to traverse the infrastructure and appear in MongoDB Atlas under <STRONG>Network Access to Private Endpoint to Pending Requests</STRONG>.</FONT></P></LI></UL> Wed, 08 Jul 2026 02:42:22 GMT balajij8 2026-07-08T02:42:22Z https://community.databricks.com/t5/administration-architecture/integration-of-mongodb-and-databricks-serverless/m-p/162154#M5401 <P>Hi,&nbsp;<BR />I'm looking to integrate the databricks serverless workspace with Mongodb atlas through the private endpoint route. Created a NCC rule from databricks. From Mongodb side I cannot see the request to approve the connection,&nbsp;<BR /><BR />Thanks,&nbsp;<BR />Tarun</P> Wed, 08 Jul 2026 01:35:44 GMT https://community.databricks.com/t5/administration-architecture/integration-of-mongodb-and-databricks-serverless/m-p/162154#M5401 tsuppalapati 2026-07-08T01:35:44Z https://community.databricks.com/t5/administration-architecture/integration-of-mongodb-and-databricks-serverless/m-p/162159#M5402 <P>What you are experiencing with the connection request not appearing in MongoDB Atlas when establishing a private link is common due to the issues given below.</P><H3><FONT size="3">You can follow below</FONT></H3><UL><LI><P><FONT size="3"><STRONG>If the connection request is missing from the MongoDB Atlas console,&nbsp;</STRONG>you can verify the Principal Allowlist. Navigate to the MongoDB Atlas project's Private Endpoint settings and ensure the Databricks Serverless IAM role is allowed. For AWS commercial regions, the required principal format is like&nbsp;</FONT>arn:aws:iam::565502421330:role/private-connectivity-role-us-east-1</P></LI><LI><P><FONT size="3"><STRONG>If the principal is allowlisted but the request is still pending generation,</STRONG> then check the Network Connectivity Configuration (NCC). In the Databricks Account Console under Security, select the NCC and verify the Private endpoint rules. Ensure you enter the same VPC endpoint service name from MongoDB Atlas and that the FQDNs exactly match your MongoDB connection string format </FONT>like*.mongodb.net<FONT size="3">.</FONT></P></LI><LI><P><FONT size="3"><STRONG>If NCC configuration is accurate,</STRONG> then review your MongoDB Atlas Endpoint Service settings. Ensure that <STRONG>Acceptance required</STRONG> is enabled, that the consumer region (Databricks workspace region) is added to the configuration and that the endpoint service spans at least two Availability Zones if this is a cross-region setup.</FONT></P></LI><LI><P><FONT size="3"><STRONG>If you have just deployed the NCC rule and verified other points,</STRONG> then <STRONG>allow for propagation time</STRONG>. It can take several minutes for the network request to traverse the infrastructure and appear in MongoDB Atlas under <STRONG>Network Access to Private Endpoint to Pending Requests</STRONG>.</FONT></P></LI></UL> Wed, 08 Jul 2026 02:42:22 GMT https://community.databricks.com/t5/administration-architecture/integration-of-mongodb-and-databricks-serverless/m-p/162159#M5402 balajij8 2026-07-08T02:42:22Z https://community.databricks.com/t5/administration-architecture/integration-of-mongodb-and-databricks-serverless/m-p/162164#M5403 <P>Is this on AWS or Azure?</P> <P>&nbsp;</P> Wed, 08 Jul 2026 03:22:17 GMT https://community.databricks.com/t5/administration-architecture/integration-of-mongodb-and-databricks-serverless/m-p/162164#M5403 anagilla 2026-07-08T03:22:17Z