How to bring high-volume IoT and OT telemetry together with ERP data in Microsoft Fabric OneLake, using Delta Parquet storage, Direct Lake reporting and Azure AI models.
Operational telemetry and enterprise data usually live apart. SCADA and IoT streams sit on one side, ERP and CRM records on the other, and the questions that matter most, such as what a unit of output actually costs, need both. Microsoft Fabric lets you land the two in one governed OneLake lakehouse and report on them together.
One Copy of Data with OneLake and Direct Lake
Store everything as Delta Parquet tables in OneLake, and Power BI's Direct Lake mode reads those tables directly. There is no scheduled import refresh and no duplicated extract to keep in step. High-frequency telemetry and business data share one copy and one set of definitions.
- Delta Parquet as the single, open storage format for every table.
- Direct Lake for near-real-time reporting without import cycles.
- One governance and lineage model across OT and IT data.
Landing Telemetry Alongside ERP
Telemetry arrives as a stream. The pattern below reads meter events from Event Hubs, parses them against a declared schema and writes them continuously to a Delta table, with a checkpoint so the stream resumes cleanly after a restart.
(spark.readStream.format("eventhubs").options(**conf).load()
.select(from_json("body", schema).alias("m"))
.writeStream.format("delta")
.option("checkpointLocation", chk)
.toTable("onelake.telemetry.meter_reads"))The result is a single analytics surface where a plant manager and a finance analyst query the same lakehouse, with telemetry, cost and outcomes side by side and one version of each number.
Tagged Under

KoderTroop Systems Squad
Technical Authors
Articles are written by KoderTroop specialists and architects who design and deliver embedded systems, cloud platforms, edge computing and applied AI for our clients.