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. Edge devices connected to the same local network to communicate with each other directly.

    I wish to use Azure IoT Edge to deploy our modules to a fleet of robots. It would be awesome if edge modules could send messages to modules of other devices within the same local network.

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

    We’ll send you updates on this idea

    0 comments  ·  Connectivity issues  ·  Flag idea as inappropriate…  ·  Admin →
  2. 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
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Connectivity issues  ·  Flag idea as inappropriate…  ·  Admin →
  3. Support configuring twin in offline scenarios

    At the moment configuring a twin is not possible in an offline scenario. We use the twin extensively for some of our modules and it would be quite inconvenient to have to implement a different communication channel to support offline scenarios.

    Implementing this would also mean the SDK would need to be extended so a module can change anothers twin properties. I think this would be a very welcome addition to the Azure IoT Edge platform.

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

    We’ll send you updates on this idea

    1 comment  ·  Developing custom modules  ·  Flag idea as inappropriate…  ·  Admin →
  4. Messages delivered to IoT Edge device instead of Leaf device to IoT hub

    I have setup Azure IoT Edge in Transparent Proxy pattern. Created a leaf device. When Messages from leaf devices are sent upstream

    "leafdeviceToUpstream":"FROM /messages/* WHERE NOT IS_DEFINED($connectionModuleId) INTO $upstream"")"

    Messages are correctly delivered to leaf device in IoT Hub.

    Now I created a custom module. Messages from leaf device are piped to custom module and from custom module (after processing) are sent upstream.
    Here, I was expecting that messages are delivered to leaf device. However, instead they are delivered to IoT Edge device. Looks like since the custom module creates new message, source of origin changes from leafdevice ID to…

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

    We’ll send you updates on this idea

    0 comments  ·  Developing custom modules  ·  Flag idea as inappropriate…  ·  Admin →
  5. snap

    In our IoT platform, we have chosen Ubuntu Core as our OS for our platforms. We would love to run IoT Edge on our platform (as we run other cloud edge services). But IoT Edge is not supported in Ubuntu Core - more specifically its not supported as a snap.

    Please consider supporting IoT Edge as a snap. Ubuntu Core is increasingly becoming an OS of choice for IoT platforms.

    Thanks,

    Giri

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

    We’ll send you updates on this idea

    0 comments  ·  Installing IoT Edge runtime  ·  Flag idea as inappropriate…  ·  Admin →
  6. IoT Edge Deployment stats goes from success to applied and get stuck on applied

    A couple of time after deploying a new manifest we experience that the deployment stats in Azure IoT-Hub first shows x reporting success. Then after a period of time it says 0 reporting success even though nothing else has happened. The "applied" state will persist until something changes in our manifest or we restart something.

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

    We’ll send you updates on this idea

    0 comments  ·  Deploying modules  ·  Flag idea as inappropriate…  ·  Admin →
  7. IoT Edge Deployment stats goes from success to applied and get stuck on applied

    A couple of time after deploying a new manifest we experience that the deployment stats in Azure IoT-Hub first shows x reporting success. Then after a period of time it says 0 reporting success even though nothing else has happened. The "applied" state will persist until something changes in our manifest or we restart something.

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

    We’ll send you updates on this idea

    0 comments  ·  Deploying modules  ·  Flag idea as inappropriate…  ·  Admin →
  8. IoT Edge Deployment stats goes from success to applied and get stuck on applied

    A couple of time after deploying a new manifest we experience that the deployment stats in Azure IoT-Hub first shows x reporting success. Then after a period of time it says 0 reporting success even though nothing else has happened. The "applied" state will persist until something changes in our manifest or we restart something.

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

    We’ll send you updates on this idea

    0 comments  ·  Deploying modules  ·  Flag idea as inappropriate…  ·  Admin →
  9. IoT Edge Deployment stats goes from success to applied and get stuck on applied

    A couple of time after deploying a new manifest we experience that the deployment stats in Azure IoT-Hub first shows x reporting success. Then after a period of time it says 0 reporting success even though nothing else has happened. The "applied" state will persist until something changes in our manifest or we restart something.

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

    We’ll send you updates on this idea

    0 comments  ·  Deploying modules  ·  Flag idea as inappropriate…  ·  Admin →
  10. Support Device Streams in IoT Edge

    Natively support Azure Device Streams in IoT Edge, preferably by entering Device Streams endpoint in IoT Edge's config.yaml file.

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

    We’ll send you updates on this idea

    0 comments  ·  Deploying Azure services  ·  Flag idea as inappropriate…  ·  Admin →
  11. Azure Blob Storage on IoT Edge: cloudToDeviceDownload

    We see lots of needs where customers use a connected Edge device as data gateway for leaf devices.
    ABSonIoTEdge module allowed us to implement upload scenarios so far, is possible to get it working the other way around too?

    For example, I'd have the need to deliver regularly to thousands of leaf devices that cannot connect to the internet the same file (e.g. a few MB firmware) through a couple of Edge devices.
    azcopy sync and a local file share works, but it would be so much better if we could have the IoT related data in the same place.

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

    We’ll send you updates on this idea

    0 comments  ·  Developing custom modules  ·  Flag idea as inappropriate…  ·  Admin →
  12. Force reprovisioning of the IoT EDGE Daemon locally

    Provide some kind of configuration of the IoT Edge runtime where I can select the provisioning scenario which works for me. That means, forced reprovisioning is facilitated by the IoT Edge Runtime.

    This way, eg. an IoT Edge on the move can start reprovisioning on its own to find the nearest IoT Hub without interrupting local compute (data ingest, transformations, executing ML, Executing actions).

    Rebooting an IoT Edge just to force reprovisioning is not an option. The logic on the device has to run 24/7. Lack of internet connectivity (either no internet connection of during reprovisioning to a new IoTHub)…

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

    We’ll send you updates on this idea

    1 comment  ·  Installing IoT Edge runtime  ·  Flag idea as inappropriate…  ·  Admin →
  13. Raspberry Pi Zero W / ARMv6 support

    Please add support for Raspberry Pi Zero W / ARMv6

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

    We’ll send you updates on this idea

    0 comments  ·  Installing IoT Edge runtime  ·  Flag idea as inappropriate…  ·  Admin →
  14. 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 )

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

    We’ll send you updates on this idea

    0 comments  ·  Connectivity issues  ·  Flag idea as inappropriate…  ·  Admin →
  15. How to deploy module by IoT Hub service SDK, like IoT Hub service node SDK.

    I want to deploy the module to my iot edge device via iot hub service SDK. But I find only 3 ways to deploy module:
    Azure portal
    Azure CLI
    VS Code

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

    We’ll send you updates on this idea

    0 comments  ·  Developing custom modules  ·  Flag idea as inappropriate…  ·  Admin →
  16. 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
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Deploying modules  ·  Flag idea as inappropriate…  ·  Admin →
  17. 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
    Sign in
    (thinking…)
    Sign in with: Microsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Connectivity issues  ·  Flag idea as inappropriate…  ·  Admin →
  18. Support for .NET Core 3.0 and .NET core 3.1

    IoT edge supports .NET core 2.0 only. But latest vesions are 3.0 and 3.1. And moreover 2.0 isn't even LTS release.
    Or does it support all versions greater than 2.0?

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

    We’ll send you updates on this idea

    0 comments  ·  Developing custom modules  ·  Flag idea as inappropriate…  ·  Admin →
  19. Store Private key for X.509 based DPS securely on HSM

    Use the X.509-based enrollment in DPS in IoTEdge without storing the private key on file system.

    The idea is to store the Private Key in a HSM and let it never leave.

    At this moment, the x.509 provisioning mode only supports a private key on the file system...

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

    We’ll send you updates on this idea

    started  ·  1 comment  ·  Developing custom modules  ·  Flag idea as inappropriate…  ·  Admin →
  20. Add Raspbian Buster as a Tier 1 OS

    Add Raspbian Buster as a Tier 1 OS

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

    We’ll send you updates on this idea

    1 comment  ·  Installing IoT Edge runtime  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3 4
  • Don't see your idea?

Feedback and Knowledge Base