Unable to Connect Mongo Compass to Provisioned Cosmos Mongodb

Hi Alex Lewis,

I'm glad that you were able to resolve your issue and thank you for posting your solution so that others experiencing the same thing can easily reference this! Since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others ", I'll repost your solution in case you'd like to accept the answer.

Issue:

Just transitioned from a serverless cosmos mongodb instance to a provisioned one. Was previously able to connect to my serverless instance with mongo compass using the connection string. With the provisioned instance, I am unable to use mongo compass. Some background:

• I know my connection string is correct since a mongorestore call from the terminal with the --uri succeeds
• I have tried setting mongo compass to use the same connection string (which uses mongodb+srv:// and have also tried using the same connection string with mongodb://. Both attempts unsuccessful
• I have confirmed that mongo compass is using ssl/tls connection
• I understand that the Azure dataexplorer tool does not work with the provisioned mongodb instance. Not sure that should imply that mongo compass shouldn't work though.

Solution:

Turns out it was an issue with my MongoCompass version. Updating mongocompass to 1.46.0 resolved the issue.

If I missed anything please let me know and I'd be happy to add it to my answer, or feel free to comment below with any additional information.

Hope this helps. Do let us know if you have any further queries.

If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.