Device how to articles

Author: dominicbetts

articles/iot-central/core/how-to-connect-devices-x509.md

@@ -3,7 +3,7 @@ title: Connect devices with X.509 certificates in an Azure IoT Central applicati
 description: How to connect devices with X.509 certificates using Node.js device SDK for IoT Central Application
 author: dominicbetts
 ms.author: dobett
-ms.date: 09/13/2022
+ms.date: 10/31/2022
 ms.topic: how-to
 ms.service: iot-central
 services: iot-central
@@ -111,7 +111,7 @@ Make a note of the location of these files. You need it later.
 
 1. The status of the primary certificate is now **Verified**:
 
-    ![Verified Certificate](./media/how-to-connect-devices-x509/verified.png)
+    :::image type="content" source="media/how-to-connect-devices-x509/verified.png" alt-text="Screenshot that shows a verified X509 certificate." lightbox="media/how-to-connect-devices-x509/verified.png":::
 
 You can now connect devices that have an X.509 certificate derived from this primary root certificate.
 
@@ -206,7 +206,7 @@ To run the sample:
 
 Verify that telemetry appears on the device view in your IoT Central application:
 
-![Screenshot that shows telemetry arriving in your IoT Central application.](./media/how-to-connect-devices-x509/telemetry.png)
+:::image type="content" source="media/how-to-connect-devices-x509/telemetry.png" alt-text="Screenshot showing telemetry from a device that connected using X.509." lightbox="media/how-to-connect-devices-x509/telemetry.png":::
 
 ## Use individual enrollment
 
@@ -257,7 +257,7 @@ These commands produce the following device certificates:
 
 1. The device now has an individual enrollment with X.509 certificates.
 
-    ![Individual enrollment certificates](./media/how-to-connect-devices-x509/individual-enrollment.png)
+    :::image type="content" source="media/how-to-connect-devices-x509/individual-enrollment.png" alt-text="Screenshot that shows how to connect a device using an X.509 individual enrollment." lightbox="media/how-to-connect-devices-x509/individual-enrollment.png":::
 
 ### Run a sample individual enrollment device
 

articles/iot-central/core/howto-connect-rigado-cascade-500.md

@@ -7,7 +7,7 @@ ms.topic: how-to
 ms.custom: [iot-storeAnalytics-conditionMonitor, iot-p0-scenario]
 author: dominicbetts
 ms.author: dobett
-ms.date: 06/15/2022
+ms.date: 11/01/2022
 
 # This article applies to solution builders.
 ---
@@ -40,11 +40,11 @@ To add a Cascade 500 device template:
 
 1. The page gives you an option to **Create a custom template** or **Use a preconfigured device template**.
 
-1. Select the C500 device template from the list of preconfigured device templates.
+1. Select the Cascade-500 device template from the list of featured device templates.
 
-1. Select **Next: Customize** to continue to the next step.
+1. Select **Next: Review** to continue to the next step.
 
-1. On the next screen, select **Create** to onboard the C500 device template into your IoT Central application.
+1. On the next screen, select **Create** to onboard the Cascade-500 device template into your IoT Central application.
 
 ## Retrieve application connection details
 
@@ -54,11 +54,11 @@ To connect the Cascade 500 device to your IoT Central application, you need to r
 
 1. Make a note of the **ID Scope** for your IoT Central application:
 
-    ![App ID Scope](./media/howto-connect-rigado-cascade-500/app-scope-id.png)
+    :::image type="content" source="media/howto-connect-rigado-cascade-500/app-scope-id.png" alt-text="Screenshot that shows the ID scope for your application." lightbox="media/howto-connect-rigado-cascade-500/app-scope-id.png":::
 
 1. Now select **SAS-IoT-Edge-Devices** and make a note of the **Primary key**:
 
-    ![Primary Key](./media/howto-connect-rigado-cascade-500/primary-key-sas.png)  
+    :::image type="content" source="media/howto-connect-rigado-cascade-500/primary-key-sas.png" alt-text="Screenshot that shows the primary SAS key for you device connection group." lightbox="media/howto-connect-rigado-cascade-500/primary-key-sas.png":::
 
 ## Contact Rigado to connect the gateway
 
@@ -68,9 +68,9 @@ When the device connects to the internet, Rigado can push down a configuration u
 
 This update applies the IoT Central connection details on the Cascade 500 device and it then appears in your devices list:
 
-![Devices list](./media/howto-connect-rigado-cascade-500/devices-list-c500.png)  
+:::image type="content" source="media/howto-connect-rigado-cascade-500/devices-list-c500.png" alt-text="Screenshot that shows a Cascade-500 device connection to your application." lightbox="media/howto-connect-rigado-cascade-500/devices-list-c500.png":::
 
-You're now ready to use your C500 device in your IoT Central application.
+You're now ready to use your Cascade-500 device in your IoT Central application.
 
 ## Next steps
 

articles/iot-central/core/howto-connect-ruuvi.md

@@ -7,7 +7,7 @@ ms.topic: how-to
 ms.custom: [iot-storeAnalytics-conditionMonitor, iot-p0-scenario]
 ms.author: avneets
 author: avneet723
-ms.date: 08/20/2021
+ms.date: 11/01/2022
 
 # This article applies to solution builders.
 ---
@@ -56,7 +56,7 @@ To connect the RuuviTag with your IoT Central application, you need to set up a
 
 1. In a few seconds, your RuuviTag appears in the list of devices within IoT Central:
 
