Merge pull request #299960 from DENKEN02MSFT/Top50_patricka_Row47

Top50 - row 47

Author: denrea

articles/iot-edge/how-to-deploy-at-scale.md

@@ -3,7 +3,7 @@ title: Deploy modules at scale in Azure portal - Azure IoT Edge
 description: Use the Azure portal to create automatic deployments for groups of IoT Edge devices
 author: PatAltimore
 ms.author: patricka
-ms.date: 06/12/2024
+ms.date: 05/15/2025
 ms.topic: concept-article
 ms.service: azure-iot-edge
 services: iot-edge
@@ -37,20 +37,20 @@ For more information about device twins and tags, see [Understand and use device
 
 ## Create a deployment
 
-IoT Edge provides two different types of automatic deployments that you can use to customize your scenario. You can create a standard *deployment*, which includes that system runtime modules and any additional modules and routes. Each device can only apply one deployment. Or you can create a *layered deployment*, which only includes custom modules and routes, not the system runtime. Many layered deployments can be combined on a device, on top of a standard deployment. For more information about how the two types of automatic deployments work together, see [Understand IoT Edge automatic deployments for single devices or at scale](module-deployment-monitoring.md).
+IoT Edge provides two different types of automatic deployments that you can use to customize your scenario. You can create a standard *deployment*, which includes that system runtime modules and any other modules and routes. Each device can only apply one deployment. Or you can create a *layered deployment*, which only includes custom modules and routes, not the system runtime. Many layered deployments can be combined on a device, on top of a standard deployment. For more information about how the two types of automatic deployments work together, see [Understand IoT Edge automatic deployments for single devices or at scale](module-deployment-monitoring.md).
 
 The steps for creating a deployment and a layered deployment are similar. Any differences are called out in the following steps.
 
-1. In the [Azure portal](https://portal.azure.com), go to your IoT Hub.
-1. On the menu in the left pane, select **Configurations + Deployments** under **Device Management**.
-1. On the upper bar, select **Add** > **Add Deployment** or **Add Layered Deployment**.
+1. In the [Azure portal](https://portal.azure.com), go to your IoT hub.
+1. On the resource menu in the left pane, select **Configurations + Deployments** under **Device Management**.
+1. On the command bar, select **Add** > **Deployment** or **Layered Deployment**.
 
 There are five steps to create a deployment. The following sections walk through each one.
 
 >[!NOTE]
 >The steps in this article reflect the latest schema version of the IoT Edge agent and hub.
 >
->If you are deploying to a device running version 1.0.9 or earlier, edit the **Runtime Settings** in the **Modules** step of the wizard to use schema version 1.0.
+>If you're deploying to a device running version 1.0.9 or earlier, edit the **Runtime Settings** in the **Modules** step of the wizard to use schema version 1.0.
 
 ### Step 1: Name and label
 
@@ -62,22 +62,22 @@ There are five steps to create a deployment. The following sections walk through
 
 You can add up to 50 modules to a deployment. If you create a deployment with no modules, it removes any current modules from the target devices.
 
-In deployments, you can manage the settings for the IoT Edge agent and IoT Edge hub modules. Select **Runtime Settings** to configure the two runtime modules. In layered deployment, the runtime modules are not included so cannot be configured.
+In deployments, you can manage the settings for the IoT Edge agent and IoT Edge hub modules. Select **Runtime Settings** to configure the two runtime modules. In layered deployment, the runtime modules aren't included so can't be configured.
 
 To add custom code as a module, or to manually add an Azure service module, follow these steps:
 
-1. In the **Container Registry Settings** section of the page, provide the credentials to access any private container registries that contain your module images.
+1. In the **Container Registry Credentials** section of the page, provide the credentials to access any private container registries that contain your module images.
 1. In the **IoT Edge Modules** section of the page, select **Add**.
 1. Choose one of the types of modules from the drop-down menu:
 
-   * **IoT Edge Module** - You provide the module name and container image URI. For example, the image URI for the sample SimulatedTemperatureSensor module is `mcr.microsoft.com/azureiotedge-simulated-temperature-sensor:1.0`. For a list of Microsoft IoT Edge module images, see the [Microsoft Artifact Registry](https://mcr.microsoft.com/catalog?cat=IoT%20Edge%20Modules&alphaSort=asc&alphaSortKey=Name).
+   * **IoT Edge Module** - You provide the module name and container image URI. For example, the image URI for the sample SimulatedTemperatureSensor module is `mcr.microsoft.com/azureiotedge-simulated-temperature-sensor:1.5`. For a list of Microsoft IoT Edge module images, see the [Microsoft Artifact Registry](https://mcr.microsoft.com/catalog?cat=IoT%20Edge%20Modules&alphaSort=asc&alphaSortKey=Name).
    * **Azure Stream Analytics Module** - Modules generated from an Azure Stream Analytics workload.
 
-1. If needed, repeat steps 2 and 3 to add additional modules to your deployment.
+1. If needed, repeat steps 2 and 3 to add more modules to your deployment.
 
-After you add a module to a deployment, you can select its name to open the **Update IoT Edge Module** page. On this page, you can edit the module settings, environment variables, create options, startup order, and module twin. If you added a module from the marketplace, it may already have some of these parameters filled in. For more information about the available module settings, see [Module configuration and management](module-composition.md#module-configuration-and-management).
+After you add a module to a deployment, you can select its name to open the **Update IoT Edge Module** page. On this page, you can edit the module settings, environment variables, create options, startup order, and module twin. If you added a module from the marketplace, it might already have some of these parameters filled in. For more information about the available module settings, see [Module configuration and management](module-composition.md#module-configuration-and-management).
 
-If you're creating a layered deployment, you may be configuring a module that exists in other deployments targeting the same devices. To update the module twin without overwriting other versions, open the **Module Twin Settings** tab. Create a new **Module Twin Property** with a unique name for a subsection within the module twin's desired properties, for example `properties.desired.settings`. If you define properties within just the `properties.desired` field, it overwrites the desired properties for the module defined in any lower priority deployments.
+If you're creating a layered deployment, you might be configuring a module that exists in other deployments targeting the same devices. To update the module twin without overwriting other versions, open the **Module Twin Settings** tab. Create a new **Module Twin Property** with a unique name for a subsection within the module twin's desired properties, for example `properties.desired.settings`. If you define properties within just the `properties.desired` field, it overwrites the desired properties for the module defined in any lower priority deployments.
 
 :::image type="content" source="./media/how-to-deploy-monitor/module-twin-property.png" alt-text="Screenshot showing how to set the module twin property for layered deployment.":::
 
@@ -87,7 +87,7 @@ Once you have all the modules for a deployment configured, select **Next: Routes
 
 ### Step 3: Routes
 
-On the **Routes** tab, you define how messages are passed between modules and the IoT Hub. Messages are constructed using name/value pairs.
+On the **Routes** tab, you define how messages are passed between modules and the IoT hub. Messages are constructed using name/value pairs.
 
 For example, a route with a name **route** and a value **FROM /messages/\* INTO $upstream** would take any messages output by any modules and send them to your IoT hub.  
 
@@ -99,11 +99,11 @@ Select **Next: Target Devices**.
 
 ### Step 4: Target devices
 
-Use the tags property from your devices to target the specific devices that should receive this deployment.
+To target the specific devices that should receive this deployment, use the `tags` property from your devices.
 
 Since multiple deployments may target the same device, you should give each deployment a priority number. If there's ever a conflict, the deployment with the highest priority (larger values indicate higher priority) wins. If two deployments have the same priority number, the one that was created most recently wins.
 
-If multiple deployments target the same device, then only the one with the higher priority is applied. If multiple layered deployments target the same device then they are all applied. However, if any properties are duplicated, like if there are two routes with the same name, then the one from the higher priority layered deployment overwrites the rest.
+If multiple deployments target the same device, then only the one with the higher priority is applied. If multiple layered deployments target the same device, then they're all applied. However, if any properties are duplicated, like if there are two routes with the same name, then the one from the higher priority layered deployment overwrites the rest.
 
 Any layered deployment targeting a device must have a higher priority than the base deployment in order to be applied.
 
@@ -114,7 +114,7 @@ Select **Next: Metrics**.
 
 ### Step 5: Metrics
 
-Metrics provide summary counts of the various states that a device may report back as a result of applying configuration content.
+Metrics provide summary counts of the various states that a device might report back as a result of applying configuration content.
 
 1. Enter a name for **Metric Name**.
 
@@ -127,7 +127,7 @@ Metrics provide summary counts of the various states that a device may report ba
      WHERE properties.reported.lastDesiredStatus.code = 200
    ```
 
-Select **Next: Review + Create** to move on to the final step.
+Select **Next: Review + create** to move on to the final step.
 
 ### Step 6: Review and create
 
@@ -136,7 +136,7 @@ Review your deployment information, then select **Create**.
 To monitor your deployment, see [Monitor IoT Edge deployments](how-to-monitor-iot-edge-deployments.md).
 
 > [!NOTE]
-> When a new IoT Edge deployment is created, sometimes it can take up to 5 minutes for the IoT Hub to process the new configuration and propagate the new desired properties to the targeted devices.
+> When a new IoT Edge deployment is created, sometimes it can take up to 5 minutes for the IoT hub to process the new configuration and propagate the new desired properties to the targeted devices.
 
 ## Modify a deployment
 
@@ -150,32 +150,32 @@ When you modify a deployment, the changes immediately replicate to all targeted
 
 ### Modify target conditions, custom metrics, and labels
 
-1. In your IoT hub, select **Configurations + Deployments** from the left pane menu.
+1. In your IoT hub, select **Configurations + Deployments** under **Device management ** from the resource menu.
 1. Select the deployment you want to configure.
 1. Select the **Target Devices** tab. Change the **Target Condition** to target the intended devices. You can also adjust the **Priority**.
 
     If you update the target condition, the following updates occur:
 
     * If a device didn't meet the old target condition, but meets the new target condition and this deployment is the highest priority for that device, then this deployment is applied to the device.
     * If a device currently running this deployment no longer meets the target condition, it uninstalls this deployment and takes on the next highest priority deployment.
-    * If a device currently running this deployment no longer meets the target condition and doesn't meet the target condition of any other deployments, then no change occurs on the device. The device continues running its current modules in their current state, but is not managed as part of this deployment anymore. Once it meets the target condition of any other deployment, it uninstalls this deployment and takes on the new one.
+    * If a device currently running this deployment no longer meets the target condition and doesn't meet the target condition of any other deployments, then no change occurs on the device. The device continues running its current modules in their current state, but isn't managed as part of this deployment anymore. Once it meets the target condition of any other deployment, it uninstalls this deployment and takes on the new one.
 
-1. Select the **Metrics** tab and select the **Edit Metrics** button. Add or modify custom metrics, using the example syntax as a guide. Select **Save**.
+1. Select the **Metrics** tab and add or modify custom metrics, using the example syntax as a guide. Select **Save**.
 
    :::image type="content" source="./media/how-to-deploy-monitor/metric-list.png" alt-text="Screenshot showing how to edit custom metrics in a deployment.":::
 
 1. Select the **Labels** tab and make any desired changes and select **Save**.
 
 ## Delete a deployment
 
-When you delete a deployment, any deployed devices take on their next highest priority deployment. If your devices don't meet the target condition of any other deployment, then the modules are not removed when the deployment is deleted.
+When you delete a deployment, any deployed devices take on their next highest priority deployment. If your devices don't meet the target condition of any other deployment, then the modules aren't removed when the deployment is deleted.
 
-1. Sign in to the [Azure portal](https://portal.azure.com) and navigate to your IoT Hub.
-1. Select **Configurations + Deployments**.
+1. Sign in to the [Azure portal](https://portal.azure.com) and navigate to your IoT hub.
+1. In the resource menu, select **Configurations + Deployments** under **Device management**.
 1. Use the checkbox to select the deployment that you want to delete.
-1. Select **Delete**.
-1. A prompt informs you that this action deletes this deployment and revert to the previous state for all devices. A deployment with a lower priority will apply. If no other deployment is targeted, no modules are removed. If you want to remove all modules from your device, create a deployment with zero modules and deploy it to the same devices. Select **Yes** to continue.
+1. Select **Delete** from the command bar.
+1. A prompt informs you that this action deletes this deployment and revert to the previous state for all devices. A deployment with a lower priority applies. If no other deployment is targeted, no modules are removed. If you want to remove all modules from your device, create a deployment with zero modules and deploy it to the same devices. Select **Yes** to continue.
 
 ## Next steps
 
-Learn more about [Deploying modules to IoT Edge devices](module-deployment-monitoring.md).
+To learn more about deploying modules to IoT Edge devices, see  [Understand IoT Edge automatic deployments for single devices or at scale](module-deployment-monitoring.md).