Merge pull request #297257 from DENKEN02MSFT/IoTFreshness_Row18

IoT Freshness - row 18

Author: JamesJBarnett

articles/iot-hub/quickstart-control-device.md

@@ -7,7 +7,7 @@ ms.service: azure-iot-hub
 services: iot-hub
 ms.topic: quickstart
 ms.custom: [mvc, mqtt, "Role: Cloud Development", devx-track-azurecli, mode-other, devx-track-dotnet, devx-track-extended-java, devx-track-python, devx-track-js]
-ms.date: 02/25/2022
+ms.date: 03/28/2025
 zone_pivot_groups: iot-hub-set1
 #Customer intent: As a developer new to IoT Hub, I need to see how to use a service application to control a device connected to the hub.
 ---
@@ -51,4 +51,4 @@ In this quickstart, you called a direct method on a device from a service applic
 To learn how to route device-to-cloud messages to different destinations in the cloud, continue to the next tutorial.
 
 > [!div class="nextstepaction"]
-> [Tutorial: Route telemetry to different endpoints for processing](tutorial-routing.md)
+> [Tutorial: Send device data to Azure Storage using IoT Hub message routing](tutorial-routing.md)

includes/iot-hub-cli-version-info.md

@@ -1,20 +1,20 @@
 ---
- title: include file
- description: include file
+ title: Include file
+ description: An include file describing the Azure IoT extension and the az extension commands you can use to list, add, and remove the Azure IoT extension.
  services: iot-hub
  author: SoniaLopezBravo
  ms.service: azure-iot-hub
  ms.topic: include
- ms.date: 03/05/2020
+ ms.date: 03/28/2025
  ms.author: sonialopez
  ms.custom: include file
 ---
 > [!NOTE]
-> This article uses the newest version of the Azure IoT extension, called `azure-iot`. The legacy version is called `azure-cli-iot-ext`.You should only have one version installed at a time. You can use the command `az extension list` to validate the currently installed extensions.
+> This article uses the newest version of the Azure IoT extension, called `azure-iot`. The legacy version is called `azure-cli-iot-ext`. You should only have one version installed at a time. You can use the command `az extension list` to validate the currently installed extensions.
 >
 > Use `az extension remove --name azure-cli-iot-ext` to remove the legacy version of the extension.
 >
 > Use `az extension add --name azure-iot` to add the new version of the extension. 
 >
-> To see what extensions you have installed, use `az extension list`.
+> To see what extensions are currently installed, use `az extension list`.
 >

includes/iot-hub-include-create-device-cli.md

@@ -5,7 +5,7 @@ author: SoniaLopezBravo
 ms.author: sonialopez
 ms.service: azure-iot-hub
 ms.topic: include
-ms.date: 01/31/2023
+ms.date: 03/28/2025
 ---
 
 A device must be registered with your IoT hub before it can connect. In this section, you use Azure CLI to create a device identity.
