Azure Digital Twins

Ranked #14 of 14 for digital twin platforms: Metered twin graph service using DTDL models and event routes.

Commercial relationships can affect which products appear and how prominently. The Azure Digital Twins link is marked as every vendor link is, see disclosure.

Visit Azure Digital Twins See it in the digital twin platforms ranking

01

Azure Digital Twins at a glance

HeadquartersNot stated by the vendor
Best forAzure-centred teams wanting a graph API with DTDL models and event routing
DeploymentUnclear from the vendor pages
Free planNone recorded
Pricing modelPay-as-you-go across three usage meters; no plan tiers
APIAzure Digital Twins mentions an API in the material we reviewed
02

What is Azure Digital Twins?

Azure Digital Twins is a Microsoft service for creating live digital models of the physical world. Its product page lists buildings, factories, farms, energy networks, railways, stadiums and cities as targets. Twin types are defined in the Digital Twins Definition Language, an open modelling language, with properties, components and relationships. A live execution environment keeps the twin graph current, historises changes and exposes a query API.

Change events leave the service through event routes to Event Hubs, Event Grid and Service Bus, and data history can flow into Azure Data Explorer. Billing is a single pay-as-you-go model with three meters. The legal page names Microsoft as the provider but states no country for the contracting entity or a registered address, so we record the country as not stated by the vendor.

03

Azure Digital Twins key features

  • DTDL modelling. Twin types are written in DTDL, which the overview calls an open modelling language. A team defines properties, components and relationships once, then creates twins from those definitions.
  • Live twin graph. The execution environment keeps the graph current and exposes a query API for insights. Queries consume query units, which depend on CPU, memory and IOPS.
  • Event routes. Twin change events go to downstream services through Event Hubs, Event Grid and Service Bus. This lets other systems react to a change without polling the graph.
  • Data history. An instance can be connected to Azure Data Explorer so that graph updates are historised there. They can then be queried with the Azure Digital Twins query plugin.
  • Explorer and 3D Scenes Studio. The Azure Digital Twins Explorer offers a visual interface for building and interacting with the graph. 3D Scenes Studio is listed as a preview for 3D visualisation.
  • REST APIs and SDKs. REST APIs and SDKs drive the service from code. Integrations listed include IoT Hub, Logic Apps, Functions, Data Lake, Synapse Analytics and Data Explorer.
  • Access control. Access is handled through role-based access control and Microsoft Entra ID, according to the product page, which also cites over 50 compliance certifications across regions and countries.
04

Who Azure Digital Twins suits

  • A building or campus operator. Buildings and stadiums are named targets. An operator could model spaces and equipment in DTDL and route changes to alerting through Event Grid.
  • An industrial data team on Azure. IoT Hub, Data Lake, Synapse Analytics and Data Explorer are named integrations. A team already using them could place the twin graph between device data and analytics.
  • A developer evaluating cost. Billing counts messages, operations and query units, with no charge in a period of no usage. A developer can build a small prototype and measure query-charge values in responses.
05

Getting started with Azure Digital Twins

The product page links a general Azure offer of free cloud services and a credit for 30 days, since no Digital Twins-specific trial is named. A first project defines a few DTDL models, creates twins and relationships through the REST API, SDK or the Explorer, then adds an event route and watches the usage.

The query API returns a query-charge figure, which shows how many query units a request consumed. The overview points to a separate service limits article that we did not read, so check limits before scaling a prototype. Charges are monthly and based on consumption, with no upfront cost and no termination fee.

06

Verdict: Azure Digital Twins

Azure Digital Twins models twins in DTDL, keeps a live graph, historises changes into Azure Data Explorer and routes events through Event Hubs, Event Grid and Service Bus.

Billing uses three meters, with query units tied to CPU, memory and IOPS, which makes cost hard to forecast before real queries run. The pricing page shows placeholder amounts and names no plan tiers or twin-specific trial.

Azure Digital Twins is entry #14 of 14 in the digital twin platforms list: AWS IoT TwinMaker is the product just above it, and it closes the list. After the challenger places, Azure Digital Twins is one of the established names, ranked in order and without a score.

The vendor states no country of establishment, so Azure Digital Twins is left out of the regional count for this list.

07

Strengths and limits of Azure Digital Twins

What Azure Digital Twins does well
  • Azure Digital Twins models twins in DTDL, keeps a live graph, historises changes into Azure Data Explorer and routes events through Event Hubs, Event Grid and Service Bus.
  • Azure Digital Twins is tagged Event routes in our records.
  • Strongest for: Azure-centred teams wanting a graph API with DTDL models and event routing.
  • Marked in our records as DTDL modelling.
  • Metered billing is among the traits we single out for it.
What to weigh against Azure Digital Twins
  • Query-unit consumption depends on CPU, memory and IOPS, so heavy queries move the bill unpredictably.
  • Not for: Teams needing a fixed price or a ready visual application.
  • The product page does not describe data residency or retention terms.
08

Azure Digital Twins pros and cons in practice

Works well
  • DTDL is described as an open modelling language, which keeps models portable in principle.
  • Billing has no upfront cost, no termination fee and no charge in a period without usage.
  • Event routes reach Event Hubs, Event Grid and Service Bus.
  • Role-based access control and Microsoft Entra ID handle access.
