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. Dynamic registration_id

    When using DPS with EST certs and boot strapping, you could remove all custom configuration by allowing registration_id to dynamically set to mac address or some other system value. This would allow you to create an image that would register with dps and iot hub with no custom scripting.

    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  ·  Installing IoT Edge runtime  ·  Flag idea as inappropriate…  ·  Admin →
  2. Support for RHEL8 for OT devices

    We have a large (thousands) amount of RHEL 8 units and we want to use IoT edge. Toady there is no official support for RHEL8 and we cannot swap out the OS on our devices fast enough and we would need to start using IoT Edge this year.

    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  ·  Installing IoT Edge runtime  ·  Flag idea as inappropriate…  ·  Admin →
  3. Add SUSE Enterprise Linux (SLES) to at least Tier-2 list

    My company has standardized on SLES as the default Linux OS of choice. We would like to use Azure IoT Edge on at least Tier 2 level. What would it take for SLES to be listed as Tier 2 "supported"?

    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  ·  Installing IoT Edge runtime  ·  Flag idea as inappropriate…  ·  Admin →
  4. Remove the dependency on Powershell for deployment

    While the industry has become more accepting of Powershell, there will always be organizations that block its usage. In such environments, there would currently be no way for an organization to deploy the runtime without creating their own installer package. Microsoft should be the one making the redistributable package (.msi or similar) that is compatible with existing deployment methods that don't require powershell.

    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  ·  Installing IoT Edge runtime  ·  Flag idea as inappropriate…  ·  Admin →
  5. Provide placeholders for modifying config.yaml in Linux IoTEdge CLI

    In Windows IoTEdge installation, we can provide values for placeholders in config.yaml file while initializing iotedge. For example:

    . {Invoke-WebRequest -useb https://aka.ms/iotedge-win} | Invoke-Expression; ` Initialize-IoTEdge -Dps -ScopeId {scope ID} -RegistrationId {registration ID}

    In case of Linux, there is no way to do this. If we automated IoTEdge installation using a script, we have to manually search and replace the corresponding lines in config.yaml. It would be better to have CLI level arguments to modify the config.yaml.

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

    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

    2 comments  ·  Installing IoT Edge runtime  ·  Flag idea as inappropriate…  ·  Admin →
  7. Raspberry Pi Zero W / ARMv6 support

    Please add support for Raspberry Pi Zero W / ARMv6

    6 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  ·  Installing IoT Edge runtime  ·  Flag idea as inappropriate…  ·  Admin →
  8. Add Raspbian Buster as a Tier 1 OS

    Add Raspbian Buster as a Tier 1 OS

    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

    2 comments  ·  Installing IoT Edge runtime  ·  Flag idea as inappropriate…  ·  Admin →
  9. IoT Edge for Azure Sphere

    I know currently MediaTek Azure Sphere chips aren't very powerfull. But, it looks like the NXP Azure Sphere chips will have more compute power. It would be pretty sweet to be able to combine the enhanced security features of the Azure Sphere platform with building Azure IoT Edge devices and gateways.

    Are there any plans to support running the Azure IoT Edge runtime on Azure Sphere devices?

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

    Running IoT Edge on an Azure Sphere device would be interesting; however it’s not planned at the moment. I’m not sure how powerful the NXP chips are; however you are correct that we would need a more powerful Azure Sphere chip than are available today. Additionally there may be some other issues we need to address in terms of authenticating with the Azure Sphere Security Service.

    The first step for integration with Azure Sphere will be allowing them to gracefully connect to an Azure IoT Edge device.

  10. change default communication ports used for amqp https

    We have a shared endpoint NGNIX where all device communication is ending on our network. Based on protocol and ports we configure forwarding rule towards the iot hub.

    Is this supported to configure https mqtt to custom port rangens instead of the following
    https://docs.microsoft.com/en-us/azure/iot-hub/iot-hub-devguide-protocols

    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  ·  Installing IoT Edge runtime  ·  Flag idea as inappropriate…  ·  Admin →
  11. Allow installation of IOT Edge (runtime) on Windows to a different directory and drive location.

    In an enterprise environment we are often restricted to where we are allowed to install software. For example all installed software should be on the D drive in Programs directory.

    This is currently not possible with the iot edge runtime without modifying the IOT Edge standard installation scripts.

    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

    unplanned  ·  1 comment  ·  Installing IoT Edge runtime  ·  Flag idea as inappropriate…  ·  Admin →
  12. Installing IoT Edge Runtime on Core OS.

    CoreOS is one of the popular container OS in the market.It will be great idea to install Azure IoT Edge Runtime(EdgeAgenet,EdgeHub,iotedged bootstrap security daemon) on Core OS.

    As per https://docs.microsoft.com/en-us/azure/iot-edge/support#operating-systems CoreOS is neither in Tier-1 nor tier-2 OS list for IOT EDGE RUNTIME.

    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  ·  Installing IoT Edge runtime  ·  Flag idea as inappropriate…  ·  Admin →
  13. Need better parent child relationship with IoT Edge

    • The Parent/Child relationship between edge and leaf devices is too restrictive for our application. We have customers that are load balanced across and within physical locations, and our devices need to roam both with and without internet connectivity. If the child device concept could be extended to contain entire deployment groups based on a certificate chain, that would be preferred. Then each of our customers could have their own intermediate certificate with each of their devices as a leaf; and that intermediate certificate could be tied to each of their Edge appliances

    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

    4 comments  ·  Installing IoT Edge runtime  ·  Flag idea as inappropriate…  ·  Admin →
  14. Support powerpc architecture

    Does Azure Iot Edge Support powerpc architecture ?
    If not, do you plan to support it ?

    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  ·  Installing IoT Edge runtime  ·  Flag idea as inappropriate…  ·  Admin →
  15. (Cloud-triggered) IoT Edge Runtime Updates

    Provide a way of an (automatic) cloud-triggered update mechanism for the IoT Edge Runtime through IoT Hubs Device Management. Providing update capabilities not only for the containers but for the runtime and even the underlying OS is crucial for IoT Scenarios.

    26 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  ·  Installing IoT Edge runtime  ·  Flag idea as inappropriate…  ·  Admin →
  16. Provision of IoT Edge Security Damon package for Tire 2 system

    For the Tier 1 system, the latest IoT Edge Security Damon package is provided in the package repository (https://packages.microsoft.com/)
    But for the Tire 2 system, it is not provided.
    For example, for Ubuntsu 18.04 of Tire 1, iotedge1.0.4-1amd64.deb is provided, Regarding Debian 9, it still iotedge1.0.0-1amd64.deb yet.
    Our products use Debian 9, and we are asked to provide packages that fix bugs from customers.
    We will to build it localy and provide it at our own repository, What do you think?

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

    56 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

    6 comments  ·  Installing IoT Edge runtime  ·  Flag idea as inappropriate…  ·  Admin →
  18. Any plans to support Yocto on ARM32?

    This post: https://docs.microsoft.com/en-us/azure/iot-edge/support indicates that Yocto on ARM32 is not supported. Will it be? And, if so, will the ARM Python SDK for IoT Edge (suggested here: https://feedback.azure.com/forums/907045-azure-iot-edge/suggestions/34976278-arm-python-sdk-for-azure-iot-edge) work on Yocto?

    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

    1 comment  ·  Installing IoT Edge runtime  ·  Flag idea as inappropriate…  ·  Admin →

    We have published preview layers for IoT Edge on Yocto – https://github.com/azure/meta-iotedge. There is still work to be done before this becomes a Tier 1 OS; however you can start playing with it and providing feedback now.

    As far as Python support, you should probably be able to build a Yocto image that supports Python. You’ll have to include the layers required by the Python SDK. This SDK is going through a rewrite at the moment; however you can see a preview at – https://github.com/Azure/azure-iot-sdk-python-preview

  19. Support for aarch64 based platforms

    It would be great if support could be extended for deploying the run time on aarch64 based platforms, a lot of industrial platforms being launched on the market are based on Cortex-A53.

    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

    4 comments  ·  Installing IoT Edge runtime  ·  Flag idea as inappropriate…  ·  Admin →
  20. Environment variable $IOTEDGE_CONF needed instead of hard-coded path in scripts and executables

    With respect to your declared environment variables (given in "./edgelet/iotedged/src/lib.rs", and "./edgelet/iotedge/src/main.rs"), they cover almost every aspect, except, an environment variable, which could replace the hard-coded path "-c /etc/iotedge/config.yaml" to something like "-c $IOTEDGE_CONF". The variable could either be set in scripts, or the iotedged service/daemon/manager, itself, with a default path, if its value is not already given by an argument or defined in an environment variable.

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

    Hi Henrik, at this time we don’t plan on adding an environment variable to control this; however you may not be blocked.

    This is already configurable in the `iotedged` executable via the `-c` option. The `iotedge check` has a `-c` option as well for setting this file location, because it reads the config file. (none of the other iotedge subcommands read the config file).

    The only scripts related to this are in the packages and installer. However, the installer places this file in a very specific place and the executable needs to have a matching location. We actually don’t use the default anywhere. The linux packages directly specify the location: https://github.com/Azure/iotedge/blob/master/edgelet/contrib/systemd/iotedge.service#L8 And, the windows service directly specifies the location: https://github.com/Azure/iotedge/blob/master/edgelet/build/windows/iotedge.wm.xml#L60

← Previous 1
  • Don't see your idea?

Feedback and Knowledge Base