Merge pull request #299956 from DENKEN02MSFT/Top50_patricka_Row31

Top50 - row 31

Author: prmerger-automator[bot]

articles/iot-edge/how-to-provision-single-device-linux-x509.md

@@ -7,7 +7,7 @@ ms.service: azure-iot-edge
 ms.custom: linux-related-content
 services: iot-edge
 ms.topic: how-to
-ms.date: 06/13/2024
+ms.date: 05/15/2025
 ms.author: patricka
 ---
 
@@ -32,11 +32,11 @@ The steps in this article walk through a process called manual provisioning, whe
 This article covers using X.509 certificates as your authentication method. If you want to use symmetric keys, see [Create and provision an IoT Edge device on Linux using symmetric keys](how-to-provision-single-device-linux-symmetric.md).
 
 > [!NOTE]
-> If you have many devices to set up and don't want to manually provision each one, use one of the following articles to learn how IoT Edge works with the IoT Hub device provisioning service:
+> If you have many devices to set up and don't want to manually provision each one, use one of the following articles to learn how IoT Edge works with the IoT Hub Device Provisioning Service:
 >
-> * [Create and provision IoT Edge devices at scale using X.509 certificates](how-to-provision-devices-at-scale-linux-x509.md)
-> * [Create and provision IoT Edge devices at scale with a TPM](how-to-provision-devices-at-scale-linux-tpm.md)
-> * [Create and provision IoT Edge devices at scale using symmetric keys](how-to-provision-devices-at-scale-linux-symmetric.md)
+> * [Create and provision IoT Edge devices at scale on Linux using X.509 certificates](how-to-provision-devices-at-scale-linux-x509.md)
+> * [Create and provision IoT Edge devices at scale with a TPM on Linux](how-to-provision-devices-at-scale-linux-tpm.md)
+> * [Create and provision IoT Edge devices at scale on Linux using symmetric keys](how-to-provision-devices-at-scale-linux-symmetric.md)
 
 ## Prerequisites
 
@@ -63,7 +63,7 @@ Now that the container engine and the IoT Edge runtime are installed on your dev
 
 # [Ubuntu / Debian / RHEL](#tab/ubuntu+debian+rhel)
 
-1. Create the configuration file for your device based on a template file that's provided as part of the IoT Edge installation.
+1. Create the configuration file for your device based on a template file provided as part of the IoT Edge installation.
 
     ```bash
     sudo cp /etc/aziot/config.toml.edge.template /etc/aziot/config.toml
@@ -94,7 +94,7 @@ Now that the container engine and the IoT Edge runtime are installed on your dev
 
 Update the following fields:
 
-* **iothub_hostname**: Hostname of the IoT Hub the device connects to. For example, `{IoT hub name}.azure-devices.net`.
+* **iothub_hostname**: Hostname of the IoT hub the device connects to. For example, `{IoT hub name}.azure-devices.net`.
 * **device_id**: The ID that you provided when you registered the device.
 * **identity_cert**: URI to an identity certificate on the device, for example: `file:///path/identity_certificate.pem`. Or, dynamically issue the certificate using EST or a local certificate authority.
 * **identity_pk**: URI to the private key file for the provided identity certificate, for example: `file:///path/identity_key.pem`. Or, provide a PKCS#11 URI and then provide your configuration information in the 
@@ -140,7 +140,7 @@ After entering the provisioning information in the configuration file, apply you
 
     Update the following fields:
 
-    * **iothub_hostname**: Hostname of the IoT Hub where the device connects. For example, `example.azure-devices.net`.
+    * **iothub_hostname**: Hostname of the IoT hub where the device connects. For example, `example.azure-devices.net`.
     * **device_id**: The ID that you provided when you registered the device.
     * **identity_cert**: URI to an identity certificate on the device, for example: `file:///var/snap/azure-iot-identity/current/shared/identity_certificate.pem`.
     * **identity_pk**: URI to the private key file for the provided identity certificate, for example: `file:///var/snap/azure-iot-identity/current/shared/identity_key.pem`.
@@ -163,7 +163,7 @@ After entering the provisioning information in the configuration file, apply you
 
 To deploy your IoT Edge modules, go to your IoT hub in the Azure portal, then:
 