-    ![RuuviTag Device List](./media/howto-connect-ruuvi/ruuvi-device-list.png)
+    :::image type="content" source="media/howto-connect-ruuvi/ruuvi-device-list.png" alt-text="Screenshot that shows the device list with a RuuviTag." lightbox="media/howto-connect-ruuvi/ruuvi-device-list.png":::
 
 You can now use this RuuviTag device within your IoT Central application.  
 

articles/iot-central/core/howto-edit-device-template.md

@@ -3,7 +3,7 @@ title: Edit a device template in your Azure IoT Central application | Microsoft
 description: Iterate over your device templates without impacting your live connected devices
 author: dominicbetts
 ms.author: dobett
-ms.date: 06/22/2022
+ms.date: 10/31/2022
 ms.topic: how-to
 ms.service: iot-central
 services: iot-central
@@ -74,7 +74,7 @@ The following snippet shows the device model for a thermostat device. The device
 
 To view this information in the IoT Central UI, select **View identity** in the device template editor:
 
-:::image type="content" source="media/howto-edit-device-template/view-identity.png" alt-text="View the identity of an interface to see the version number":::
+:::image type="content" source="media/howto-edit-device-template/view-identity.png" alt-text="View the identity of an interface to see the version number" lightbox="media/howto-edit-device-template/view-identity.png":::
 
 ## Version a device template
 
@@ -107,7 +107,7 @@ You can create multiple versions of the device template. Over time, you'll have
 1. Select the device you need to migrate to another version.
 1. Choose **Migrate**:
 
-    :::image type="content" source="media/howto-edit-device-template/migrate-device.png" alt-text="Choose the option to start migrating a device":::
+    :::image type="content" source="media/howto-edit-device-template/migrate-device.png" alt-text="Choose the option to start migrating a device" lightbox="media/howto-edit-device-template/migrate-device.png":::
 
 1. Select the device template with the version you want to migrate the device to and select **Migrate**.
 

articles/iot-central/core/howto-use-commands.md

@@ -3,7 +3,7 @@ title: How to use device commands in an Azure IoT Central solution
 description: How to use device commands in Azure IoT Central solution. This tutorial shows you how to use device commands in client app to your Azure IoT Central application. 
 author: dominicbetts
 ms.author: dobett
-ms.date: 06/22/2022 
+ms.date: 10/31/2022 
 ms.topic: how-to
 ms.service: iot-central
 services: iot-central
@@ -32,7 +32,7 @@ Standard commands are sent to a device to instruct the device to do something. A
 
 Commands are defined as part of a device template. The following screenshot shows the **Get Max-Min report** command definition in the **Thermostat** device template. This command has both request and response parameters: 
 
-:::image type="content" source="media/howto-use-commands/command-definition.png" alt-text="Screenshot showing Get Max Min Report command in Thermostat device template":::
+:::image type="content" source="media/howto-use-commands/command-definition.png" alt-text="Screenshot showing Get Max Min Report command in Thermostat device template" lightbox="media/howto-use-commands/command-definition.png":::
 
 The following table shows the configuration settings for a command capability:
 
@@ -155,7 +155,7 @@ The call to `onDeviceMethod` sets up the `commandHandler` method. This command h
 
 The following screenshot shows how the successful command response displays in the IoT Central UI:
 
-:::image type="content" source="media/howto-use-commands/simple-command-ui.png" alt-text="Screenshot showing how to view command payload for a standard command":::
+:::image type="content" source="media/howto-use-commands/simple-command-ui.png" alt-text="Screenshot showing how to view command payload for a standard command" lightbox="media/howto-use-commands/simple-command-ui.png":::
 
 ## Long-running commands
 
@@ -208,7 +208,7 @@ The call to `onDeviceMethod` sets up the `commandHandler` method. This command h
 
 The following screenshot shows the IoT Central UI when it receives the property update that indicates the command is complete:
 
-:::image type="content" source="media/howto-use-commands/long-running-finish.png" alt-text="Screenshot that shows long-running command finished":::
+:::image type="content" source="media/howto-use-commands/long-running-finish.png" alt-text="Screenshot that shows long-running command finished" lightbox="media/howto-use-commands/long-running-finish.png":::
 
 ## Offline commands
 
@@ -219,7 +219,7 @@ This section shows you how a device handles an offline command. If a device is o
 
 The following screenshot shows an offline command called **GenerateDiagnostics**. The request parameter is an object with datetime property called **StartTime** and an integer enumeration property called **Bank**:
 
-:::image type="content" source="media/howto-use-commands/offline-command.png" alt-text="Screenshot that shows the UI for an offline command":::
+:::image type="content" source="media/howto-use-commands/offline-command.png" alt-text="Screenshot that shows the UI for an offline command" lightbox="media/howto-use-commands/offline-command.png":::
 
 The following code snippet shows how a client can listen for offline commands and display the message contents:
 
@@ -251,7 +251,7 @@ Properties: {"propertyList":[{"key":"iothub-ack","value":"none"},{"key":"method-
 
 You can call commands on a device that isn't assigned to a device template. To call a command on an unassigned device navigate to the device in the **Devices** section, select **Manage device** and then **Command**. Enter the method name, payload, and any other required values. The following screenshot shows the UI you use to call a command:
 
-:::image type="content" source="media/howto-use-commands/unassigned-commands.png" alt-text="Screenshot that shows an example of calling a command on an unassigned device.":::
+:::image type="content" source="media/howto-use-commands/unassigned-commands.png" alt-text="Screenshot that shows an example of calling a command on an unassigned device." lightbox="media/howto-use-commands/unassigned-commands.png":::
 
 ## Next steps