Update device-update-agent-provisioning.md

ValOlson · web-flow · commit 8fce39803beb · 2021-03-31T17:07:06.000-07:00
diff --git a/articles/iot-hub-device-update/device-update-agent-provisioning.md b/articles/iot-hub-device-update/device-update-agent-provisioning.md
@@ -13,65 +13,65 @@ The Device Update Module agent can run alongside other system processes and [IoT
 Module Identity vs Device Identity: In IoT Hub, under each device identity, you can create up to 50 module identities. Each module identity implicitly generates a module twin. On the device side, the IoT Hub device SDKs enable you to create modules where each one opens an independent connection to IoT Hub. Module identity and module twin provide the similar capabilities as device identity and device twin but at a finer granularity. [Learn more about Module Identities in IoT Hub](https://docs.microsoft.com/azure/iot-hub/iot-hub-devguide-module-twins)
 
 Currently supported IoT device types with Device Update:
-1.	Linux devices (IoT Edge and Non-IoT Edge devices):
-    * Image A/B update:
+*	Linux devices (IoT Edge and Non-IoT Edge devices):
+    + Image A/B update:
       - Yocto - ARM64 (reference image), extensible via open source to [build you own images](device-update-agent-provisioning.md#how-to-build-and-run-device-update-agent) for other architecture as needed.
       - Ubuntu 18.04 simulator
-    * Package Agent supported builds for the following platforms/architectures.
+    + Package Agent supported builds for the following platforms/architectures.
       - Ubuntu Server 18.04 x64 Package Agent 
       - Debian 9 
-2.	Constrained devices:
-    * AzureRTOS Device Update agent samples: [Device Update for Azure IoT Hub tutorial for Azure-Real-Time-Operating-System](device-update-azure-real-time-operating-system.md)
-3.	Disconnected devices: 
-    * [Understand support for disconnected device update](connected-cache-disconnected-device-update.md)
+*	Constrained devices:
+    + AzureRTOS Device Update agent samples: [Device Update for Azure IoT Hub tutorial for Azure-Real-Time-Operating-System](device-update-azure-real-time-operating-system.md)
+*	Disconnected devices: 
+    + [Understand support for disconnected device update](connected-cache-disconnected-device-update.md)
 
 ## Pre-Requisite  
 If you are setting up the IoT device/IoT Edge device for [package based updates](https://docs.microsoft.com/azure/iot-hub-device-update/understand-device-update#support-for-a-wide-range-of-update-artifacts), add packages.microsoft.com to your machine’s repositories by following the steps below:
 1.	Log onto the machine or IoT device on which you intend to install the Device Update agent.
 2.	Open a Terminal window.
 3.	Install the repository configuration that matches your device’s operating system.
-   ```shell
-   curl https://packages.microsoft.com/config/ubuntu/18.04/multiarch/prod.list > ./microsoft-prod.list
-   ```
+      ```shell
+      curl https://packages.microsoft.com/config/ubuntu/18.04/multiarch/prod.list > ./microsoft-prod.list
+      ```
 4.	Copy the generated list to the sources.list.d directory.
-   ```shell
-   sudo cp ./microsoft-prod.list /etc/apt/sources.list.d/
-   ```
+      ```shell
+      sudo cp ./microsoft-prod.list /etc/apt/sources.list.d/
+      ```
 5.	Install the Microsoft GPG public key.
-   ```shell
-   curl https://packages.microsoft.com/keys/microsoft.asc | gpg --dearmor > microsoft.gpg
-   ```
-   ```shell
-   sudo cp ./microsoft.gpg /etc/apt/trusted.gpg.d/
-   ```
+      ```shell
+      curl https://packages.microsoft.com/keys/microsoft.asc | gpg --dearmor > microsoft.gpg
+      ```
+      ```shell
+      sudo cp ./microsoft.gpg /etc/apt/trusted.gpg.d/
+      ```
 
 ## How to provision the Device Update agent as a Module Identity
-This section describes how to provision the Device Update agent as a module identity.
+This section describes how to provision the Device Update agent as a module identity on IoT Edge enabled devices, non-Edge IoT devices, and other IoT devices.
 
-### 1. On IoT Edge enabled devices
+### On IoT Edge enabled devices
 Follow these instructions to provision the Device Update agent on [IoT Edge enabled devices](https://docs.microsoft.com/azure/iot-edge).
 1.	Follow the instructions to [Install and provision the Azure IoT Edge runtime](https://docs.microsoft.com/azure/iot-edge/how-to-install-iot-edge?view=iotedge-2020-11&preserve-view=true).
 2.	Then install the Device Update agent from [Artifacts](https://github.com/Azure/iot-hub-device-update/releases) and you are now ready to start the Device Update agent on your IoT Edge device.
 
-### 2. On non-Edge IoT Linux devices
+### On non-Edge IoT Linux devices
 Follow these instructions to provision the Device Update agent on your IoT Linux devices.
 1.	Install the IoT Identity Service and add the latest version to your IoT device. 
     * Log onto the machine or IoT device.
     * Open a terminal window.
     *	Install the latest [IoT Identity Service](https://github.com/Azure/iot-identity-service/blob/main/docs/packaging.md#installing-and-configuring-the-package) on your IoT device using the command below.
-   ```shell
-   sudo apt-get install aziot-identity-service
-   ```
+      ```shell
+      sudo apt-get install aziot-identity-service
+      ```
 2.	Provisioning IoT Identity service to get the IoT device information.
     * Create a custom copy of the configuration template so we can add the provisioning information. In a terminal, enter the below command.
-   ```shell
-   sudo cp /etc/aziot/config.toml.template /etc/aziot/config.toml 
-   ```
+      ```shell
+      sudo cp /etc/aziot/config.toml.template /etc/aziot/config.toml 
+      ```
    
 3. Next edit the configuration file to include the connection string of the device you wish to act as the provisioner for this device or machine. In a terminal, enter the below command.
-   ```shell
-   sudo nano /etc/aziot/config.toml
-   ```
+      ```shell
+      sudo nano /etc/aziot/config.toml
+      ```
    
 4. You should be greeted with a view like below:
 :::image type="content" source="media/understand-device-update/config.png" alt-text="Diagram of IoT Identity Service config file." lightbox="media/understand-device-update/config.png"::: 
@@ -82,12 +82,12 @@ Follow these instructions to provision the Device Update agent on your IoT Linux
     * In the window, delete the string within the quotes to the right of 'connection_string' and then add your connection string there 
     * Save your changes to the file with 'Ctrl+X' and then 'Y' and hit the 'enter' key to save your changes. 
 5.	Now apply and restart the IoT Identity service with the command below. You should now see a “Done!” printout that means you have successfully configured the IoT Identity Service. Note: The IoT Identity service registers    module identities with IoT Hub using symmetric keys currently.
-   ```shell
-   sudo aziotctl config apply
-   ```
+      ```shell
+      sudo aziotctl config apply
+      ```
 6.	Finally install the Device Update agent from [Artifacts](https://github.com/Azure/iot-hub-device-update/releases) and you are now ready to start the Device Update agent on your IoT Edge device.
 
-### 3. Other IoT devices
+### Other IoT devices
 The Device Update agent can also be configured without the IoT Identity service for testing or on constrained devices. Follow the below steps to provision the Device Update agent using a connection string (from the Module or Device).
 1.	Install Device Update agent from [Artifacts](https://github.com/Azure/iot-hub-device-update/releases).
 2.	Log onto the machine or IoT Edge device/IoT device.
@@ -106,13 +106,13 @@ The Device Update agent can also be configured without the IoT Identity service
 This section describes how to start and verify the Device Update agent as a module identity running successfully on your IoT device.
 1.	Log into the machine or device that has the Device Update agent installed.
 2.	Open a Terminal window, and enter the command below.
-   ```shell
-   sudo systemctl restart adu-agent
-   ```
+      ```shell
+      sudo systemctl restart adu-agent
+      ```
 3.	You can check the status of the agent using the command below. If you see any issues, refer to this [troubleshooting guide](troubleshoot-device-update.md).
-   ```shell
-   sudo systemctl status adu-agent
-   ```
+      ```shell
+      sudo systemctl status adu-agent
+      ```
 4.	You should see status OK.
 5.	On the IoT Hub portal,  go to IoT device or IoT Edge devices to find the device that you configured with Device Update agent. There you will see the Device Update agent running as a module, For example:
 :::image type="content" source="media/understand-device-update/device-update-module.png " alt-text="Diagram of Device Update module name." lightbox="media/understand-device-update/device-update-module.png":::