-1. Select **Devices** from the IoT Hub menu.
+1. Select **Devices**, under **Device management**, from the resource menu.
 
 1. Select your device to open its page.
 
@@ -203,23 +203,23 @@ Use the `check` tool to verify configuration and connection status of the device
 sudo iotedge check
 ```
 
-You can expect a range of responses that may include **OK** (green), **Warning** (yellow), or **Error** (red). For troubleshooting common errors, see [Solutions to common issues for Azure IoT Edge](troubleshoot-common-errors.md).
+You can expect a range of responses that might include **OK** (green), **Warning** (yellow), or **Error** (red). For troubleshooting common errors, see [Solutions to common issues for Azure IoT Edge](troubleshoot-common-errors.md).
 
 :::image type="content" source="media/how-to-provision-single-device-linux-x509/config-checks.png" alt-text="Screenshot of sample responses from the check command." lightbox="media/how-to-provision-single-device-linux-x509/config-checks.png":::
 
 >[!TIP]
 >Always use `sudo` to run the check tool, even after your permissions are updated. The tool needs elevated privileges to access the config file to verify configuration status.
 
 >[!NOTE]
->On a newly provisioned device, you may see an error related to IoT Edge Hub:
+>On a newly provisioned device, you might see an error related to IoT Edge Hub:
 >
 >**× production readiness: Edge Hub's storage directory is persisted on the host filesystem - Error**
 >
 >**Could not check current state of edgeHub container**
 >
 >This error is expected on a newly provisioned device because the IoT Edge Hub module isn't running. To resolve the error, in IoT Hub, set the modules for the device and create a deployment. Creating a deployment for the device starts the modules on the device including the IoT Edge Hub module.
 
-View all the modules running on your IoT Edge device. When the service starts for the first time, you should only see the **edgeAgent** module running. The edgeAgent module runs by default and helps to install and start any additional modules that you deploy to your device.
+View all the modules running on your IoT Edge device. When the service starts for the first time, you should only see the **edgeAgent** module running. The edgeAgent module runs by default and helps to install and start any other modules that you deploy to your device.
 
    ```bash
    sudo iotedge list
@@ -229,12 +229,12 @@ When you create a new IoT Edge device, it displays the status code `417 -- The d
 
 ## Offline or specific version installation (optional)
 
-The steps in this section are for scenarios not covered by the standard installation steps. This may include:
+The steps in this section are for scenarios not covered by the standard installation steps. These scenarios might include:
 
 * Install IoT Edge while offline
 * Install a release candidate version
 
-Use the steps in this section if you want to install a specific version of the Azure IoT Edge runtime that isn't available through your package manager. The Microsoft package list only contains a limited set of recent versions and their sub-versions, so these steps are for anyone who wants to install an older version or a release candidate version.
+Use the steps in this section if you want to install a specific version of the Azure IoT Edge runtime that isn't available through your package manager. The Microsoft package list only contains a limited set of recent versions and their subversions, so these steps are for anyone who wants to install an older version or a release candidate version.
 
 If you're using Ubuntu snaps, you can download a snap and install it offline. For more information, see [Download snaps and install offline](https://forum.snapcraft.io/t/download-snaps-and-install-offline/15713).
 
@@ -248,7 +248,7 @@ Using curl commands, you can target the component files directly from the IoT Ed
 
    1. Find the **aziot-identity-service** file that matches your IoT Edge device's architecture. Right-click on the file link and copy the link address.
 
-   2. Use the copied link in the following command to install that version of the identity service:
+   2. To install that version of the identity service, use the copied link in the following command:
 
       # [Ubuntu / Debian](#tab/ubuntu+debian)
       ```bash

articles/iot-edge/includes/iot-edge-generate-device-identity-certs.md

@@ -1,6 +1,6 @@
 ---
 ms.topic: include
-ms.date: 01/04/2024
+ms.date: 05/15/2025
 author: PatAltimore
 ms.author: patricka
 ms.service: azure-iot-edge
@@ -11,7 +11,7 @@ services: iot-edge
 
 Manual provisioning with X.509 certificates requires IoT Edge version 1.0.10 or newer.
 
