Forum Discussion
Regarding Adding reference data to my stream in Microsoft fabric event stream.
Makes sense. In this case, the pattern is established. Eventstream loads the initial stream into Eventhouse, where the stream is contextualized with the reference data and written to a new table. Then create a new eventstream that uses an Azure Data Explorer source (with the Eventhouse uri information). Even though the source says ADX Eventhouse is the same engine.
Then add a custom endpoint destination where your customer can subscribe. THe other thing you could consider is rather streaming back into the eventstream simply make the data available in eventhouse via the rest api
Hi Venu,
You’re right — as of now, Fabric Event Streams doesn’t directly allow adding a Lakehouse table as reference data in the same way you can with a Fabric SQL database. The demo you mentioned uses a Fabric SQL DB because reference data sources currently need to be queryable in a structured format.
A couple of workarounds you can try:
Materialize your Lakehouse table into a Fabric SQL Database (via shortcut or pipeline), then reference that SQL table in your Event Stream.
If the reference data is relatively static, you could also pre-load it into a small external store (like Azure SQL DB) and link it in as reference data.
Keep an eye on updates—support for direct Lakehouse integration as reference data has been a frequent ask and may get added in future releases.
For now, the most straightforward route is to use a Fabric SQL DB as the bridge.