topic Expose Pub/Sub topics for IoT Hub Data Sources in Eventstream

Expose Pub/Sub topics for IoT Hub Data Sources

uriel-kluk — Mon, 15 Sep 2025 15:41:56 GMT

Work Item Type
Feature Request

Description

Similar to: https://community.fabric.microsoft.com/t5/Eventstream/Bind-IoT-Hub-Data-Sources-to-separate-streams/td-p/4826580/jump-to/first-unread-message, but a different approach
Propose a topic model for IoT Hub sources. IoT Hub writes to topics per Data Source. EventStream acts as the consumer and subscribes to one or more topics.

User Story
Raj manages an industrial robotics line. He needs telemetry data for performance analytics, twin changes for configuration tracking, and lifecycle events for predictive maintenance. Today, all event types arrive in one stream, forcing him to filter, re-route, and risk dropping messages. With topic-based subscriptions, Raj could point analytics jobs directly at the telemetry topic, dashboards at twin-change, and alerting at lifecycle, reducing cost and ensuring clean separation of workloads.

Note
EventHubs and EventStreams are efficient, full-featured, and scalable. However, in many IoT scenarios, a lightweight Pub/Sub architecture with MQTT brokers and clients is desirable for simpler routing, lower cost, and better alignment with device-oriented patterns. It would be valuable to allow configuration of user topics in addition to the built-in “events,” so telemetry can be routed automatically without extra processing.

Re: Expose Pub/Sub topics for IoT Hub Data Sources

tayloramy — Mon, 15 Sep 2025 16:07:02 GMT

Hi uriel-kluk,

To submit a feature request, please submit the idea here:

https://community.fabric.microsoft.com/t5/Fabric-Ideas/idb-p/fbc_ideas

This will allow the community to vote for it, and is where the Fabric CAT team looks when they're looking to add new features.

If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution.

Re: Expose Pub/Sub topics for IoT Hub Data Sources

uriel-kluk — Mon, 15 Sep 2025 16:19:20 GMT

While writing down the idea, I realized that I could connect the EventStream output to an MQTT broker. This is a 2-step approach, but flexible. I am accepting the solution as I don't believe changes to IoTHub and Fabric are needed with this approach.