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.
-
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…
73 votes -
Support Ubuntu Core
Add Ubuntu Core as supported Operating Systems. It is becoming a preferred "secure by default" OS which is preinstalled on many IoT Gateways. E.g. Dell Edge Gateways
46 votesWe are aware of this OS and want to get to it; however CentOS 7.5 and Yocto are currently higher on our priority list.
-
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 votesThis is a gap that we are aware of, want to fix, and are currently discussing with the Azure Sphere team.
-
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.
29 votes -
Remote login to IoT Gateway
If an IoT Gateway is deployed in the industrial plant and if some application crashes in Gateway or some need of login to the gateway.
In that case, Azure IoT edge should allow users to remotely log in to the IoT gateway using ssh/telnet. This will very easy to monitor the status and debugging/maintenance.19 votes -
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.
18 votes -
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 -
More options, or configuration parameters, of storeAndForwardConfiguration
storeAndForwardConfiguration has a parameter, timeToLiveSecs to specify offline period to retain data.
Preferable to add following 3 parameters to storeAndForwardConfiguration
1. Limit the amount of disk usage to be used for SnF feature.
2. Specify the directory/path of storage for SnF feature
3. Flush un-forwarded messages in SnF memory out to specified files12 votes -
Add Raspbian Buster as a Tier 1 OS
Add Raspbian Buster as a Tier 1 OS
10 votesRaspbian Buster definitely works with IoT Edge; however CentOS, Debian, and Yocto currently have higher priority in terms of getting them into the test gates.
-
Add Feature to Check Upstream Connection Status (Expose to Modules)
Is there some connection state to IoT Hub from IoT Edge that can be made available to edge modules? We are trying to get the upstream connection status to IoT Hub from the edge module context (.NET).
We would like this status check to be available during first-time-configuration as well as outside of the first-time-configuration use case so that, if needed, we can leverage this for troubleshooting devices in the field.
9 votesWe will consider this for the next round of feature planning which will cover work done in the first half of 2021.
-
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…
9 votes -
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)…
8 votesWe’ve completed our feature planning for the second half of 2020. We’ll consider this when we do feature planning for the first half of 2021.
-
Container Encryption
Provide container encryption technologies (e.g. Vormetric from Thales) to Azure IoT Edge to make sure that partners protect their IP
8 votes -
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…
7 votes -
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…
7 votesWe see the value in the feature; however there is no easy way to do this at the moment.
-
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.
4 votesWe’ve completed our feature planning for the second half of 2020. We’ll consider this when we do feature planning for the first half of 2021.
-
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)4 votesCurrently we encrypt the container registry credentials to disk on Edge devices. In the future we’d like to send them down to Edge devices already encrypted.
-
Enable Azure Media Services streaming an analytics through IoT Edge.
Live media streams requires usually a good bandwith. By running the Azure Media Services, through the IoT Edge, it should be possible to employ ML, and vision analytics on the edge before streaming to cloud.
4 votes -
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 )
3 votesWe’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.
-
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.
3 votes
- Don't see your idea?