Gets in the way
  • Query units depend on CPU, memory and IOPS, which makes cost hard to forecast before real queries run.
  • The pricing page showed placeholder amounts and no plan tiers.
  • No Digital Twins-specific trial is named, only a general Azure credit offer.
  • 3D Scenes Studio is listed as a preview, and data residency terms are not on the product page.
09

Living with Azure Digital Twins: setup and exit

Digital Twins Explorer offers a visual interface for the graph, and 3D Scenes Studio is listed as a preview.

Access runs through role-based control and Microsoft Entra ID, with REST APIs and SDKs for integration.

10

Azure Digital Twins pricing

Pricing as recorded: Pay-as-you-go across three usage meters; no plan tiers.

One pay-as-you-go model with three meters applies: messages, operations and query units, each billed per million units. Operations are metered per API call in 1 KB increments of the response body, rounded up. Messages on event routes to external destinations are metered in 1 KB increments of payload size. Query units are consumed by CPU, memory and IOPS. The page lists no plan names or tiers, and the per-meter amounts were not visible in the text we read, which showed placeholder values. Prices are calculated in US dollars and converted using exchange rates, with a selector offering 16 currencies. Charges are monthly with no upfront cost, no termination fee and no charge in a period without usage.

Where this comes from: the vendor pages at azure.microsoft.com, checked for Best Digital Twin Platforms in 2026 on 15 November 2026.

11

Azure Digital Twins: data and security

Access is handled through role-based access control and Microsoft Entra ID, according to the product page, which cites over 50 compliance certifications across regions and countries. It does not describe data residency, retention or processing terms, and the overview points to a separate service limits article we did not read.

Data history sends graph updates to Azure Data Explorer, so a second store then holds the history. The legal page names Microsoft as provider but gives no country of the contracting entity or registered address.

12

Fact sheet: Azure Digital Twins

ProductAzure Digital Twins
Vendor websiteazure.microsoft.com
Rank there#14 of 14
Price visibilityModel recorded, no figure
Head-to-head pagesNone yet
Primary guideBest Digital Twin Platforms in 2026
Alternatives pageNo dedicated page
Catalogue tagsDTDL modelling, Event routes, Metered billing
Gaps in our recordsheadcount, funding and customer count
HeadquartersNot stated by the vendor
13

Azure Digital Twins integrations and ecosystem

Integrations the vendor names (9):

  • Azure IoT Hub
  • Azure Logic Apps
  • Azure Functions
  • Azure Data Lake
  • Azure Synapse Analytics
  • Azure Data Explorer
  • Event Hubs
  • Event Grid
  • Service Bus

Also in our records:

  • Access runs through role-based control and Microsoft Entra ID, with REST APIs and SDKs for integration.
14

What to look at instead of Azure Digital Twins

The choice below rests on shared catalogue tags, price model, free plan and region, with rank distance as the tie-break.

  • Eclipse Ditto (#2 of 14): Open source IoT middleware that models connected devices as digital twins. Suits: Engineering teams building their own twin layer over device data without licence fees.
  • Cognite Data Fusion (#7 of 14): Not for: small teams wanting self-serve sign-up with listed prices. Industrial data platform that unifies and contextualises plant data for AI.
  • Matterport (#9 of 14): Immersive 3D capture sold to real estate, facilities and construction teams.
  • Ansys Twin Builder (#10 of 14): Simulation-based twin builder with hybrid analytics and exportable deployments.
15

Also ranked in

16

Questions about Azure Digital Twins

9 answers
Which country is Azure Digital Twins from?

The vendor pages we reviewed state no country of establishment for Azure Digital Twins, so we do not give one.

What does Azure Digital Twins cost?

As recorded: Pay-as-you-go across three usage meters; no plan tiers. On free access, a paid plan is required, per our records.

What are the main alternatives to Azure Digital Twins?

The nearest neighbours in our ranking are Eclipse Ditto, Cognite Data Fusion, Matterport and Ansys Twin Builder. All of them are reviewed in the same ranking.

Where does Azure Digital Twins stand among digital twin platforms?

In our digital twin platforms list Azure Digital Twins stands at place 14 of 14.

Who should choose Azure Digital Twins?

Azure-centred teams wanting a graph API with DTDL models and event routing. It is a weaker match for the following: teams needing a fixed price or a ready visual application.

How is Azure Digital Twins billed?

Through three meters, messages, operations and query units, each billed per million units. The page lists no plan tiers.

Is there a trial?

No Digital Twins-specific free tier or trial is named. The pricing page links to a general Azure offer of free cloud services and a credit for 30 days.

Which modelling language does it use?

The Digital Twins Definition Language, which the overview describes as an open modelling language.

Where does history go?

Data history connects an instance to Azure Data Explorer, where graph updates are historised and can be queried.

17

Azure Digital Twins: sources

Read from the vendor’s own pages on 15 November 2026.

18

How we rank

Four tests decide a position: how soon the product is useful, what the bill really becomes, how data leaves and who it suits. On those tests Azure Digital Twins lands at place 14 of 14. Read the editorial process for the method and where paid visibility fits in.