{"id":12834,"date":"2026-10-09T00:00:28","date_gmt":"2026-10-09T07:00:28","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/cosmosdb\/?p=12834"},"modified":"2026-10-02T07:49:08","modified_gmt":"2026-10-02T14:49:08","slug":"introducing-the-native-confluent-cloud-connector-experience-in-azure-cosmos-db","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/cosmosdb\/introducing-the-native-confluent-cloud-connector-experience-in-azure-cosmos-db\/","title":{"rendered":"Introducing the Native Confluent Cloud Connector Experience in Azure Cosmos DB!"},"content":{"rendered":"

Co-authored with Praveen Raja P<\/strong><\/em><\/p>\n

<\/i>Quick hint<\/strong><\/p>Connectors run in a Confluent organization provisioned through Apache Kafka & Apache Flink on Confluent Cloud, an Azure Native Integrations service<\/strong><\/a>. The organization is managed as an Azure resource, uses Microsoft Entra ID single sign-on, and is billed through your Azure invoice.<\/p>\n

 <\/p>\n

No organization yet? Select Create Confluent organization<\/strong> on the Integrations > Apache Kafka on Confluent Cloud<\/strong> page to launch the creation experience<\/a> in place. Confluent also offers a free trial with credits to get started with the Confluent Cloud \u2013 Pay as you Go<\/strong> plan. Once the organization is created, it\u2019s selected automatically, so you can move straight to creating a connector.<\/div><\/p>\n

Azure Cosmos DB already includes a powerful event foundation: change feed<\/a> provides a durable, ordered record of item changes within each logical partition. It is ideal for reacting to operational data as it changes, building projections, and driving workflows directly from the database. Confluent Cloud adds a complementary event layer rather than replacing change feed. Kafka topics can carry database changes alongside explicit business events from many systems, retain them independently from the operational database, and let multiple consumer groups process and replay each stream at their own pace. Teams also gain Kafka\u2019s broad ecosystem for stream processing, integration, governance, and cross-system event distribution, while Azure Cosmos DB continues to serve globally distributed operational state with low latency.<\/p>\n

Together, they support data movement in both directions: publish Azure Cosmos DB changes to Kafka for independent downstream consumers, or project Kafka events into Azure Cosmos DB as application-ready views. This existing integration is backed by the fully managed V2 Kafka connector for Azure Cosmos DB<\/a>, and today we are announcing a new native Azure portal experience. Connector discovery, resource selection, validation, and cluster creation can now happen directly from your Azure Cosmos DB account, without custom relay plumbing or switching between consoles.<\/p>\n

\"event<\/a><\/p>\n

\n

Start where your operational data lives<\/h2>\n<\/div>\n

In an Azure Cosmos DB for NoSQL account, open Integrations<\/strong>\u00a0>\u00a0Apache Kafka on Confluent Cloud<\/strong>. Select a Confluent organization, environment, and cluster to view connectors or create one.<\/p>\n

\"02<\/a><\/p>\n

\n

<\/h2>\n

Choose the data direction<\/h2>\n<\/div>\n

Select\u00a0Create new connector<\/strong>. The guided workflow covers Basics, Authentication, Configuration, and Review + Create while carrying the Azure Cosmos DB account and selected Confluent resources forward.<\/p>\n

\"05<\/a><\/p>\n