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. 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 →
  2. 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 →
  3. 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 →
  4. 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 →
  5. 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 →
  6. 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 →
  7. 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 →
  8. 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…

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

    We’ll send you updates on this idea

    under review  ·  0 comments  ·  Deploying modules  ·  Flag idea as inappropriate…  ·  Admin →
  9. 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 →
  10. 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 →
  11. 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

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

    We’ll send you updates on this idea

    5 comments  ·  Connectivity issues  ·  Flag idea as inappropriate…  ·  Admin →
  12. 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 →
  13. 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 →
  14. 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 →
  15. 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 →
  16. 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 →
  17. 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 →
  18. Support hierarchical module input structure

    Currently the input channel is determined by a single name. But from my point of view it could be interesting to support a hierarchy of inputs in a module (e.g. something like /modules/{{mid}}/inputs/{{input}}/{{subchannel}} would be possible) - this would be interesting in scenarios where the module just registers a generic handler for messages and uses the information contained in the hierarchy of the input channel (e.g. for routing purposes) - for sure something similar could be achieved by just using/interpreting a different 'split char', but it would be nice if a simple '/' could be used. Also this wouldn't allow…

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

    We’ll send you updates on this idea

    under review  ·  3 comments  ·  Developing custom modules  ·  Flag idea as inappropriate…  ·  Admin →
  19. 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 →
  20. 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.

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

    We’ll send you updates on this idea

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

Feedback and Knowledge Base