Home Blog Digital Twins IoB and Smart Azure Digital Twins: getting started for enterprises
🧠 Digital Twins IoB and Smart May 21, 2026 12 min read

Azure Digital Twins: getting started for enterprises

Digital Twins IoB and Smart Enterprise Guide 2026 SCALE D2C Digital Twins IoB and Smart Enterprise Guide 2026

Azure Digital Twins (ADT) is Microsoft's managed service for building real-time digital twin graphs β€” modelling the relationships between physical assets, spaces, and processes as a queryable, live-updating graph of interconnected twin instances. For enterprises already on Azure, ADT provides the lowest-friction path from IoT sensor data to a structured, queryable digital twin environment. This getting-started guide covers ADT architecture, DTDL modelling, data ingestion, and the integration patterns that connect ADT to enterprise analytics.

ADT Architecture

Azure Digital Twins β€” Core Concepts
ADT has four core concepts: (1) Digital Twin Definition Language (DTDL) β€” a JSON-LD based schema language for defining what a twin looks like: its properties, telemetry, commands, relationships, and components; (2) Twin instances β€” individual objects in the ADT graph, each conforming to a DTDL model; (3) Relationships β€” directed edges between twins (a floor "contains" a room, a sensor "isPartOf" a machine); (4) Event routing β€” ADT emits events to Event Grid/Event Hub when twin properties change, enabling downstream processing in Azure Functions, Stream Analytics, or custom services.

DTDL Modelling Guide

DTDL models define the shape of your digital twin types. Good DTDL design starts with your physical ontology β€” what types of assets exist, what properties do they have, and how do they relate?

DTDL CapabilityPurposeExample
@type: PropertyStatic or slowly-changing attributeFloorNumber, MaxOccupancy, ManufacturerName
@type: TelemetryHigh-frequency sensor readings β€” streamed, not storedTemperature, Vibration, OEE
@type: RelationshipDirected edge to another twin typecontains, isLocatedIn, controls
@type: ComponentEmbedded sub-model within a twinMotor component within a CNC machine model
ExtendsInheritance β€” reuse common properties across model typesCNCMachine extends AssetBase
ADT Explorer
Azure Digital Twins Explorer (explorer.digitaltwins.azure.net) β€” the visual interface for importing DTDL models, creating twin instances, editing relationships, and running graph queries. The fastest way to validate your DTDL design before writing code
ADX
Azure Data Explorer integration β€” ADT's time-series history flows automatically to ADX via the ADT-to-ADX data history connection. Enables complex time-series analytics and joins between twin properties and telemetry history without custom pipeline development
Real Industry Ontologies
DTDL ontologies exist for buildings (RealEstateCore), smart manufacturing (ISA-95), energy (DTDL Energy Grid), and smart cities β€” import these as starting points rather than modelling from scratch
01
Step 1
Provision ADT and Upload Models

Create ADT instance: az dt create --resource-group my-rg --name my-adt --location eastus. Assign RBAC: az dt role-assignment create --dt-name my-adt --assignee your-object-id --role "Azure Digital Twins Data Owner". Upload your DTDL model files: az dt model create --dt-name my-adt --models ./models/. Open ADT Explorer to verify models loaded correctly. Import community ontologies from github.com/Azure/opendigitaltwins-building or similar repos as starting points. Our DevOps team handles ADT IaC setup.

az dt createDTDL model uploadADT Explorer validation
02
Step 2
Ingest IoT Data via Azure Functions

Data flow: IoT Hub β†’ Event Hub trigger β†’ Azure Function β†’ ADT SDK update. Write a Function that: receives IoT Hub messages, extracts device ID and telemetry values, calls client.UpdateDigitalTwin(twinId, patchDocument) on the ADT SDK. The patch document uses JSON Patch format to update specific properties. For high-volume telemetry, consider ADT's telemetry type (not stored in graph, forwarded to Event Grid for downstream time-series storage). Connect ADT to Azure Data Explorer for historical analytics.

IoT Hub β†’ Event Hub β†’ FunctionUpdateDigitalTwin SDKADX data history
03
Step 3
Query and Visualise

ADT uses its own SQL-like query language (ADTQ): SELECT * FROM DIGITALTWINS WHERE IS_OF_MODEL('dtmi:myco:CNCMachine;1'). Query the twin graph for aggregations: find all machines in a specific building section, calculate average OEE across a production line. Connect to Power BI via the ADT Query plugin for operational dashboards. Use ADT Explorer for ad-hoc queries during development. For production alerting, route ADT twin-change events via Event Grid to Azure Functions that trigger PagerDuty or your alerting platform.

ADTQ query languagePower BI connectorEvent Grid alerting
Azure Digital Twins Implementation

Our IoT solutions, data analytics, and DevOps teams design and deploy Azure Digital Twins solutions from single-asset pilots to enterprise-wide facility twin programmes. Book a free advisory session.

Frequently Asked Questions

End-to-end Digital Twins IoB and Smart strategy, implementation, and optimisation. Contact us for a free consultation.

Strategy: 4–8 weeks. Full implementation: 3–12 months.

Yes β€” D2C brands to enterprise. View our pricing.

DIGITAL TWIN

Ready to Implement Digital Twins IoB and Smart?

Our specialist team delivers measurable ROI for enterprise and D2C brands.

Free Audit