Blog Post

Internet of Things Blog
2 MIN READ

Direct IoT Hub-to-Fabric message routing, with context preserved via CloudEvents, in Public Preview

vindhyabanda's avatar
vindhyabanda
Icon for Microsoft rankMicrosoft
Aug 13, 2026

Organizations rely on Azure IoT Hub to securely connect, manage, and route data from millions of devices. As operational data volumes continue to grow, customers are looking for simpler ways to bring device telemetry into analytics, AI, and digital operations solutions without building and maintaining custom integration pipelines. Today we're excited to announce the Public Preview of Microsoft Fabric Eventstreams as a native IoT Hub routing endpoint. Microsoft Fabric provides a unified platform for real-time analytics. By bringing enriched IoT data directly into Fabric, organizations can accelerate the path from data ingestion to insight and action within a managed environment.

Getting started with Microsoft Fabric Eventstreams

Fabric Eventstreams is a service within Microsoft Fabric Real-Time Intelligence that ingests events from multiple sources, transforms them using no-code, low-code event processors, and routes data to various destinations. The platform provides source connectors for multiple event types, optional transformation capabilities, and support for Kafka endpoints, enabling teams to capture and route real-time signals across databases and external data sources. Learn more about Fabric Eventstreams.

Leverage IoT Hub’s routing and enrichment capabilities to land operational data in Microsoft Fabric

The addition of Fabric Eventstreams as an Azure IoT Hub routing endpoint enables organizations to create new or extend existing IoT Hub message routes. Customers can continue using routing rules, filters, and message enrichments configurable in Azure IoT Hub, now with Fabric Eventstreams as a supported destination.

Once data is routed into Fabric, customers can analyze streaming telemetry in real time, filter, transform, or combine device data with business and operational datasets, detect patterns across assets and environments, and trigger actions based on changing conditions. Additionally, customers can route this data to other Fabric destinations like Eventhouse, Lakehouse, etc., set up alerts, and build real-time dashboards.

Preserving operational context with CloudEvents

CloudEvents is an industry-standard envelope, preserved across transports and encodings, that separates event metadata from the event payload. Events routed from Azure IoT Hub to Microsoft Fabric Eventstreams are delivered using the CloudEvents schema, enabling a consistent event format across IoT Hub message types. Learn more about how the schema is structured.

Through the CloudEvents envelope, device identifiers, event timestamps, message identifiers, routing metadata, and IoT Hub enrichments are persisted alongside the payload. Additionally, for customers using Azure IoT Hub instances with Azure Device Registry enabled, the externalID field is carried forward in the payload, helping maintain the connection between telemetry and assets for downstream analytics workflows.

Preserving critical context helps downstream systems understand and act on operational data by retaining the information needed to identify what an event is, where it came from, and what should happen next.

Call to action

Ready to get started? Explore the documentation and share your feedback as you evaluate the preview.

  1. Microsoft Fabric Eventstreams as a routing endpoint (preview)

  2. Understand Azure IoT Hub Message routing - Azure IoT Hub | Microsoft Learn
  3. Understand message format - Azure IoT Hub | Microsoft Learn

For questions or feedback, email us at iotdeviceonboarding@microsoft.com.

Published Aug 13, 2026
Version 1.0

1 Comment

  • devoforge's avatar
    devoforge
    Copper Contributor

    This is a significant improvement for IoT data pipelines. Preserving device identifiers, timestamps, message IDs, routing metadata, and enrichments through CloudEvents should make downstream analytics much easier to implement without maintaining custom integration layers.

    The ability to route IoT Hub telemetry directly into Fabric Eventstreams also looks particularly useful for industrial IoT scenarios where real-time telemetry needs to be combined with operational and business data.

    I’m especially interested in how this performs at scale and how organizations will approach cost and latency when processing high-frequency telemetry from thousands of devices.

    Looking forward to seeing real-world implementations of this architecture during the public preview.