Forum Discussion

uriel-kluk's avatar
uriel-kluk
Regular Visitor
11 months ago
Solved

Bind IoT Hub Data Sources to separate streams

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 unit...
  • v-sgandrathi's avatar
    11 months ago

    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.