Bind IoT Hub Data Sources to separate streams

[uriel-kluk]

Description
IoT Hub routes support multiple Data Sources for message routing. Today, all event types are mixed into a single EventStream.

User Example
Sophie manages a fleet of connected HVAC units. She uses telemetry to monitor temperature, twin changes to track updated settings, and lifecycle events to know when devices are provisioned. She wants a clean pipeline where telemetry feeds into an analytics model, twin changes feed into a configuration dashboard, and lifecycle events feed into inventory management. Today, because all events arrive mixed in one stream, Sophie must build filters and SQL queries to split them out, which is redundant, adds cost, and increases risk of misrouting data.

Expected Result

• Select a single Data Source at source setup instead of mapping it to the built-in "event".

• One EventStream per Data Source. No mixing.

• Avoid redundant de-multiplexing with filters or SQL.

Actual Result

• All event types land in one stream.

Impact

• Pipelines and models are hard to separate.

• Increases complexity and compute cost.

Repro Steps

1. Create IoT Hub routes for Telemetry, Twin Changes, Lifecycle, and Connectivity to "events".

2. Add one IoT Hub source in EventStream.

3. Send steady telemetry. Then disconnect the device or change a property.

4. Open schema editor.

5. Observe all event types in one stream.

6. Observe new fields are not addable without a live sample.

Acceptance Criteria

• Given a source bound to Telemetry, only telemetry arrives.

• Given a source bound to Twin Changes, only twin changes arrive.

• Given a source bound to Lifecycle, only lifecycle events arrive.

Note
This issue could be worked around by using a separate Event Hub per route instead of mapping everything to the built-in "events." However, that duplicates the messaging infrastructure. The request is to support direct routing without that duplication. If the cost is calculated per message rather than per service, this concern may be less relevant.

[v-sgandrathi · Accepted solution]

Hi @uriel-kluk,

Thank you for providing a comprehensive overview of your scenario and the challenges with IoT Hub event routing. You are correct that currently, all event types—such as telemetry, twin changes, lifecycle, and connectivity—are routed into a single EventStream, which means additional filtering or SQL queries are necessary to separate them.

We recognize that this increases pipeline complexity and cost, and your suggestion to enable binding data sources to individual streams is well-founded. As you noted, using separate Event Hubs for each route is a potential workaround, though it can lead to duplicated infrastructure and added overhead.

We encourage you to submit this suggestion to the Fabric Ideas forum, where product teams monitor and prioritize enhancements based on community feedback. This will also give others with similar requirements the opportunity to support your idea.

Fabric Ideas - Microsoft Fabric Community

Thank you.

[v-sgandrathi]

Hi @uriel-kluk,

Just checking in to see if you had a chance to review the suggested solution. If it addressed your issue, please consider marking it as accepted, it could benefit other members facing similar challenges. Always happy to assist.

Thank you.