Azure Digital Twins Model Builder

MonitoringAzure

Build Digital Twins DTDL v3 model configs with properties, telemetry, relationships, commands, components, and event routes.

Azure Digital Twins Configuration

Build Digital Twins DTDL v3 model configs with properties, telemetry, relationships, commands, components, event routes, and endpoints.

Required Fields

instanceNamemodelsmodels[0].@idmodels[0].@typemodels[0].contents

{
  "instanceName": "adt-contoso-smartbuilding",
  "resourceGroup": "rg-digital-twins",
  "location": "eastus2",
  "hostName": "adt-contoso-smartbuilding.api.eus2.digitaltwins.azure.net",
  "models": [
    {
      "@id": "dtmi:contoso:Building;1",
      "@type": "Interface",
      "displayName": "Building",
      "description": "A building in the campus.",
      "contents": [
        {
          "@type": "Property",
          "name": "name",
          "schema": "string",
          "description": "Building name"
        },
        {
          "@type": "Property",
          "name": "address",
          "schema": "string"
        },
        {
          "@type": ["Property", "Latitude"],
          "name": "latitude",
          "schema": "double"
        },
        {
          "@type": ["Property", "Longitude"],
          "name": "longitude",
          "schema": "double"
        },
        {
          "@type": "Relationship",
          "name": "hasFloor",
          "target": "dtmi:contoso:Floor;1",
          "properties": [
            {
              "@type": "Property",
              "name": "isAccessible",
              "schema": "boolean"
            }
          ]
        }
      ],
      "@context": "dtmi:dtdl:context;3"
    },
    {
      "@id": "dtmi:contoso:Floor;1",
      "@type": "Interface",
      "displayName": "Floor",
      "contents": [
        {
          "@type": "Property",
          "name": "floorNumber",
          "schema": "integer"
        },
        {
          "@type": ["Telemetry", "Temperature"],
          "name": "temperature",
          "schema": "double",
          "unit": "degreeCelsius"
        },
        {
          "@type": ["Telemetry", "Humidity"],
          "name": "humidity",
          "schema": "double",
          "unit": "percent"
        },
        {
          "@type": "Telemetry",
          "name": "occupancy",
          "schema": "integer"
        },
        {
          "@type": "Relationship",
          "name": "hasRoom",
          "target": "dtmi:contoso:Room;1"
        },
        {
          "@type": "Component",
          "name": "hvac",
          "schema": "dtmi:contoso:HVAC;1"
        }
      ],
      "@context": "dtmi:dtdl:context;3"
    },
    {
      "@id": "dtmi:contoso:Room;1",
      "@type": "Interface",
      "displayName": "Room",
      "contents": [
        {
          "@type": "Property",
          "name": "roomName",
          "schema": "string"
        },
        {
          "@type": "Property",
          "name": "capacity",
          "schema": "integer"
        },
        {
          "@type": "Property",
          "name": "roomType",
          "schema": {
            "@type": "Enum",
            "valueSchema": "string",
            "enumValues": [
              { "name": "conference", "enumValue": "Conference" },
              { "name": "office", "enumValue": "Office" },
              { "name": "lobby", "enumValue": "Lobby" },
              { "name": "breakRoom", "enumValue": "BreakRoom" }
            ]
          }
        },
        {
          "@type": ["Telemetry", "Temperature"],
          "name": "temperature",
          "schema": "double",
          "unit": "degreeCelsius"
        },
        {
          "@type": "Telemetry",
          "name": "isOccupied",
          "schema": "boolean"
        },
        {
          "@type": "Command",
          "name": "setTemperature",
          "request": {
            "name": "targetTemp",
            "schema": "double"
          },
          "response": {
            "name": "result",
            "schema": "string"
          }
        }
      ],
      "@context": "dtmi:dtdl:context;3"
    },
    {
      "@id": "dtmi:contoso:HVAC;1",
      "@type": "Interface",
      "displayName": "HVAC System",
      "contents": [
        {
          "@type": "Property",
          "name": "model",
          "schema": "string"
        },
        {
          "@type": ["Telemetry", "Temperature"],
          "name": "setPoint",
          "schema": "double",
          "unit": "degreeCelsius"
        },
        {
          "@type": "Property",
          "name": "mode",
          "schema": {
            "@type": "Enum",
            "valueSchema": "string",
            "enumValues": [
              { "name": "cooling", "enumValue": "Cooling" },
              { "name": "heating", "enumValue": "Heating" },
              { "name": "auto", "enumValue": "Auto" },
              { "name": "off", "enumValue": "Off" }
            ]
          }
        }
      ],
      "@context": "dtmi:dtdl:context;3"
    }
  ],
  "eventRoutes": [
    {
      "name": "route-to-eventhub",
      "endpointName": "ep-eventhub-telemetry",
      "filter": "type = 'Microsoft.DigitalTwins.Twin.Update'"
    },
    {
      "name": "route-to-tsi",
      "endpointName": "ep-tsi-environment",
      "filter": "type = 'Microsoft.DigitalTwins.Twin.Update' AND $body.temperature != null"
    }
  ],
  "endpoints": [
    {
      "name": "ep-eventhub-telemetry",
      "type": "EventHub",
      "connectionString": "Endpoint=sb://evhns-contoso-adt.servicebus.windows.net/;EntityPath=adt-telemetry",
      "authenticationType": "IdentityBased"
    }
  ]
}

Generated Output

Output will appear here...

Overview

Build Digital Twins DTDL v3 model configs with properties, telemetry, relationships, commands, components, and event routes. This tool helps Azure engineers generate valid configurations quickly without consulting documentation, reducing errors and accelerating infrastructure deployment. All processing runs in your browser with no data sent to external servers.

How Engineers Use This

•Producing a Digital Twins Model starting point for a new service that follows the Azure reference architecture rather than copy-paste from another team's repo.
•Drafting a Digital Twins Model change for an Azure Bicep or Terraform module before raising the pull request, so reviewers can see intent in plain text.
•Comparing two candidate Digital Twins Model layouts side by side to pick the one with the cleaner permission boundary.
•Showing a security or compliance reviewer a proposed Digital Twins Model configuration without forcing them through the Azure portal.

Questions & Answers

Can I use this Digital Twins Model builder for Azure Government or sovereign clouds?

Most Digital Twins Model primitives behave the same across commercial, Government, and other sovereign Azure clouds, but the endpoints, available regions, and a handful of services differ. The output is portable in terms of resource shape; you must verify service availability and adjust endpoints when targeting a sovereign cloud.

How does this Digital Twins Model builder keep up with new Azure features?

The Digital Twins Model options surface what is currently documented in the Azure reference for that service. When Microsoft adds a new property or value, we add it here after verifying the schema in a real subscription. If a recently-announced feature is not yet selectable, treat that as a 'not yet supported' signal rather than an opinion that it should not be used.

Related Learning Guides

Cost Management Guide24 min read
Azure Monitor & Application Insights26 min read

Was this tool helpful?

Disclaimer: This tool runs entirely in your browser. No data is sent to our servers. Always verify outputs before using them in production. AWS, Azure, and GCP are trademarks of their respective owners.