-When you provision an IoT Edge device with X.509 certificates, you use what's called a *device identity certificate*. This certificate is only used for provisioning an IoT Edge device and authenticating the device with Azure IoT Hub. It's a leaf certificate that doesn't sign other certificates. The device identity certificate is separate from the certificate authority (CA) certificates that the IoT Edge device presents to modules or downstream devices for verification.
+When you provision an IoT Edge device with X.509 certificates, you use a *device identity certificate*. This certificate is only used for provisioning an IoT Edge device and authenticating the device with Azure IoT Hub. It's a leaf certificate that doesn't sign other certificates. The device identity certificate is separate from the certificate authority (CA) certificates that the IoT Edge device presents to modules or downstream devices for verification.
 
 For X.509 certificate authentication, each device's authentication information is provided in the form of *thumbprints* taken from your device identity certificates. These thumbprints are given to IoT Hub at the time of device registration so that the service can recognize the device when it connects.
 
@@ -39,4 +39,4 @@ You need the following files for manual provisioning with X.509:
     SHA1 Fingerprint=D2:68:D9:04:9F:1A:4D:6A:FD:84:77:68:7B:C6:33:C0:32:37:51:12
     ```
 
-If you don't have certificates available, you can [Create demo certificates to test IoT Edge device features](../how-to-create-test-certificates.md). Follow the instructions in that article to set up certificate creation scripts, create a root CA certificate, and create a IoT Edge device identity certificate. For testing, you can create a single device identity certificate and use the same thumbprint for both primary and secondary thumbprint values when registering the device in IoT Hub.
+If you don't have certificates available, you can [Create demo certificates to test IoT Edge device features](../how-to-create-test-certificates.md). Follow the instructions in that article to set up certificate creation scripts, create a root CA certificate, and create an IoT Edge device identity certificate. For testing, you can create a single device identity certificate and use the same thumbprint for both primary and secondary thumbprint values when registering the device in IoT Hub.

articles/iot-edge/includes/iot-edge-register-device-x509.md

@@ -1,6 +1,6 @@
 ---
 ms.topic: include
-ms.date: 07/18/2023
+ms.date: 05/15/2025
 author: PatAltimore
 ms.author: patricka
 ms.service: azure-iot-edge
@@ -17,7 +17,7 @@ In your IoT hub in the Azure portal, IoT Edge devices are created and managed se
 
 1. Sign in to the [Azure portal](https://portal.azure.com) and navigate to your IoT hub.
 
-1. In the left pane, select **Devices** from the menu, then select **Add Device**.
+1. In the resource menu, expand the **Device management** group and select **Devices**, then select **Add Device** from the command bar.
 
 1. On the **Create a device** page, provide the following information:
 
@@ -27,7 +27,7 @@ In your IoT hub in the Azure portal, IoT Edge devices are created and managed se
    * Provide the primary and secondary identity certificate thumbprints. Thumbprint values are 40-hex characters for SHA-1 hashes or 64-hex characters for SHA-256 hashes. The Azure portal supports hexadecimal values only. Remove column separators and spaces from the thumbprint values before entering them in the portal. For example, `D2:68:D9:04:9F:1A:4D:6A:FD:84:77:68:7B:C6:33:C0:32:37:51:12` is entered as `D268D9049F1A4D6AFD8477687BC633C032375112`.
 
    > [!TIP]
-   > If you are testing and want to use one certificate, you can use the same certificate for both the primary and secondary thumbprints.
+   > If you're testing and want to use one certificate, you can use the same certificate for both the primary and secondary thumbprints.
 
 1. Select **Save**.
 
@@ -61,7 +61,7 @@ Devices that use X.509 certificate authentication need their IoT hub name, their
 
 # [Portal](#tab/azure-portal)
 
-The edge-enabled devices that connect to your IoT hub are listed on the **Devices** page. You can filter the list by device type *IoT Edge devices*.
+The edge-enabled devices that connect to your IoT hub are listed on the **Devices** page. You can filter the list by the device type, *IoT Edge devices*.
 
 # [Visual Studio Code](#tab/visual-studio-code)
 
@@ -77,6 +77,6 @@ Use the [az iot hub device-identity list](/cli/azure/iot/hub/device-identity) co
    az iot hub device-identity list --hub-name <hub_name_here>
    ```
 
-Any device that's registered as an IoT Edge device has the property **capabilities.iotEdge** set to **true**.
+Any device registered as an IoT Edge device has the property **capabilities.iotEdge** set to **true**.
 
 ---