AzureFeeds

We are pleased to announce the introduction of the Confluent Kafka Connector in Logic Apps (Standard) which allows you to both send and receive messages between Logic Apps and Confluent Kafka.

Confluent Kafka is a distributed streaming platform for building real-time data pipelines and streaming applications. It is used across many industries including financial services, Omnichannel retail, autonomous cars, fraud detection services, microservices and IoT deployments.

Some of the benefits of using Confluent Kafka include the ability

• Publish and subscribe to streams of records


• Store streams of records in a fault tolerant way


• Process streams of records

Our current connector offering supports both triggers (receive) and sending (publish) within Logic Apps.

Consuming Messages

To enable a trigger, we need to search for the Confluent connector within our designer. We will discover an operation called Receive messages from Confluent Kafka show up as a built-in connector.

We can click on this operation to have our trigger operation added to our design surface. We now need to focus on configuring our trigger by providing a Topic Name, Consumer Group, Authentication Mode and Protocol.

We can subsequently use the payload from our trigger in downstream actions. For the purposes of this example, we are just going to place the payload within a Compose action.

Publishing Messages

To publish, or send a message, we can search for the Confluent connector within our design experience. We will discover an operation called Send messages to Kafka topic. We can click this operation to add it to our design surface.

With our Confluent Kafka action on our design surface we need to provide a Topic Name and a Message that we would like to send to the Topic.

We have now configured our solution and can run messages through our solution. To view this solution running in action, please see the following video.

Supported Regions

We are currently rolling this connector out worldwide and some regions will receive it before others. As of this writing the following regions will have this connector deployed in it:

• West Central US


• East Asia


• West US 2


• North Europe


• North Central US


• East US


• South Africa West


• Canada East

Remaining regions will receive this connector over the next coming weeks.

Feedback

This is our initial release of this connector. We are actively seeking feedback on what additional capabilities you require. Please fill out the following survey and we will be happy to follow-up with you.