Azure Digital Twins

Azure Digital Twins is a platform that provides organizations with the foundation they need to create the next generation of IoT solutions. With Azure Digital Twins, you can virtually replicate the physical world by modeling the relationships between people, places, and devices in a special intelligence graph. You can use predefined data schema that are aligned to a solution’s domain-specific needs and that can accelerate and simplify it’s creation. You can query data in the context of a space rather than from disparate sensors. And you can build solutions that scale and replicate across multiple tenants.

More details are available in the Azure Digital Twins documentation. If you have a technical issue, please open a post on the developer forums through Stack Overflow.

  1. Making a graph viewer available in the Azure portal

    To easily get a clear overview of the Digital Twins hierarchy of spaces, it would be great to add a (readonly) graph viewer for Digital Twins. A graph viewer has already been build and published to GitHub. Why not add this option to the Azure portal as the Digital Twins Explorer. (https://github.com/Azure/azure-digital-twins-graph-viewer)
    Optionaly the explorer could be used to add, modify of delete spaces, devices or sensors in a non-readonly mode.

    7 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Feature Request  ·  Flag idea as inappropriate…  ·  Admin →
  2. Explain how to access the IoT Hub created by the sample Azure Digital Twins

    I started using ADT with the samples provided, and the "occupancy-quickstart" project created an IoT Hub automatically. I can send events to it and redirect them to another location using endpoints, but I don't see the hub anywhere in our subscription, and as such, I cannot manage it. Also, it doesn't appear when I run the "az iot hub list" command in the Azure console.
    So, how can we access that hub? Or maybe a best practice would be to create one hub beforehand and assign it to the root of the ADT space tree by hand?
    Thanks for clarifying…

    20 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Feature Request  ·  Flag idea as inappropriate…  ·  Admin →
  3. Postman Collection for download

    It save a lot of time if there was a downloadable Postman collection with the API calls already defined (as with Swagger). It is simple to export/import a collection and environments can be used to ensure that credentials are kept separate.

    5 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  4. Creditings continueosly myuba accts2064835406,interswitch reward money And Others.

    Myuba accts 2064835406,interswtich reward money And Others.Amounts 3000000.50000,20000,5000,240000500,234567,90000,+.Digital,Autopay,Webpay.Salaries my Director,more.All travelings And Others.

    1 vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Feature Request  ·  Flag idea as inappropriate…  ·  Admin →
  5. We are service integrators, would like to understand how the spacial maps are created, say the Map of Building

    We are service integrators, would like to understand how the spacial maps are created, say the Map of Building

    1 vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Feature Request  ·  Flag idea as inappropriate…  ·  Admin →
  6. Error 500.600.999.999

    After deleting my Digital Twins instance and deploying one with the same name a few minutes later I can't make any requests to the instance without the following error:

    {
    "error": {
    "code": "500.600.999.999",
    "message": "The underlying provider failed on Open.",
    "innererror": {
    "code": "500.600.999.999",
    "message": "Login failed for user 'ManagementApi'."
    }
    }
    }

    This occurs on a GET request to
    https://<instance-name>.westeurope.azuresmartspaces.net/management/api/v1.0/devices

    4 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Bug  ·  Flag idea as inappropriate…  ·  Admin →
  7. Support for building the Azure Digital Twin special model from the existing automation systems.

    Support for building the Azure Digital Twin special model from the existing automation systems which are based on Industry standard like ISA95, ISA106, AutomationML

    1 vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Feature Request  ·  Flag idea as inappropriate…  ·  Admin →
  8. Backup/restore feature Azure Digital Twins API

    The user is able to create a backup of ADT data and restore it using by ADT API. It's possible to backup one subscription and restore data in other empty subscription

    5 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  9. Unable to push data for some sensor hardware ids

    I made a setup using the csharp ProvisionSample flow.

    Simplified the user defined function to just set the sensor value in the graph:

    function process(telemetry, executionContext) {

    try {
    // Log SensorId and Message
    log(`Sensor ID: ${telemetry.SensorId}. `);
    log(`Sensor value: ${JSON.stringify(telemetry.Message)}.`);

    // Get sensor metadata
    var sensor = getSensorMetadata(telemetry.SensorId);

    // Retrieve the sensor reading
    var parseReading = JSON.parse(telemetry.Message);

    // Set the sensor reading as the current value for the sensor.
    setSensorValue(telemetry.SensorId, sensor.DataType, parseReading.SensorValue);

    } catch (error) {
    log(`An error has occurred processing the UDF Error: ${error.name} Message ${error.message}.`);
    }
    }

    Created some spaces, with a device in one of them,…

    5 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  Bug  ·  Flag idea as inappropriate…  ·  Admin →
  10. Moving a device from a space to another does not automatically move the attached sensors

    Hello,

    I recently moved a device from one spaceId to another via API call from Postman. To my surprise, the sensors attached to that device were still assigned to the previous spaceId. But, in the Azure Digital Twins Graph Viewer, they were properly displayed. Is this a bug in the API or is it a desired behaviour?

    Kind regards,
    Tudor Mazilu

    3 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Bug  ·  Flag idea as inappropriate…  ·  Admin →
  11. Please fix the ErrorInformation metadata produced in the Open API spec for Digital Twins

    Here's what the API metadata says is produced for ErrorInformation when creating a new Device with a POST call:

    {
    "code": "string",
    "message": "string",
    "target": "string",
    "details": [
    null
    ],
    "exception": {}
    }

    Here's what's actually produced:

    {"error":{"code":"400.600.000.000","message":"Device already exists."}}

    The claimed ErrorInformation object is actually a child of what's produced in the "error" property, rather than being the root object. Please fix this as it is breaking our error handling strategies for Digital Twin.

    2 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Bug  ·  Flag idea as inappropriate…  ·  Admin →
  12. Link arbitrary sensor data types to arbitrary data sub types/data unit types

    Currently, if you'd add a new sensor, for instance a 'Gas' sensor, we'd like to provide the following types:
    Type: Manufacturer
    Data type: Gas
    Data sub type: Delivery
    Data unit type: CubicMeterGas

    However, the Data sub type has to be named 'DeliveryGas'. Even though we'd also like an Energy sensor with:
    Type: Manufacturer
    Data type: Energy
    Data sub type: Delivery
    Data unit type: KilowattHourEnergy

    Now we have to define two separate sub types. If this is by design, let us know :)

    9 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Feature Request  ·  Flag idea as inappropriate…  ·  Admin →
  13. IotHub Device Configuration should allow device twin path to be properties.tags

    it should be possible to create a device configuration with device twin properties containing certain tags

    1 vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Feature Request  ·  Flag idea as inappropriate…  ·  Admin →
  14. Digital Twin service creation flow needs to check for name collisions

    If you pick an obviously used name like "Twins", the service creation flow gives it a green check mark and lets you continue, but when you look at the status later you see deployment failed:

    {
    "code": "DeploymentFailed",
    "message": "At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-debug for usage details.",
    "details": [
    {
    "code": "BadRequest",
    "message": "{\r\n \"code\": \"BadRequest\",\r\n \"message\": \"Service 'Twins' is already in use. Please choose a different name.\",\r\n \"details\": {\r\n \"code\": 400\r\n }\r\n}"
    }
    ]
    }

    This should be verified during creation, just like all other services.

    1 vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Bug  ·  Flag idea as inappropriate…  ·  Admin →
  15. Add support for direct export to Time Series Insights

    Please add support for providing parameters for a Time Series Insights instance to which the Digital Twin resource can export all of its historical device data.

    8 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Feature Request  ·  Flag idea as inappropriate…  ·  Admin →
  16. How do you deal with conflictig permissions in Role defintions?

    How do you deal with conflictig permissions in Role defintions?

    Is it a union of all permissions or intersection?

    2 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  17. Role assignment API - how do I obtain object ID for a service principal/user? Is there some API which retrieves object Id given upn or name?

    Role assignment API - how do I obtain object ID for a service principal/user? Is there some API which retrieves object Id given upn or name?

    2 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  18. Add paging support

    Since a max node limit now exists on API GET calls, it would be helpful to have support for the ODATA $count feature.

    9 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Feature Request  ·  Flag idea as inappropriate…  ·  Admin →
  19. PUT /management/api/v1.0/endpoints/{id}

    Hello,

    I am trying to replace an already existing endpoint to make it point to a different Events Hub instance. Checking the swagger documentation for my Digital Twins, I saw the PUT /endpoints/{id} which should do just that.
    But, I am currently getting a surprising error:
    {
    "error": {
    "code": "400.600.000.000",
    "message": "An eventhub endpoint with DeviceMessage eventType has already been created. Only one endpoint of this combination can be created."
    }
    }

    This is a similar body to the one that I am using:
    {
    "type": "EventHub",
    "eventTypes": [
    "DeviceMessage"
    ],
    "connectionString": "Endpoint=sb://my-namespace.servicebus.windows.net/;SharedAccessKeyName=full-permissions;SharedAccessKey=someKey;EntityPath=my-entity",
    "secondaryConnectionString": "Endpoint=sb://my-namespace.servicebus.windows.net/;SharedAccessKeyName=full-permissions;SharedAccessKey=someKey;EntityPath=my-instance",
    "path": "my-instance"
    }

    Is…

    2 votes
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Bug  ·  Flag idea as inappropriate…  ·  Admin →
  20. Will Digital Twins support MSAL tokens?

    Will Digital Twins support MSAL tokens? (i.e. Azure AD 2.0)

    1 vote
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1
  • Don't see your idea?

Azure Digital Twins

Categories

Feedback and Knowledge Base