{"id":825,"date":"2019-12-17T00:00:00","date_gmt":"2019-12-17T00:00:00","guid":{"rendered":"https:\/\/azure.microsoft.com\/blog\/new-enhancements-for-azure-iot-edge-automatic-deployments"},"modified":"2025-06-29T10:36:36","modified_gmt":"2025-06-29T17:36:36","slug":"new-enhancements-for-azure-iot-edge-automatic-deployments","status":"publish","type":"post","link":"https:\/\/azure.microsoft.com\/en-us\/blog\/new-enhancements-for-azure-iot-edge-automatic-deployments\/","title":{"rendered":"New enhancements for Azure IoT Edge automatic deployments"},"content":{"rendered":"\n

Since releasing Microsoft Azure IoT Edge<\/a>, we have seen many customers using IoT Edge automatic deployments<\/a> to deploy workloads to the edge at scale. IoT Edge automatic deployments handle the heavy lifting of deploying modules to the relevant Azure IoT Edge devices and allow operators to keep a close eye on status to quickly address any problems. Customers love the benefits and have given us feedback on how to make automatic deployments even better through greater flexibility and seamless experiences. Today, we are sharing a set of enhancements to IoT Edge automatic deployments that are a direct result of this feedback. These enhancements include layered deployments, deploying marketplace modules from the Azure portal and other UI updates, and module support for automatic device configurations.<\/p>\n\n\n\n

Layered deployments<\/h2>\n\n\n\n

Layered deployments are a new type of IoT Edge automatic deployments that allow developers and operators to independently deploy subsets of modules. This avoids the need to create an automatic deployment for every combination of modules that may exist across your device fleet. Microsoft Azure IoT Hub evaluates all applicable layered deployments to determine the final set of modules for a given IoT Edge device. Layered deployments have the same basic components as any automatic deployment. They target devices based on tags in the device twins and provide the same functionality around labels, metrics, and status reporting. Layered deployments also have priorities assigned to them, but instead of using the priority to determine which deployment is applied to a device, the priority determines how multiple deployments are ranked on a device. For example, if two layered deployments have a module or a route with the same name, the layered deployment with the higher priority will be applied while the lower priority is overwritten.<\/p>\n\n\n\n

\"Modules<\/figure>\n\n\n\n

This first illustration shows how all modules need to be included in each regular deployment, requiring a separate deployment for each target group.<\/p>\n\n\n\n

\"Layered<\/figure>\n\n\n\n

This second illustration shows how layered deployments allow modules to be deployed independently to each target group, with a lower overall number of deployments.<\/p>\n\n\n\n

Revamped UI for IoT Edge automatic deployments<\/h2>\n\n\n\n

There are updates throughout the IoT Edge automatic deployments UI in the Azure portal. For example, you can now select modules from Microsoft Azure Marketplace<\/a> from directly within the create deployment experience. The Azure Marketplace features many Azure IoT Edge modules built by Microsoft and partners.<\/p>\n\n\n\n

\"A<\/figure>\n\n\n\n

Automatic configuration for module twins<\/h2>\n\n\n\n

Automatic device management<\/a> in Azure IoT Hub automates many of the repetitive and complex tasks of managing large device fleets by using automatic device configurations to update and report status on device twin properties. We have heard from many of you that you would like the equivalent functionality for configuring module twins, and are happy to share that this functionality is now available.<\/p>\n\n\n\n

Next steps<\/h2>\n\n\n\n