Update: Microsoft will be moving away from UserVoice sites on a product-by-product basis throughout the 2021 calendar year. We will leverage 1st party solutions for customer feedback. Learn more here.

Azure IoT Edge

Azure IoT Edge moves analytics and logic out of the cloud and onto your on-premises devices. Using a cloud interface, you can deploy either Azure service logic or your own code to devices without having to physically access them. And offline capabilities mean that you can extract business insights anywhere, without worrying about maintaining constant communication with a cloud service.

More details about the services are available in the documentation.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Increase "IoT Edge automatic deployments" limit

    According to the docs (https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-devguide-quotas-throttling) you can only have "100 deployments (including layered deployments) per paid SKU hub". I have a scenario in which this limit is limiting my usage of IoT Edge features.

    The scenario is that I'd like to have a deployment per customer. Since every of our customers only has <10 edge devices, this means that for every approx. 1000 devices (100 deployments, targeting 10 devices) I would need to purchase a new IoT Hub unit. This would make IoT Hub too expensive for my scenario.

    For now we are not using IoT Edge (layered)…

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Deploying modules  ·  Flag idea as inappropriate…  ·  Admin →
  2. Content trust

    Continuing discussion from https://github.com/Azure/iotedge/issues/1173:

    IoT Edge pulls unsigned modules down even when DOCKERCONTENTTRUST=1.

    IoT Edge should support and respect content trust for Docker images.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Deploying modules  ·  Flag idea as inappropriate…  ·  Admin →
  3. Content trust

    Continuing discussion from https://github.com/Azure/iotedge/issues/1173:

    IoT Edge pulls unsigned modules down even when DOCKERCONTENTTRUST=1.

    IoT Edge should support and respect content trust for Docker images.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Deploying modules  ·  Flag idea as inappropriate…  ·  Admin →
  4. Blob Storage on Edge module: upload throttling setting per container

    With the azure-blob-storage module it would be great if, as a desired.property, one could impose a (temporary or permanent) throttling in the upload speed of the Blobs. We deploy the modules in industrial settings where upload speed in distant regions is limited, and/or where blob uploads would compete with interactive traffice like SSH/VNC to remote-diagnose machines.

    A throttling setting (either "global" or per container) would help a lot, especially if it is a "desired.property" (i.e. a TWIN property that can be changed at run-time)

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Deploying modules  ·  Flag idea as inappropriate…  ·  Admin →
  5. Blob Storage on Edge module: allow configuring of log severity

    When looking into the azure-blob-storage logs we see a once-per second line of [2021-03-11 20:31:51.460] [info ] [tid 609] [BlobInterface.cc:1494] [ListBlobsInOrder] ListBlobsInOrder received. Container:telemetrycold BlobNameStart:null MaxBlobNames:1 OrderType:0 Flags:1

    It would be great if one would be able to configure the log severity, as this kind-of floods the log will irrelevant information.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Deploying modules  ·  Flag idea as inappropriate…  ·  Admin →
  6. Blob Storage on Edge module: allow SAS key per container

    We would like to use the the azure-blob-storage module as a central point for outgoing blob traffic for our deployed modules on IoT edge. Sadly it lacks the option to configure a per-container SAS key. Depending on which container gets written to, we want to upload the blobs to different target storage accounts. But also in the same storage account, depending on the container there might be a different key or SAS token required .

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Deploying modules  ·  Flag idea as inappropriate…  ·  Admin →
  7. Node Affinity and Tolerations Support for IoT Edge Modules in Kubernetes

    This request is related to the kubernetes version of IoT Edge. Please add node affinity configuration support in the deployment.json for module pods. NodeSelector is too restrictive. The use case is that we would like to keep single device modules on the single node if possible. This is related to the performance issues as our modules do a lot of heavy internal messaging between themselves and also use shared in-memory state. Also in the same time in the case of fail-over we would like to have the possibility to recreate the device on an alternative nodes which nodeSelector would not…

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Deploying modules  ·  Flag idea as inappropriate…  ·  Admin →
  8. Better for support for automated layer deployments

    Currently, the Azure DevOps "Azure IoT Edge" tasks only supports full deployments and not layered. There is a workaround that says to use the az cli but that doesn't support replacing the current layered release for an environment, so you need to increment the release name in the hub for it to work. This leads to loads of new releases when doing ci/cd and then need to be cleaned up.

    So could either the DevOps task be updated to support layered deployment because it does an in-place update of an Edge deployment in the hub or could the edge cli…

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Deploying modules  ·  Flag idea as inappropriate…  ·  Admin →
  9. deploy group of IoT modules independently like an Helm Chart

    One of the good things about helm in k8s is that modules can be charts can be deployed independently within the same namespace. It would be nice to be able to group IoT edge modules and deploy them independently like a chart within the device. This will allow to have a community driven configured "charts" deployed in IoT Edge, then can communicate with each other thru IoT Edge Hub. If you think this is a good idea, vote so it can be prioritized.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Deploying modules  ·  Flag idea as inappropriate…  ·  Admin →
  10. Display failure count + time until planned restart for modules in backoff state

    Right now 'iotedge list' as well as the Portal show a module in 'backoff' state without giving any indication of when the module will be restarted, or how many times in a row the module has failed. It would be very helpful for troubleshooting purposes if that capability could be added.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Deploying modules  ·  Flag idea as inappropriate…  ·  Admin →
  11. Optional signature for the deployment manifest

    Optional signature for the deployment manifest, so that the IoTEdge can verify the integrity of the manifest independent of transport/cloud integrity.

    The overall objective should be to at least enable users of the Azure IoT edge solution to secure/harden the system in a way that even a cloud breach couldn't lead to a corruption of the local systems or an information leak. At the moment the system depends solely on the cloud integrity - but a second security barrier should be available.

    For sure there are multiple starting points - e.g. signing container images; generally disable upstream-messaging. But the biggest…

    10 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  0 comments  ·  Deploying modules  ·  Flag idea as inappropriate…  ·  Admin →
  12. Progress bar for deployment of modules

    For development, testing and monitoring purposes it would be great if there would be more information about the progress of a deployment, especially on the Edge device itself. One can look at the logfiles for the start and finish of a deployment, but I would like to know more than this. My suggestion would be to see the container in the 'iotedge list' with status downloading (42MB/100MB, 42%), but I'm open to any other form of monitoring the progress of the deployment.

    25 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Deploying modules  ·  Flag idea as inappropriate…  ·  Admin →
  13. sign container

    Provide option during the install (only local on edge device) that forces all containers to be signed by a specific certificate.

    This would allow to harden the device against a leak of the IoT Hub Management Credentials or of the Customer Platform managing the deployments.

    14 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Deploying modules  ·  Flag idea as inappropriate…  ·  Admin →
  14. Removing unused modules from IoT Edge devices

    I am successfully able to add and remove custom modules from a deployment. However, I notice that modules that I remove through a deployment, remain on the device, occupying space. So at some point, the device's storage will get filled up with junk (outdated or unnecessary modules), leading to a system crash.

    This is the response I received from Microsoft - "Thanks for your feedback @baharw . That is by design - you can easily integrate a direct method for example that would be responsible to remove all unused docker images on your edge device. I nevertheless suggest that you…

    101 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  8 comments  ·  Deploying modules  ·  Flag idea as inappropriate…  ·  Admin →
  15. Wildcard support in routes' source

    Enable wildcard for modules in iot edge hub routes so all modules having the same output are routed to the same module. Useful for example when integrating a local database with multiple modules sending data to.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Deploying modules  ·  Flag idea as inappropriate…  ·  Admin →
  16. Allow for placeholder variables in IoT Edge deployment templates

    I am looking to have a configured deployment for Azure IoT Edge that automatically gets applied, based on the configured tags for a new IoT Edge device.
    That works perfectly (modules are being set, routes are defined, module twins are configured)

    However, I’d like to leverage a concept like ‘placeholder values’ that I can override on edge device level.

    For example: I might have 5 different devices, all using the same deployment, but inside one of their module, I need to set a specific Environment Variable, or update a value in their desired properties (of the module twin). Once creating…

    9 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Deploying modules  ·  Flag idea as inappropriate…  ·  Admin →
  17. Delta Updates for Modules for low-bandwith scenarios

    Provide a (binary) delta update process for module/container updates. As of now Azure IoT Edge is not suitable for low-bandwith / bad connectivity (eg. cellular) scenarios as the module/container download always pulls the whole image with potentially hundreds of MBs.

    7 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    under review  ·  2 comments  ·  Deploying modules  ·  Flag idea as inappropriate…  ·  Admin →
  18. Issue iotedge commands from Azure

    It would be great to issue iotedge commands from Azure on specific devices. Especially the "iotedge logs" command to see what is happening on a device remotely.

    7 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Deploying modules  ·  Flag idea as inappropriate…  ·  Admin →
  19. Allow upstream IoT Hub (Event Hub) to be different as management one

    It would be nice to have possibility to set upstream IoT Hub (or even Event Hub) to be different as management IoT Hub. Scenario is, that Dev Company is taking care of development and operation of IoT Edge device, but collected data should flow to their customer subscription for further processing. Sure it is possible to connect to different IoT Hub from module and send data that way, but this bypasses routes feature provided by IoT Edge.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Deploying modules  ·  Flag idea as inappropriate…  ·  Admin →
  20. IoT Edge Module deployment limit

    Currently there is a limit of 10 modules (includes agent, hub) to be deployed to IoT Edge device. What is the plan for module deployment limit for GA release? The reason is the solution we are working demands multiple (more than 8) peripheral integration at device level and we see that each Edge module could represent the peripherals. Also, please share tentative plan of GArelease?

    24 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

Feedback and Knowledge Base