@@ -16,18 +16,18 @@ To create a device identity:
 
 1. Run the [az iot hub device-identity create](/cli/azure/iot/hub/device-identity#az-iot-hub-device-identity-create) command in your CLI shell. This command creates the device identity.
 
-    *your_iot_hub_name*. Replace this placeholder below with the name you chose for your IoT hub.
+    *YourIoTHubName*. Replace this placeholder and the surrounding braces in the following command, using the name you chose for your IoT hub. An IoT hub name must be globally unique in Azure. 
 
     *myDevice*. You can use this name for the device ID throughout this article, or provide a different device name.
 
     ```azurecli-interactive
-    az iot hub device-identity create --device-id myDevice --hub-name {your_iot_hub_name}
+    az iot hub device-identity create --device-id myDevice --hub-name {YourIoTHubName}
     ```
 
 1. Run 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.
 
     ```azurecli-interactive
-    az iot hub device-identity connection-string show --device-id myDevice --hub-name {your_iot_hub_name}
+    az iot hub device-identity connection-string show --device-id myDevice --hub-name {YourIoTHubName}
     ```
 
     The connection string output is in the following format:
@@ -39,4 +39,4 @@ To create a device identity:
 1. Save the connection string in a secure location.
 
 > [!NOTE]
-> Keep your CLI app open. You'll use it in later steps.
+> Keep your CLI app open. You use it in later steps.

includes/iot-hub-include-create-hub-cli.md

@@ -5,7 +5,7 @@ author: SoniaLopezBravo
 ms.author: sonialopez
 ms.service: azure-iot-hub
 ms.topic: include
-ms.date: 01/31/2023
+ms.date: 03/28/2025
 ---
 
 In this section, you use Azure CLI to create an IoT hub and a resource group.  An Azure resource group is a logical container into which Azure resources are deployed and managed. An IoT hub acts as a central message hub for bi-directional communication between your IoT application and the devices.
@@ -36,8 +36,8 @@ To create an IoT hub and a resource group:
 
 1. Run the [az iot hub create](/cli/azure/iot/hub#az-iot-hub-create) command to create an IoT hub. It might take a few minutes to create an IoT hub.
 
-    *YourIotHubName*. Replace this placeholder and the surrounding braces in the following command, using the name you chose for your IoT hub. An IoT hub name must be globally unique in Azure. Use your IoT hub name in the rest of this quickstart wherever you see the placeholder.
+    *YourIoTHubName*. Replace this placeholder and the surrounding braces in the following command, using the name you chose for your IoT hub. An IoT hub name must be globally unique in Azure. Use your IoT hub name in the rest of this quickstart wherever you see the placeholder.
 
     ```azurecli-interactive
-    az iot hub create --resource-group MyResourceGroup --name {your_iot_hub_name}
+    az iot hub create --resource-group MyResourceGroup --name {YourIoTHubName}
     ```

includes/iot-hub-quickstarts-clean-up-resources.md

@@ -5,28 +5,30 @@ services: iot-hub
 author: SoniaLopezBravo
 ms.service: azure-iot-hub
 ms.topic: include
-ms.date: 06/19/2018
+ms.date: 03/28/2025
 ms.author: sonialopez
 ms.custom: include file
 ---
 
 
-If you will be continuing to the next recommended article, you can keep the resources you've already created and reuse them.
+If you're continuing to the next recommended article, you can keep the resources you already created and reuse them.
 
 Otherwise, you can delete the Azure resources created in this article to avoid charges. 
 
 > [!IMPORTANT]
-> Deleting a resource group is irreversible. The resource group and all the resources contained in it are permanently deleted. Make sure that you do not accidentally delete the wrong resource group or resources. If you created the IoT Hub inside an existing resource group that contains resources you want to keep, only delete the IoT Hub resource itself instead of deleting the resource group.
+> Deleting a resource group is irreversible. The resource group and all the resources contained in it are permanently deleted. Make sure that you don't accidentally delete the wrong resource group or resources. If you created the IoT hub inside an existing resource group that contains resources you want to keep, only delete the IoT Hub resource itself instead of deleting the resource group.
 >
 
 To delete a resource group by name:
 
 1. Sign in to the [Azure portal](https://portal.azure.com) and select **Resource groups**.
 
-2. In the **Filter by name** textbox, type the name of the resource group containing your IoT Hub. 
+2. In the **Filter for any field** textbox, type the name of the resource group containing your IoT hub.
 
-3. To the right of your resource group in the result list, select **...** then **Delete resource group**.
+3. In the result list, select the resource group containing your IoT hub. 
 
-    ![Delete](./media/iot-hub-quickstarts-clean-up-resources/iot-hub-delete-resource-group.png)
+4. In the working pane for the resource group, select **Delete resource group** from the command bar.
 
-4. You will be asked to confirm the deletion of the resource group. Type the name of your resource group again to confirm, and then select **Delete**. After a few moments, the resource group and all of its contained resources are deleted.
+    :::image type="content" source="./media/iot-hub-quickstarts-clean-up-resources/iot-hub-delete-resource-group.png" alt-text="Screenshot that shows the working pane of a resource group in Azure portal, with the Delete resource group command highlighted in the command bar.":::
+    
+5. You're asked to confirm the deletion of the resource group. Type the name of your resource group again to confirm, and then select **Delete**. After a few moments, the resource group and all of its contained resources are deleted.

includes/media/iot-hub-quickstarts-clean-up-resources/iot-hub-delete-resource-group.png

@@ -6,10 +6,10 @@ services: iot-hub
 ms.devlang: csharp
 ms.topic: include
 ms.custom: [mvc, mqtt, 'Role: Cloud Development', devx-track-azurecli]
-ms.date: 03/08/2022
+ms.date: 03/28/2025
 ---
 
-The quickstart uses two pre-written .NET applications:
+The quickstart uses two prewritten .NET applications:
 
 * A simulated device application that responds to direct methods called from a service application. To receive the direct method calls, this application connects to a device-specific endpoint on your IoT hub.
 
@@ -29,9 +29,9 @@ The quickstart uses two pre-written .NET applications:
     dotnet --version
     ```
 
-* Clone or download the [Azure IoT C# SDK](https://github.com/Azure/azure-iot-sdk-csharp) from GitHub.
+* Clone or download the [Microsoft Azure IoT SDK for .NET](https://github.com/Azure/azure-iot-sdk-csharp) from GitHub. The sample applications used by this quickstart are included in the SDK.
 
-* Make sure that port 8883 is open in your firewall. The device sample in this quickstart uses MQTT protocol, which communicates over port 8883. This port may be blocked in some corporate and educational network environments. For more information and ways to work around this issue, see [Connecting to IoT Hub (MQTT)](../articles/iot/iot-mqtt-connect-to-iot-hub.md#connect-to-iot-hub).
+* Make sure that port 8883 is open in your firewall. The device sample in this quickstart uses MQTT protocol, which communicates over port 8883. This port might be blocked in some corporate and educational network environments. For more information and ways to work around this issue, see the [Connect to IoT Hub](../articles/iot/iot-mqtt-connect-to-iot-hub.md#connect-to-iot-hub) section of [Communicate with an IoT hub using the MQTT protocol](../articles/iot/iot-mqtt-connect-to-iot-hub.md).
 
 [!INCLUDE [azure-cli-prepare-your-environment.md](~/reusable-content/azure-cli/azure-cli-prepare-your-environment-no-header.md)]
 
@@ -59,9 +59,9 @@ You use this value later in the quickstart.
 
 The simulated device application connects to a device-specific endpoint on your IoT hub, sends simulated telemetry, and listens for direct method calls from your hub. In this quickstart, the direct method call from the hub tells the device to change the interval at which it sends telemetry. The simulated device sends an acknowledgment back to your hub after it executes the direct method.
 
-1. In a local terminal window, navigate to the root folder of the sample C# project. Then navigate to the **iothub\device\samples\getting started\SimulatedDeviceWithCommand** folder.
+1. In a local terminal window, navigate to the root folder of the SDK. Then, navigate to the **iothub\device\samples\getting started\SimulatedDeviceWithCommand** folder.
 
-2. Run the following command to install the required packages for simulated device application:
+2. Run the following command to install the required packages for the simulated device application:
 
     ```cmd/sh
     dotnet restore
@@ -77,13 +77,13 @@ The simulated device application connects to a device-specific endpoint on your
 
     The following screenshot shows the output as the simulated device application sends telemetry to your IoT hub:
 
-    ![Run the simulated device](./media/quickstart-control-device-dotnet/SimulatedDevice-1.png)
+    :::image type="content" source="./media/quickstart-control-device-dotnet/SimulatedDevice-1.png" alt-text="Screenshot of a terminal window that shows the output of the simulated device application.":::
 
 ## Call the direct method
 
 The service application connects to a service-side endpoint on your IoT Hub. The application makes direct method calls to a device through your IoT hub and listens for acknowledgments. An IoT Hub service application typically runs in the cloud.
 
-1. In another local terminal window, navigate to the root folder of the sample C# project. Then navigate to the **iothub\service\samples\getting started\InvokeDeviceMethod** folder.
+1. In another local terminal window, navigate to the root folder of the SDK. Then, navigate to the **iothub\service\samples\getting started\InvokeDeviceMethod** folder.
 
 2. In the local terminal window, run the following commands to install the required libraries for the service application:
 
@@ -103,8 +103,9 @@ The service application connects to a service-side endpoint on your IoT Hub. The
 
     The following screenshot shows the output as the application makes a direct method call to the device and receives an acknowledgment:
 
-    ![Run the service application](./media/quickstart-control-device-dotnet/BackEndApplication.png)
+    :::image type="content" source="./media/quickstart-control-device-dotnet/BackEndApplication.png" alt-text="Screenshot of a terminal window that shows the result of the direct method call from the service application.":::
+    
+    After you run the service application, you see a message in the local terminal window running the simulated device, and the rate at which it sends messages changes:
 
-    After you run the service application, you see a message in the console window running the simulated device, and the rate at which it sends messages changes:
-
-    ![Change in simulated client](./media/quickstart-control-device-dotnet/SimulatedDevice-2.png)
+    :::image type="content" source="./media/quickstart-control-device-dotnet/SimulatedDevice-2.png" alt-text="Screenshot of a terminal window that shows the direct message result and updated output from the simulated device application.":::
+    

includes/quickstart-control-device-dotnet.md

@@ -6,7 +6,7 @@ services: iot-hub
 ms.devlang: java
 ms.topic: include
 ms.custom: mvc, mqtt, devx-track-java, devx-track-azurecli
-ms.date: 01/31/2023
+ms.date: 03/28/2025
 ---
 
 This quickstart uses two Java applications: 
@@ -34,9 +34,9 @@ This quickstart uses two Java applications:
     mvn --version
     ```
 
-* Clone or download the [Azure IoT Java samples](https://github.com/Azure-Samples/azure-iot-samples-java/) from GitHub.
+* Clone or download the [Azure IoT Samples for Java](https://github.com/Azure-Samples/azure-iot-samples-java/) from GitHub.
 
-* Make sure that port 8883 open in your firewall. The device sample in this quickstart uses MQTT protocol, which communicates over port 8883. This port may be blocked in some corporate and educational network environments. For more information and ways to work around this issue, see [Connecting to IoT Hub (MQTT)](../articles/iot/iot-mqtt-connect-to-iot-hub.md#connect-to-iot-hub).
+* Make sure that port 8883 is open in your firewall. The device sample in this quickstart uses MQTT protocol, which communicates over port 8883. This port might be blocked in some corporate and educational network environments. For more information and ways to work around this issue, see the [Connect to IoT Hub](../articles/iot/iot-mqtt-connect-to-iot-hub.md#connect-to-iot-hub) section of [Communicate with an IoT hub using the MQTT protocol](../articles/iot/iot-mqtt-connect-to-iot-hub.md).
 
 [!INCLUDE [azure-cli-prepare-your-environment.md](~/reusable-content/azure-cli/azure-cli-prepare-your-environment-no-header.md)]
 
@@ -54,7 +54,7 @@ This quickstart uses two Java applications:
 
 You also need a _service connection string_ to enable the back-end application to connect to your IoT hub and retrieve the messages. The following command retrieves the service connection string for your IoT hub:
 
-**YourIoTHubName**: Replace this placeholder below with the name you chose for your IoT hub.
+**YourIoTHubName**: Replace this placeholder in the following command with the name you chose for your IoT hub.
 
 ```azurecli-interactive
 az iot hub connection-string show --policy-name service --hub-name {YourIoTHubName} --output table
@@ -90,7 +90,7 @@ The simulated device application connects to a device-specific endpoint on your
 
     The following screenshot shows the output as the simulated device application sends telemetry to your IoT hub:
 
-    ![Output from the telemetry sent by the device to your IoT hub](./media/quickstart-control-device-java/iot-hub-application-send-telemetry-output.png)
+    :::image type="content" source="./media/quickstart-control-device-java/iot-hub-application-send-telemetry-output.png" alt-text="Screenshot of a terminal window that shows the output of the simulated device application.":::
 
 ## Call the direct method
 
@@ -116,8 +116,9 @@ The back-end application connects to a service-side endpoint on your IoT Hub. Th
 
     The following screenshot shows the output as the application makes a direct method call to the device and receives an acknowledgment:
 
-    ![Output as the application makes a direct method call through your IoT hub](./media/quickstart-control-device-java/iot-hub-direct-method-call-output.png)
+    :::image type="content" source="./media/quickstart-control-device-java/iot-hub-direct-method-call-output.png" alt-text="Screenshot of a terminal window that shows the result of the direct method call from the service application.":::
+    
+    After you run the back-end application, you see a message in the local terminal window running the simulated device, and the rate at which it sends messages changes:
 
-    After you run the back-end application, you see a message in the console window running the simulated device, and the rate at which it sends messages changes:
-
-    ![Console message from device shows the rate at which it changes](./media/quickstart-control-device-java/iot-hub-sent-message-change-rate.png)
+    :::image type="content" source="./media/quickstart-control-device-java/iot-hub-sent-message-change-rate.png" alt-text="Screenshot of a terminal window that shows the direct message result and updated output from the simulated device application.":::
+