Skip to main content
Industrial robotic arms on an automotive production line

Azure IoT Central migration

Leave IoT Central.
Land on Helin Platform.

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

IoT Central is retiring.
Your devices and data can stay.

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

From your devices to Microsoft Fabric.

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.

Leaf device
OPC UA
Modbus
MQTT
Helin edgeData Collector X.509
Helin PlatformPowered by Azure
IoT Hub + DPS

Microsoft

Fabric

  • Eventstream
  • Eventhouse
  • Dashboards
  • Ontology
Leaf devices can connect directly to IoT Hub or through the Helin edge. Helin data pipelines carry your signals into Microsoft Fabric.

Helin Platform

Your fleet on Azure IoT Hub, run by Helin.

One managed platform from the machine to Microsoft Fabric, with a dedicated stack for every customer.

13+
industrial protocols at the edge
X.509
identity on every device
80–95%
less bandwidth with delta filtering
1
dedicated hub, vault and database per customer

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 Hub and DPS

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.

Helin edge

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.

Helin data pipelines

Route each stream to Fabric Eventhouse, Azure Data Explorer, Kafka, TimescaleDB, MQTT or SFTP, several in parallel.

Remote operations

Change edge configuration from the portal without SSH, and roll out updates over the air.

Observability

Device health in Log Analytics and ready-made Grafana dashboards from day one.

Models

Your DTDL models become the Helin ontology.

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.

DTDL device templates mapped to Helin and Fabric ontology
Device templateHelin ontologyFabric ontology
RelationshiplocatedInSiteEntity typesite
PropertymodelAssetEntity typeasset
CommandrebootDeviceCommanddevice
TelemetrytemperatureSignalEventhousetemperature

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

Every export becomes a Helin pipeline.

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.

Central exportHelin pipelineDestination
Telemetry
TelemetryIoT Hub route
Fabric Eventhouse
Properties
PropertiesIoT Hub route
Blob storage
Alerts
AlertsIoT Hub route
Event Hubs
Central 1,200 msgsHelin 1,200 msgsCounts match

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

How the move runs.

  1. 01

    Assess

    The free assessment reads your Central app and maps every device, template and export.

  2. 02

    Setup

    Your dedicated IoT Hub, DPS, vault and database.

  3. 03

    Rebuild

    Exports become Helin pipelines.

  4. 04

    Run side by side

    Old and new run in parallel until the message counts match.

  5. 05

    Move device groups

    Device groups move one at a time, with Central kept on as the fallback.

Book my assessment

Book an assessment call

Your migration plan, and your first edge application.

One 45-minute session with a Helin engineer. You leave with two things:

  • A migration outline
  • A first use case

Free assessment. No commitment.

Book your migration assessment

No commitment. The outline is yours either way.

FAQ

Questions about your migration

No new IoT Central apps can be created from September 23, 2026. Existing apps keep working until September 20, 2029.

Yes. Helin maps your DTDL interfaces, properties, commands and relationships into an ontology of sites, assets, devices and signals, then carries it into Fabric ontology.

Each export is rebuilt as an IoT Hub route to the same destination, with Microsoft Fabric alongside. Both run in parallel until the message counts match, then device groups move one at a time.

The Helin Data Collector buffers data when offline and forwards it over mutual TLS when connectivity returns.

Nothing. One 45-minute session with a Helin engineer gives you a migration outline and a first use case, with no commitment.

Last updated: . Information is subject to change.