final screenshots and cli ref links

Author: kgremban

articles/iot-hub/media/tutorial-connectivity/desired-properties.png

@@ -5,7 +5,7 @@ services: iot-hub
 author: kgremban
 ms.author: kgremban
 ms.custom: [mvc, amqp, mqtt, 'Role: Cloud Development', 'Role: IoT Device', devx-track-js, devx-track-azurecli]
-ms.date: 10/26/2021
+ms.date: 02/01/2023
 ms.topic: tutorial
 ms.service: iot-hub
 
@@ -80,15 +80,15 @@ To simulate a device sending telemetry to your IoT hub, run the Node.js simulate
 
    The terminal window displays a success message once it connects to your hub:
 
-   :::image type="content" source="{media/tutorial-connectivity/sim-1-connected.png}" alt-text="Screenshot that shows the simulated device connecting.":::
+   :::image type="content" source="media/tutorial-connectivity/sim-1-connected.png" alt-text="Screenshot that shows the simulated device connecting.":::
 
 You've now successfully authenticated from a device using a device key generated by your IoT hub.
 
 ### Reset keys
 
 In this section, you reset the device key and observe the error when the simulated device tries to connect.
 
-1. To reset the primary device key for your device, run the following commands:
+1. To reset the primary device key for your device, run the [az iot hub device-identity update](/cli/azure/iot/hub/device-identity#az-iot-hub-device-identity-update) command:
 
    ```azurecli-interactive
    # Generate a new Base64 encoded key using the current date
@@ -118,7 +118,7 @@ In some scenarios, such as in a cloud protocol gateway or as part of a custom au
 > [!NOTE]
 > The SimulatedDevice-2.js sample includes examples of generating a SAS token both with and without the SDK.
 
-1. Run the following command to generate a known-good SAS token using the CLI:
+1. Run the [az iot hub genereate-sas-token](/cli/azure/iot/hub#az-iot-hub-generate-sas-token) command to generate a known-good SAS token using the CLI:
 
    ```azurecli-interactive
    az iot hub generate-sas-token --device-id {your_device_id} --hub-name {your_iot_hub_name}
@@ -155,15 +155,15 @@ A device can use any of the following protocols to connect to your IoT hub:
 
 If the outbound port is blocked by a firewall, the device can't connect:
 
-![Port blocked](media/tutorial-connectivity/port-blocked.png)
+:::image type="content" source="media/tutorial-connectivity/port-blocked.png" alt-text="Screenshot that shows a connection error when the outbound port is blocked.":::
 
 ## Check device-to-cloud connectivity
 
 After a device connects, it can start sending telemetry to your IoT hub. This section shows you how you can verify that the telemetry sent by the device reaches your hub.
 
 ### Send device-to-cloud messages
 
-1. Since we reset the connection string for your device in the previous section, use the following command to retrieve the updated connection string:
+1. Since we reset the connection string for your device in the previous section, use the [az iot hub device-identity connection-string show](/cli/azure/iot/hub/device-identity/connection-string#az-iot-hub-device-identity-connection-string-show) command to retrieve the updated connection string:
 
    ```azurecli-interactive
    az iot hub device-identity connection-string show --device-id {your_device_id} --output table --hub-name {your_iot_hub_name}
@@ -206,19 +206,19 @@ This section shows how you can make a test direct method call to a device to che
    node SimulatedDevice-3.js "{your_device_connection_string}"
    ```
 
-1. In a separate window, use a CLI command to call a direct method on the device:
+1. In a separate window, use the [az iot hub invoke-device-method](/cli/azure/iot/hub#az-iot-hub-invoke-device-method) command to call a direct method on the device:
 
    ```azurecli-interactive
    az iot hub invoke-device-method --device-id {your_device_id} --method-name TestMethod --timeout 10 --method-payload '{"key":"value"}' --hub-name {your_iot_hub_name}
    ```
 
    The simulated device prints a message to the console when it receives a direct method call:
 
-   ![Simulated device receives direct method call](media/tutorial-connectivity/receive-method-call.png)
+   :::image type="content" source="media/tutorial-connectivity/receive-method-call.png" alt-text="Screenshot that shows the device confirming that the direct method was received.":::
 
    When the simulated device successfully receives the direct method call, it sends an acknowledgment back to the hub:
 
-   ![Receive direct method acknowledgment](media/tutorial-connectivity/method-acknowledgement.png)
+   :::image type="content" source="media/tutorial-connectivity/method-acknowledgement.png" alt-text="Screenshot showing that the device returns a direct method acknowledgment.":::
 
 ## Check twin synchronization
 
@@ -232,25 +232,25 @@ The simulated device you use in this section sends reported properties to the hu
    node SimulatedDevice-3.js "{your_device_connection_string}"
    ```
 
-1. In a separate window, run the following CLI command to verify that the hub received the reported properties from the device:
+1. In a separate window, run the [az iot hub device-twin show](/cli/azure/iot/hub/device-twin#az-iot-hub-device-twin-show) command to verify that the hub received the reported properties from the device:
 
-```azurecli-interactive
-az iot hub device-twin show --device-id {your_device_id} --hub-name {your_iot_hub_name}
-```
+   ```azurecli-interactive
+   az iot hub device-twin show --device-id {your_device_id} --hub-name {your_iot_hub_name}
+   ```
 
    In the output from the command, you can see the **devicelaststarted** property in the reported properties section. This property shows the date and time you last started the simulated device.
 
-   ![View reported properties](media/tutorial-connectivity/reported-properties.png)
+   :::image type="content" source="(media/tutorial-connectivity/reported-properties.png" alt-text="Screenshot showing the reported properties of a device.":::
 
-1. To verify that the hub can send desired property values to the device, use the following CLI command:
+1. To verify that the hub can send desired property values to the device, use the [az iot hub device-twin update](/cli/azure/iot/hub/device-twin#az-iot-hub-device-twin-update) command:
 
    ```azurecli-interactive
    az iot hub device-twin update --set properties.desired='{"mydesiredproperty":"propertyvalue"}' --device-id {your_device_id} --hub-name {your_iot_hub_name}
    ```
 
    The simulated device prints a message when it receives a desired property update from the hub:
 
-   ![Receive desired properties](media/tutorial-connectivity/desired-properties.png)
+   :::image type="content" source="media/tutorial-connectivity/desired-properties.png" alt-text="Screenshot that shows the device confirming that the desired properties update was received.":::
 
 In addition to receiving desired property changes as they're made, the simulated device automatically checks for desired properties when it starts up.