Service Bus Connector

Route device events to Azure Service Bus for enterprise-grade messaging with queues and topics. Guaranteed FIFO delivery, dead-letter handling, and transactional operations for mission-critical IoT event processing.

What is Service Bus

Azure Service Bus is a fully managed enterprise message broker supporting queues (point-to-point) and topics (publish-subscribe). It provides reliable message delivery with advanced features like sessions, transactions, and scheduled delivery.

Key Features:

Guaranteed Delivery: Messages are durably stored and guaranteed to be delivered, even during consumer outages.

FIFO with Sessions: Strict first-in-first-out ordering with message sessions for sequenced processing.

Dead-letter Queue: Failed messages automatically moved to DLQ for inspection and reprocessing.

Duplicate Detection: Automatic deduplication of messages within a configurable time window.

Scheduled Delivery: Schedule messages for future delivery with precision timing.

How it Works

When the Service Bus connector is enabled, /IOTCONNECT™ sends device events as messages to your Service Bus queue or topic:

Device triggers event → Telemetry, fault, or diagnostic event is generated.

Message created → Event data is formatted as a Service Bus message with properties.

Sent to queue/topic → Message is sent to your configured Service Bus entity.

Consumer processes → Your applications receive and process messages from the queue/subscription.

User Manual

Step 1: Navigate to Connector Settings

Go to Settings > Configuration > Live Data Streaming in the /IOTCONNECT™ portal.

Step 2: Enable Service Bus

Find the Service Bus connector card and toggle the switch to ON (green).

Step 3: Select Data Types

Choose which data to route: Telemetry, Faulty, Diagnostics, Command History.

Step 4: Run ARM Template

Click the ARM template link. This deploys:

A Service Bus namespace (Standard or Premium tier)

Queue or Topic with configured dead-letter handling

Shared Access Policy for cross-tenant message sending

Step 5: Confirm Subscription ID

Subscription ID auto-populates after deployment.

Step 6: Save

Click Save. Events begin flowing to your Service Bus queue.

Use Cases

Order Processing: Process device commands and OTA operations in guaranteed sequence.

Microservice Decoupling: Decouple IoT data producers from downstream consumers with reliable queues.

Work Distribution: Load-balance telemetry processing across multiple worker instances.

Workflow Orchestration: Trigger multi-step business workflows from device events.

Cross-system Integration: Bridge IoT data to ERP, CRM, and ticketing systems via Service Bus subscriptions.

ⓘ NOTE

Service Bus Premium tier provides dedicated resources and predictable performance for high-volume IoT workloads. Messages can be retained for up to 14 days. Use topics with subscriptions for fan-out to multiple consumers.