Helin ontology for DTDL
Central device templates are DTDL. Helin turns them into one ontology of your sites, assets, devices and signals, and carries it into Fabric ontology.

Azure IoT Central migration
Helin Platform runs your fleet on Azure IoT Hub and DPS, keeps your device models and data exports, and streams every signal into Microsoft Fabric.
Free · 45 minutes · Helin engineer
The timeline
In September 2026, Microsoft announced that Azure IoT Central will retire. Existing apps keep working until September 20, 2029. Microsoft recommends moving to Azure IoT Hub and the Device Provisioning Service, with Microsoft Fabric for analytics.
No new IoT Central apps
IoT Central apps retire
How it works
Helin Platform connects your leaf devices and edge fleet to Azure IoT Hub and DPS, turns your DTDL models into a living ontology, and streams every signal into Microsoft Fabric through Helin data pipelines.
Microsoft
Fabric
Helin Platform
One managed platform from the machine to Microsoft Fabric, with a dedicated stack for every customer.
Central device templates are DTDL. Helin turns them into one ontology of your sites, assets, devices and signals, and carries it into Fabric ontology.
A dedicated IoT Hub per customer. Leaf devices send straight to the hub or through the Helin edge, enrolled through DPS with X.509 certificates from Helin’s own PKI.
The Fledge-based Helin Data Collector reads OPC UA, Modbus, MQTT and data from nearby leaf devices, buffers when offline and forwards over mutual TLS.
Route each stream to Fabric Eventhouse, Azure Data Explorer, Kafka, TimescaleDB, MQTT or SFTP, several in parallel.
Change edge configuration from the portal without SSH, and roll out updates over the air.
Device health in Log Analytics and ready-made Grafana dashboards from day one.
Models
What you modelled in Central comes with you. Helin maps every interface, property, command and relationship into one ontology, then carries it into Fabric ontology through Helin data pipelines.
| Device template | Helin ontology | Fabric ontology |
|---|---|---|
| RelationshiplocatedIn | Site | Entity typesite |
| Propertymodel | Asset | Entity typeasset |
| Commandreboot | Device | Commanddevice |
| Telemetrytemperature | Signal | Eventhousetemperature |
Your Central device templates are DTDL models.
Helin reads them into one ontology: sites, assets, devices and signals. Helin data pipelines carry it into Fabric ontology, bound to live data in Eventhouse.
Data
Each Central data export is rebuilt as an IoT Hub route to the same destination, with Microsoft Fabric alongside. Old and new run side by side until the counts match, then device groups move one at a time.
Illustrative message-count comparison.
Same destinations, plus Microsoft Fabric. Both run side by side until the counts match. Then device groups move one at a time. Central stays on as the fallback.
How we do it
The free assessment reads your Central app and maps every device, template and export.
Your dedicated IoT Hub, DPS, vault and database.
Exports become Helin pipelines.
Old and new run in parallel until the message counts match.
Device groups move one at a time, with Central kept on as the fallback.
Book an assessment call
One 45-minute session with a Helin engineer. You leave with two things:
Free assessment. No commitment.
FAQ
Last updated: . Information is subject to change.