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. 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…

    105 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 →
  2. Module for receiving data from BACnet systems

    Alike a Modbus module, it would be useful if a BACnet module is made available to support BACnet systems.

    15 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 →
  3. 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…

    11 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 →
  4. 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…

    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

    2 comments  ·  Deploying modules  ·  Flag idea as inappropriate…  ·  Admin →
  5. 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 →
  6. Safe Storage for Container Registry Credentials

    Using a Azure Container Registry which is not public leads to having the credentials to the registry on every deployed device.
    It would be nice to have the authentication handled by the IoT Hub or a solution to store the credentials inside the tpm (if it would be necessary to have them onto each device)

    5 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 →
  7. 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 →
  • Don't see your idea?

Feedback and Knowledge Base