Configure Azure IoT Central continuous data export to stream device data to Blob Storage, Event Hubs, or Service Bus
domain: iot · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Confirm you have the Data export permission in your IoT Central application
Create the destination resource (Storage account/container, Event Hubs namespace/hub, or Service Bus namespace/queue or topic) and assign your IoT Central app's system-assigned managed identity the matching role (Storage Blob Data Contributor for Blob Storage, Azure Event Hubs Data Sender for Event Hubs, Azure Service Bus Data Sender for Service Bus)
In IoT Central, go to Data export > + New destination, pick the destination type, choose managed identity or connection string auth, and enter the endpoint/host name plus container, event hub, or queue/topic name
Create a new export: select the data type(s) to stream (telemetry, property changes, device connectivity, device lifecycle, device template lifecycle, or audit logs), optionally add filters and enrichments
Attach the destination(s) to the export (up to 5 per export) and save — data begins streaming continuously from that point forward in near real time (Blob Storage batches and writes once per minute)
Known gotchas
Data export only streams data from the moment it's turned on — there's no way to backfill historical data through this feature (use the REST API to query past data instead)
Use the Storage Blob Data Contributor role for Blob Storage exports, not Storage Account Contributor as shown in Microsoft's own walkthrough video
Exported messages can take up to 60 seconds to reach the destination, measured from when IoT Central receives the message from the underlying IoT hub
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?