Forum Discussion
Adding an MQTT Broker as Data Source in Real-Time Intelligence
Dear Fabric Community,
I’ve been testing the functionality to directly ingest MQTT messages (from a Broker using MQTT v5) into Microsoft Fabric — specifically into an Event Stream.
Overall, it works 'well'. However, I noticed something missing: a crucial part of our telemetry is contained in the MQTT topic itself, but this information doesn’t seem to appear anywhere in the event data.
For example, I can see the actual payload (e.g., temperature = 34°C), but there’s no way to identify which device sent it, since the topic is not exposed or stored.
Could you please confirm whether this is the expected behavior, or if I might be overlooking a configuration option?
Thank you in advance for your insights — I really appreciate it.
Kind regards,
Omar
Hi, omarecd Thank you for sharing your feedback through the community post.
Your expection to have the message headers to be shown for previewing or downstream transformation is absolutely reasonable. We also receive the similar ask to expose the message headers for other Eventstream connectors. So, we have this feature in our backlog and we will plan it accordingly.
4 Replies
Hi, omarecd Thank you for sharing your feedback through the community post.
Your expection to have the message headers to be shown for previewing or downstream transformation is absolutely reasonable. We also receive the similar ask to expose the message headers for other Eventstream connectors. So, we have this feature in our backlog and we will plan it accordingly.
By the way, dear xujx ,
I wanted to mention something else. The MQTT datasource in Fabric currently seems to accept only MQTT v5.0.
This means that for devices using v3.1.1 — which is, by the way, still the most widely adopted and commonly used version in IoT applications — we need to set up a bridge to receive data in v3.1.1 and then re-publish it in v5.0. So far, this approach works fine, but it does add some complexity since it introduces an additional component from a third party (see image below).
Would it be possible to consider adding support for v3.1.1 directly? Given how popular this version is, I’m sure it would be highly appreciated by many users.
Let me know what you think.
Best regards,
OmarThis is being worked as of now. It will be available in coming two or three months. Stay tuned.
