## Problem Statement
The README recommends using the MongoDB connector for the Cosmos DB Mongo API, however, it seems that since the Cosmos DB Mongo API doesn't support the connectionStatus command, newer versions of the MongoDB Connector are incompatible with Cosmos DB. Mongo rejected a PR last year to add an option that would keep Cosmos DB supported: https://jira.mongodb.org/browse/KAFKA-332
I work for Confluent and have a customer using the Mongo API variant of Cosmos DB. I'm wondering if you can share any insight into what you would recommend and how we could best support this customer? Is MSFT looking to close this gap long term by adding Mongo API support for either the connectionStatus command or by creating a 1st party connector?
## Proposed Solution
Ideally, MSFT would provide a supported solution for Cosmos DB Mongo API users to integrate with Kafka.
## Alternative Solutions
The customer could use an older version of the MongoDB connector or patch the connector but maintaining this could be increasingly challenging long term.
## Problem Statement The README recommends using the MongoDB connector for the Cosmos DB Mongo API, however, it seems that since the Cosmos DB Mongo API doesn't support the connectionStatus command, newer versions of the MongoDB Connector are incompatible with Cosmos DB. Mongo rejected a PR last year to add an option that would keep Cosmos DB supported: https://jira.mongodb.org/browse/KAFKA-332
I work for Confluent and have a customer using the Mongo API variant of Cosmos DB. I'm wondering if you can share any insight into what you would recommend and how we could best support this customer? Is MSFT looking to close this gap long term by adding Mongo API support for either the connectionStatus command or by creating a 1st party connector?
## Proposed Solution Ideally, MSFT would provide a supported solution for Cosmos DB Mongo API users to integrate with Kafka.
## Alternative Solutions The customer could use an older version of the MongoDB connector or patch the connector but maintaining this could be increasingly challenging long term.
## Additional context Happy to collaborate here.
Next Steps