Azure Digital Twins

About Azure Digital Twins

Azure Digital Twins is a Microsoft Azure platform service for building live digital representations of physical environments, assets and business systems. Teams define models for people, places and things, create digital twins from those models, connect the twins through relationships, and query the resulting graph. Microsoft positions the service as part of a wider IoT and data architecture rather than as a complete device platform on its own. It is distinct from IoT Hub device twins and from digital twin builder in Microsoft Fabric.

What is Azure Digital Twins used for?

Azure Digital Twins is designed for situations where relationships and physical context matter as much as individual sensor readings. Microsoft gives examples such as buildings, factories, farms, energy networks, railways, stadiums and cities. A team can represent these environments as models and keep individual twins updated from connected devices or business systems.

This lets operators reason about an environment instead of only about device IDs. For example, a temperature reading can be associated with a room, floor, building and cooling system. The twin graph can then be queried to investigate how assets, locations and systems relate to one another.

How do DTDL models and the twin graph work?

Azure Digital Twins uses Digital Twins Definition Language, or DTDL, to describe model types. Microsoft documents properties, components and relationships as core parts of the model structure. Teams can design their own model sets or use published DTDL industry ontologies where an existing vocabulary fits the domain.

Digital twins are instances of those models. Relationships connect the twins into a graph that represents the broader environment. This graph structure is a major reason to choose Azure Digital Twins instead of keeping unrelated device records in a conventional application database.

How does Azure Digital Twins connect to IoT and business systems?

Azure Digital Twins can work with Azure IoT Hub to bring device data into a wider model of an environment. Microsoft also documents REST APIs and integrations with services such as Logic Apps for bringing in business data. Azure Functions can provide custom event processing and business logic.

The service does not replace all of those components. A production solution may also require device ingestion, compute, messaging, storage, analytics, identity and monitoring. Buyers should therefore estimate and design the complete architecture rather than treating the Digital Twins instance as the whole IoT platform.

How can teams query and historize twin data?

Azure Digital Twins provides a query API for retrieving information from the live twin graph. Queries can use property values, relationships, relationship properties and model information. APIs and SDKs are also available for managing instances, models, twins and relationships.

For historical analysis, Microsoft documents a data history capability that connects Azure Digital Twins with Azure Data Explorer so graph updates can be historized and queried over time. Event routes can also send data to Event Hubs, Event Grid and Service Bus for downstream processing, analytics or custom workflows.

What visualization tools are available?

Microsoft provides Azure Digital Twins Explorer as a preview tool for visualizing and working with twin graphs. It can run queries, display twins and relationships, inspect models and help manage graph data. Microsoft also documents that the hosted Explorer does not support private endpoints. Organizations using Private Link can deploy the open source Explorer code privately instead.

Microsoft also offers 3D Scenes Studio as a preview capability for connecting digital twin information to 3D representations of physical environments. Because both tools carry preview considerations, buyers should check current preview terms, data handling requirements and production support before making either interface part of a critical operating process.

How does Azure Digital Twins pricing work?

Pricing was checked against Microsoft's Azure Digital Twins pricing page on September 3, 2026. Microsoft currently bills the service through three usage dimensions: operations, messages and query units. API calls count as operations, outbound event-route traffic can count as messages, and graph queries consume query units according to the resources required to execute them.

Microsoft states that there is no upfront cost or termination fee and that an instance with no operations, messages or query units during the billing period does not incur Azure Digital Twins usage charges. Connected services such as IoT Hub, Functions, Event Hubs, Azure Data Explorer, storage and networking can still generate separate charges.

What are the main limitations and planning considerations?

Azure Digital Twins is a platform component that requires solution design and development. Teams still need to create a useful domain model, maintain relationships, connect data sources, implement event processing and decide how applications will consume the graph. A weak model can make the environment hard to understand even when the Azure service itself is healthy.

Service limits and rate limits also matter at larger scale, so Microsoft recommends reviewing the current service limits during architecture planning. Region availability, private networking requirements, downstream costs and the support status of preview tools should also be checked before production deployment.

How is Azure Digital Twins different from IoT Hub device twins?

Microsoft explicitly distinguishes Azure Digital Twins from the device twins used by Azure IoT Hub. An IoT Hub device twin stores state and metadata associated with an individual device. Azure Digital Twins models broader environments and the relationships among people, places, assets and systems.

The two can work together. IoT Hub can provide device connectivity and telemetry that helps keep an Azure Digital Twins graph current. Buyers should treat them as complementary services when a solution needs both device management and an environment-level graph.

Who should choose something else?

A team that only needs device ingestion, device state or device management may be better served by Azure IoT Hub without adding a full environment graph. A conventional relational, document or graph database may also be simpler when the data is not tied to a live physical environment or when the organization already has an application model that meets the requirement.

Azure Digital Twins is most useful when physical context, relationships and changing operational state are central to the problem. If the project is primarily business analytics, workflow automation, asset inventory or dashboard reporting, buyers should compare the relevant Azure data, analytics and integration services before adding digital twin modeling complexity.