HomeWinBuzzer NewsMicrosoft Releases Kafka Connect for Azure IoT Hub, alongside Source Code on...

Microsoft Releases Kafka Connect for Azure IoT Hub, alongside Source Code on GitHub

Kafka Connect for Azure IoT Hub will allow develops to access telemetry data from connected devices in a secure and performant manner.


has released Kafka Connect for Azure IoT Hub, allowing developers to read telemetry data from connected devices. The Redmond giant has also released the source code for this connector on GitHub, alongside extensive documentation.

According to Azure IoT partner director Sam George, the functionality “enables developers to connect IoT Hub to systems using Kafka for a powerful, secure and performant IoT solution.”

George also reveals that you can use Kafka Connect via Microsoft's Apache Hadoop distribution, Azure HD Insight. The functionality will be welcome for many users, and developers are told to “stay tuned for more announcements.

We can get a vague idea of what the team is planning through the GitHub page. Under the section “Future work,” is a couple of updates.

Microsoft is accepting code contributions for this, though you'll have to sign a license agreement.

Here's what the Azure team has listed so far:

  • “Add support to use the schema name in the message in IoT Hub as the topic name. This will allow sending data with different schemas to their respective topics. (For example, for a device recording and sending temperature and humidity data to IoT Hub, the data can be pumped to “temperature” and “humidity” topics respectively, for easier consumption).
  • Add a Kafka sink connector to send messages from Kafka to IoT devices via the IoT Hub.”

IP Filtering

The new Kafka functionality comes just a few weeks after the inclusion IP filtering in Azure IoT Hub. Admins can now choose to accept only certain IP addresses, block specific ones, or both at the same time.

For the moment, IP Filtering supports the following protocols:

  • MQTT
  • HTTP/1

To avoid tipping off potential attackers, rejected addresses aren't told about the policies. Instead, they get a simple unauthorized 401 code. This means that all that new telemetry data will be safe from prying eyes.

You can read more about IP Filtering on the Azure blog, where you'll also find a short explanation of Kafka Connect.

Ryan Maskell
Ryan Maskellhttps://ryanmaskell.co.uk
Ryan has had a passion for gaming and technology since early childhood. Fusing the skills from his Creative Writing and Publishing degree with profound technical knowledge, he enjoys covering news about Microsoft. As an avid writer, he is also working on his debut novel.

Recent News