Implement Business Integration
What you must know
Business integration means moving IoT data into line-of-business systems. Know IoT Hub message routing with queries on message properties, twin properties, and body, and the endpoints: Event Hubs, Service Bus queues and topics, Blob Storage, and custom endpoints. Understand message enrichment (adding static or twin-derived properties) and filtering with the message routing query language.
Know Event Grid integration for reactive, event-driven flows (device created, device connected, telemetry) and Logic Apps or Azure Functions for orchestration. Understand Azure Stream Analytics as the stream processing engine for windowed aggregation and anomaly detection, and Time Series Insights for time-series exploration.
Traps
- Confusing Event Grid (discrete events, push) with Event Hubs (high-volume telemetry stream).
- Assuming message routing can transform the payload - it cannot; use Stream Analytics or Functions for transformation.
- Forgetting that routing queries must reference valid system or application properties; unknown property names silently fail to match.
- Assuming a single route can have multiple endpoints - each route has one endpoint.
Rule of thumb
If the requirement is "notify when a device connects", use Event Grid. If it is "aggregate temperature over 5-minute windows", use Stream Analytics. If it is "send only alerts above a threshold to a queue", use message routing with a query.
Worked example
To route only messages where temperature > 30, create a route with the query temperature > 30 and endpoint a Service Bus queue. Add enrichment { "building": "A" } so downstream consumers do not need to look up device metadata.