Azure IoT Central

Overview

The Azure IoT Central blueprint crawls device templates and deployed devices from Azure IoT Central. It provides visibility into the IoT fleet configuration and enables digital thread traceability to upstream BOM/PLM systems via the PartNumber field.

Resources Collected

• Device Templates: Template definitions including ID, display name, description, PartNumber (from capabilityModel.description), and template type
• Devices: Deployed device instances including ID, display name, template reference, simulated flag, and enabled status

Prerequisites

• Azure IoT Central application
• Application subdomain (e.g. kscope for kscope.azureiotcentral.com)
• API authentication token (SAS token or personal access token)

Setup Instructions

1. Get Application Subdomain

The subdomain is the first part of your Azure IoT Central URL: https://{subdomain}.azureiotcentral.com

2. Generate API Token

1. Open your Azure IoT Central application
2. Navigate to Security > Permissions > API tokens
3. Click New token, select Operator role or higher
4. Copy the generated token

3. Configure Crawler

Field	Description	Required
azureiotAppSubdomain	Azure IoT Central app subdomain	Yes
azureiotApiToken	API token or SAS token	Yes

Data Points

Data Point	Source	Details
Device Templates	Azure IoT Central REST API v2022-07-31	Template ID, display name, PartNumber (from capabilityModel.description)
Devices	Azure IoT Central REST API v2022-07-31	Device ID, display name, associated template ID

Cross-System Correlation

• azureiot.iot.DeviceTemplate.PartNumber (sourced from capabilityModel.description) correlates with aligni.design.Part.ManufacturerPn to link IoT device templates back to BOM parts
• azureiot.iot.DeviceTemplate.PartNumber also correlates with losant.iot.DeviceRecipe.PartNumberTag to link forward to Losant field operations
• See AlignI blueprint and Losant IoT blueprint for the full digital thread setup