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. Serial Port support in eflow

    In IoTEdge v1.2 on Windows devices (eflow), only Linux containers will be supported.

    This implicitly deprecates support for passing host serial ports into containers in Windows (since this is only supported in Windows host/Windows containers or Linux host/Linux containers configurations).

    The suggested workaround is to run com0com or hub4com on the Windows host to convert serial port communication to tcp communication. This is insufficiently scalable because it requires additional configuration on the host and doesn't easily accommodate common situations like comport discovery or the addition of usb serial dongles after installation and setup.
    WILL iotedge EVER support either (a) Windows…

    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  ·  Connectivity issues  ·  Flag idea as inappropriate…  ·  Admin →
  2. Device/Module connected and disconnected event messages to built-in events endpoint

    I've a service backend which monitors all the Edge devices registered at an IoT Hub. E.g. to be notified if a new device or module identity was created, a module twin has changed or to ingest D2C telemetry messages - for all those messages I'm using the built-in events endpoint which is actually an Event hub, according to the documentation.

    However, it would be very nice if in addition to the identity and twin change events also device connected and disconnected events are published at this endpoint via simple messages.
    This is very similar to: https://docs.microsoft.com/en-us/azure/event-grid/event-schema-iot-hub?tabs=event-grid-event-schema - but I don't…

    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  ·  Connectivity issues  ·  Flag idea as inappropriate…  ·  Admin →
  3. Settings for China Azure

    Metrics collector has a setting for connecting to azure like LogAnalyticsWorkspaceId and LogAnalyticsSharedKey

    The module is sending to https://{workspaceId}.ods.opinsights.azure.com/api/logs?api-version=

    .com, not .cn

    If you set up with workspace id from log analytics in azure china - no such host is known.

    Possibility to setttings in azure china is needed.

    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  ·  Connectivity issues  ·  Flag idea as inappropriate…  ·  Admin →
  4. Improve configuration of HTTP(s) proxy for deployments at customer sites

    Hello,

    we are having a bit of trouble with the way iotedge handles HTTP(s)-Proxy configuration.

    Current State

    Right now a HTTP(s) proxy for an iotedge needs to be configured


    • locally in /etc/iotedge/config.yml (and required linux daemons)

    • and in IoT Edge deployment (IoT Hub) via

      • edgeAgent environment variable https_proxy

      • edgeHub environment variable https_proxy



    Therefore each edge deployed at a customer site with a proxy needs a custom deployment in IoT Hub.

    Problem(s)

    This poses several problems


    • customer passwords need to be stored in IoT hub

      • which then need to be kept in sync with local proxy configuration

      • which we'd prefer not…
    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

    0 comments  ·  Connectivity issues  ·  Flag idea as inappropriate…  ·  Admin →
  5. edgehub status in built-in metrics

    Hi,
    It would be very convenient to have a status of the edgehub regarding the following steps during startup :


    • starting

    • ready

    • ... ("problem" or something ?)

    For our use case, we need to reboot frequently our edge device and our modules wait edgehub to be ready. For now, we are waiting these messages in logs :


    • "Started MQTT head"

    • "route: FROM /messages/* INTO $upstream"

    When we see those mesages, we know that edgehub is ready for receiving messages and can forward them to iothub. But parsing logs is not a good solution, it would be great to use built-in…

    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  ·  Connectivity issues  ·  Flag idea as inappropriate…  ·  Admin →
  6. Support or Document simple "Device Move" Scenarios

    We use Azure IoT-Edge with both the Transparent-Gateway pattern to new IoT-Devices and Identity-Translation-Gateway pattern to legacy devices. We need to find the best solution to "Move" a device between two IoT-Edge instances.

    The Device-Move could be frequent between the IoT-Edge instances, not just once, so the procedure cannot be too complicated/intrusive. Some of the Device-Twin data needs to be common across the "Moves" but this can be handled in the IoT-Hub directly (via an Azure Function, for example).

    What we are looking for here is ideas or suggestions for the best (supported) "Move" options.
    - Online-Move: move an IoT-Device…

    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

    1 comment  ·  Connectivity issues  ·  Flag idea as inappropriate…  ·  Admin →
  7. Remotely detect if devices/IoT Edge software are offline

    Recently the edgeAgent direct method "ping" was added to manually/programmatically perform checks.
    But I would like to see a similar approach that does these checks automatically, integrated with e.g. "IoT Edge Runtime Response" in the Azure Portal.

    There were a similar question at GitHub about this issue https://github.com/Azure/iotedge/issues/2341.

    As of now there is no built-in automatic report when devices/IoT Edge software are offline due to e.g. power outages/unexpected loss of internet connection.

    4 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  ·  Connectivity issues  ·  Flag idea as inappropriate…  ·  Admin →
  8. Hybrid downstream devices with opaque gateway

    I would like to connect my downstream device to the gateway, apply some filter, and send the data to the cloud on behalf of the originated device.

    As implemented today, if a message gets extracted by a module and then forwarded upstream, the system properties are attributed to the Edge device.

    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  ·  Connectivity issues  ·  Flag idea as inappropriate…  ·  Admin →
  9. Support storing the module identities within edgeAgent on the filesystem

    At the moment the module identities are stored within edgeAgent which get destroyed as soon as the edgeAgent container is removed. It would be great to have an option to store the identities on the filesystem (for example by bind mounting a folder in which they are stored in somehow).

    Doing this would make running IoT Edge in offline scenarios a lot easier. Given the following scenario:
    - An IoT Edge device is used offline
    - The firmware is being updated, measures are being taken to persist the docker images so the modules will be able to start after the…

    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  ·  Connectivity issues  ·  Flag idea as inappropriate…  ·  Admin →
  10. Remote Restart of the IoT EDGE Daemon for re-provisining services

    For DPS re-provision scenarios, such as moving the device to a new IoT hub or setting new configuration of the device, the daemon needs to restarted in order to use the config.yaml file to communicate with DPS, so the configuration can be updated.

    it would be useful to be able to restart the daemon remotely ( via a direct method of the edge agent as an example )

    4 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  ·  Connectivity issues  ·  Flag idea as inappropriate…  ·  Admin →

    We’ll likely add this capability as we expand our device management and update capabilities. In the meantime, you can write a custom module that exposes this method and calls the correct system methods for the OS used by your devices.

  11. Add sha256 support for authenticating downstream devices with self signed certificates

    I set up an edge device, added a child device to it and modified the child device's connection string to point to the edge device. The device is using self signed certs. If I add the device to the hub using the sha256 thumbprint, the edge cannot authenticate the device. If I add the device using the sha1 thumbprint, it works. I followed the instructions here, which says to use sha1: https://docs.microsoft.com/en-us/azure/iot-edge/how-to-authenticate-downstream-device

    But, when I use a Device Provisioning Service to add the device to the hub, it uses the sha256 thumbprint, so my device won't connect to the 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  ·  Connectivity issues  ·  Flag idea as inappropriate…  ·  Admin →
  12. Using Bluetooth to communicate with mobile app

    I can't find any C# tutorial which uses the built-in Bluetooth chip on the Raspberry Pi 3 (everyone seems to be using SensorTags) to chat with mobile app. I have been able to connect to mobile phone and receive messages on my Edge module in Python, but I can't find any reliable and full tutorial to do it in C#

    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

    1 comment  ·  Connectivity issues  ·  Flag idea as inappropriate…  ·  Admin →
  13. when processing queued messages after reconnecting, send messages with LIFO instead of FIFO as the latest data is the most important for rea

    when processing queued messages after reconnecting, send messages with LIFO instead of FIFO as the latest data is the most important for real time monitoring. This is similar to the one posted already

    40 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  ·  Connectivity issues  ·  Flag idea as inappropriate…  ·  Admin →
  14. Certificate based Proxy Authentication

    Can you please provide support for certificate based proxy authentication on IoT Edge. The certificate are client signed certificates used to securely authenticate within the client network.

    19 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  ·  Connectivity issues  ·  Flag idea as inappropriate…  ·  Admin →
  15. Low bandwidth / partially connected: message delivery priority

    For scenarios with low bandwidth and connectivity issues sending messages in the FIFO order of the message cache after being offline is not working. We need a way to specify "important" messages (delivery priority) that needs to be sent before trying to send all other messages from the msg cache. Specifying different TTL values for different priorities would be necessary as well.

    8 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

    started  ·  2 comments  ·  Connectivity issues  ·  Flag idea as inappropriate…  ·  Admin →
  16. Local Edge N+M high availability and scalability (no cloud connection required after setup)

    1) Deploy Edges as local clusters such that they can suffer failure and there is a high availability strategy that doesn't require a cloud connection.

    2) Edge scalability to horizontally add nodes to the Local Edge Cluster. Maybe it kind of behaves like Docker Swarm. i.e. Say I have a pretty intense preprocessor for data prep before handing it to ML Inference. That could get scaled out across multiple nodes in a Local Edge Cluster.

    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  ·  Connectivity issues  ·  Flag idea as inappropriate…  ·  Admin →
  17. Document how to connect Azure Sphere Device as Downstream Device to Edge

    It would be great to connect the new Azure Sphere to the IoT Hub on Edge to use Sphere in a Transparent Gateway Scenario

    31 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

    10 comments  ·  Connectivity issues  ·  Flag idea as inappropriate…  ·  Admin →
  18. Hierarchy possibilities for edge devices.

    The purpose is to have for example 5 incoming sensors in the 'sensor' edge device where we can do some calculations on the edge. The output goes to another edge device, where again we can do some calculations on the edge with input from other similar 'sensor' edge devices. The last edge device in the chain will send the data to the IoT Hub.

    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

    2 comments  ·  Connectivity issues  ·  Flag idea as inappropriate…  ·  Admin →
  19. C2D Messaging

    I know direct methods are possible but sometimes you just want to have a queue of C2D messages which are delivered to devices when they come online. Direct methods only work when a device is connected and it would require some effort to implement the aforementioned scenario. Also one would need some routing logic to deliver those messages to modules.

    36 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  ·  4 comments  ·  Connectivity issues  ·  Flag idea as inappropriate…  ·  Admin →
  20. Need a way to distribute communication at edge devices when offline with IoT hub

    During offline with IoT hub, is it possible to have a mechanism at Edge device to distribute the messages among other Edge devices? This will help to address a scenario were one Edge device needs to share message/information with another Edge device as there is no cloud data storage share available due to
    connectivity issue.

    12 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

    need-feedback  ·  5 comments  ·  Connectivity issues  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base