Skip to content

Commit f765e68

Browse files
prmerger-automator[bot]prmerger-automator[bot]
authored
Merge pull request #277058 from PatAltimore/patricka-freshness
Freshness
2 parents 11e470b + 89f31fa commit f765e68

5 files changed

+28
-29
lines changed

‎articles/iot-edge/how-to-provision-devices-at-scale-linux-on-windows-tpm.md

Lines changed: 4 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,11 @@
11
---
2-
title: Create and provision an IoT Edge for Linux on Windows device by using a TPM - Azure IoT Edge | Microsoft Docs
2+
title: Create and provision an IoT Edge for Linux on Windows device by using a TPM
33
description: Use a simulated TPM on a Linux on Windows device to test the Azure device provisioning service for Azure IoT Edge.
44
author: PatAltimore
5-
manager: lizross
65
ms.author: patricka
76
ms.reviewer: fcabrera
8-
ms.date: 02/09/2022
9-
ms.topic: conceptual
7+
ms.date: 06/03/2024
8+
ms.topic: how-to
109
ms.service: iot-edge
1110
ms.custom: linux-related-content
1211
services: iot-edge
@@ -129,7 +128,7 @@ Simulated TPM samples:
129128
Provision-EflowVM -provisioningType "DpsTpm" -scopeId "SCOPE_ID_HERE"
130129
```
131130

132-
If you have enrolled the device using a custom **Registration Id**, you must specify that registration ID as well when provisioning:
131+
If you enrolled the device using a custom **Registration Id**, you must specify that registration ID as well when provisioning:
133132

134133
```powershell
135134
Provision-EflowVM -provisioningType "DpsTpm" -scopeId "SCOPE_ID_HERE" -registrationId "REGISTRATION_ID_HERE"

‎articles/iot-edge/how-to-provision-devices-at-scale-linux-on-windows-x509.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,10 @@
11
---
2-
title: Create and provision IoT Edge devices using X.509 certificates on Linux on Windows - Azure IoT Edge | Microsoft Docs
2+
title: Create and provision Azure IoT Edge devices using X.509 certificates on Linux on Windows
33
description: Use X.509 certificate attestation to test provisioning devices at scale for Azure IoT Edge with device provisioning service
44
author: PatAltimore
55
ms.author: patricka
6-
ms.date: 11/15/2022
7-
ms.topic: conceptual
6+
ms.date: 06/03/2024
7+
ms.topic: how-to
88
ms.service: iot-edge
99
ms.custom: linux-related-content
1010
services: iot-edge
@@ -58,7 +58,7 @@ To create test certificates, follow the steps in [Create demo certificates to te
5858
* `<WRKDIR>\certs\iot-edge-device-identity-<name>-full-chain.cert.pem`
5959
* `<WRKDIR>\private\iot-edge-device-identity-<name>.key.pem`
6060

61-
You need both these certificates on the IoT Edge device. If you're going to use individual enrollment in DPS, then you will upload the .cert.pem file. If you're going to use group enrollment in DPS, then you also need an intermediate or root CA certificate in the same certificate chain of trust to upload. If you're using demo certs, use the `<WRKDIR>\certs\azure-iot-test-only.root.ca.cert.pem` certificate for group enrollment.
61+
You need both these certificates on the IoT Edge device. If you're going to use individual enrollment in DPS, then you upload the .cert.pem file. If you're going to use group enrollment in DPS, then you also need an intermediate or root CA certificate in the same certificate chain of trust to upload. If you're using demo certs, use the `<WRKDIR>\certs\azure-iot-test-only.root.ca.cert.pem` certificate for group enrollment.
6262

6363
<!-- Create a DPS enrollment using X.509 certificates H2 and content -->
6464
[!INCLUDE [iot-edge-create-dps-enrollment-x509.md](includes/iot-edge-create-dps-enrollment-x509.md)]
@@ -96,7 +96,7 @@ You can verify that the group enrollment that you created in device provisioning
9696

9797
---
9898

99-
1. Log in to your IoT Edge for Linux on Windows virtual machine using the following command in your PowerShell session:
99+
1. Sign in to your IoT Edge for Linux on Windows virtual machine using the following command in your PowerShell session:
100100

101101
```powershell
102102
Connect-EflowVm
@@ -134,7 +134,7 @@ You can verify that the group enrollment that you created in device provisioning
134134
>
135135
>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.
136136

137-
When you create a new IoT Edge device, it will display the status code `417 -- The device's deployment configuration is not set` in the Azure portal. This status is normal, and means that the device is ready to receive a module deployment.
137+
When you create a new IoT Edge device, it displays the status code `417 -- The device's deployment configuration is not set` in the Azure portal. This status is normal, and means that the device is ready to receive a module deployment.
138138
139139
<!-- Uninstall IoT Edge for Linux on Windows H2 and content -->
140140
[!INCLUDE [uninstall-iot-edge-linux-on-windows.md](includes/iot-edge-uninstall-linux-on-windows.md)]

‎articles/iot-edge/how-to-provision-single-device-linux-on-windows-symmetric.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,12 @@
11
---
2-
title: Create and provision an IoT Edge for Linux on Windows device using symmetric keys - Azure IoT Edge | Microsoft Docs
2+
title: Create and provision an Azure IoT Edge for Linux on Windows device using symmetric keys
33
description: Create and provision a single IoT Edge for Linux on Windows device in IoT Hub using manual provisioning with symmetric keys
44
author: PatAltimore
55
ms.service: iot-edge
66
ms.custom: linux-related-content
77
services: iot-edge
8-
ms.topic: conceptual
9-
ms.date: 11/15/2022
8+
ms.topic: how-to
9+
ms.date: 06/03/2024
1010
ms.author: patricka
1111
---
1212

@@ -57,7 +57,7 @@ This article covers registering your IoT Edge device and installing IoT Edge for
5757

5858
You're ready to set up your device with its cloud identity and authentication information.
5959

60-
To provision your device using symmetric keys, you will need your device's **connection string**.
60+
To provision your device using symmetric keys, you need your device's **connection string**.
6161

6262
Run the following command in an elevated PowerShell session on your target device. Replace the placeholder text with your own values.
6363

@@ -71,7 +71,7 @@ For more information about the `Provision-EflowVM` command, see [PowerShell func
7171

7272
Verify that IoT Edge for Linux on Windows was successfully installed and configured on your IoT Edge device.
7373

74-
1. Log in to your IoT Edge for Linux on Windows virtual machine using the following command in your PowerShell session:
74+
1. Sign in to your IoT Edge for Linux on Windows virtual machine using the following command in your PowerShell session:
7575

7676
```powershell
7777
Connect-EflowVm
@@ -110,7 +110,7 @@ Verify that IoT Edge for Linux on Windows was successfully installed and configu
110110
>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.
111111

112112

113-
When you create a new IoT Edge device, it will display the status code `417 -- The device's deployment configuration is not set` in the Azure portal. This status is normal, and means that the device is ready to receive a module deployment.
113+
When you create a new IoT Edge device, it displays the status code `417 -- The device's deployment configuration is not set` in the Azure portal. This status is normal, and means that the device is ready to receive a module deployment.
114114
115115
<!-- Uninstall IoT Edge for Linux on Windows H2 and content -->
116116
[!INCLUDE [uninstall-iot-edge-linux-on-windows.md](includes/iot-edge-uninstall-linux-on-windows.md)]

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

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,12 @@
11
---
2-
title: Create and provision an IoT Edge for Linux on Windows device using X.509 certificates - Azure IoT Edge | Microsoft Docs
2+
title: Create and provision an Azure IoT Edge for Linux on Windows device using X.509 certificates
33
description: Create and provision a single IoT Edge for Linux on Windows device in IoT Hub using manual provisioning with X.509 certificates
44
author: PatAltimore
55
ms.service: iot-edge
66
ms.custom: linux-related-content
77
services: iot-edge
8-
ms.topic: conceptual
9-
ms.date: 02/09/2022
8+
ms.topic: how-to
9+
ms.date: 06/03/2024
1010
ms.author: patricka
1111
---
1212

@@ -61,7 +61,7 @@ This article covers registering your IoT Edge device and installing IoT Edge for
6161

6262
You're ready to set up your device with its cloud identity and authentication information.
6363

64-
To provision your device using X.509 certificates, you will need your **IoT hub name**, **device ID**, and the absolute paths to your **identity certificate** and **private key** on your Windows host machine.
64+
To provision your device using X.509 certificates, you need your **IoT hub name**, **device ID**, and the absolute paths to your **identity certificate** and **private key** on your Windows host machine.
6565

6666
Have the device identity certificate and its matching private key ready on your target device. Know the absolute path to both files.
6767

@@ -77,7 +77,7 @@ For more information about the `Provision-EflowVM` command, see [PowerShell func
7777

7878
Verify that IoT Edge for Linux on Windows was successfully installed and configured on your IoT Edge device.
7979

80-
1. Log in to your IoT Edge for Linux on Windows virtual machine using the following command in your PowerShell session:
80+
1. Sign in to your IoT Edge for Linux on Windows virtual machine using the following command in your PowerShell session:
8181

8282
```powershell
8383
Connect-EflowVm
@@ -115,7 +115,7 @@ Verify that IoT Edge for Linux on Windows was successfully installed and configu
115115
>
116116
>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.
117117

118-
When you create a new IoT Edge device, it will display the status code `417 -- The device's deployment configuration is not set` in the Azure portal. This status is normal, and means that the device is ready to receive a module deployment.
118+
When you create a new IoT Edge device, it displays the status code `417 -- The device's deployment configuration is not set` in the Azure portal. This status is normal, and means that the device is ready to receive a module deployment.
119119
120120
<!-- Uninstall IoT Edge for Linux on Windows H2 and content -->
121121
[!INCLUDE [uninstall-iot-edge-linux-on-windows.md](includes/iot-edge-uninstall-linux-on-windows.md)]

‎articles/iot-edge/how-to-retrieve-iot-edge-logs.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,11 @@
11
---
2-
title: Retrieve IoT Edge logs - Azure IoT Edge
2+
title: Retrieve Azure IoT Edge logs
33
description: IoT Edge module log retrieval and upload to Azure Blob Storage.
44
author: PatAltimore
55

66
ms.author: patricka
7-
ms.date: 09/01/2022
8-
ms.topic: conceptual
7+
ms.date: 06/03/2024
8+
ms.topic: how-to
99
ms.reviewer: veyalla
1010
ms.service: iot-edge
1111
ms.custom: devx-track-azurecli
@@ -29,7 +29,7 @@ While not required, for best compatibility with this feature, the recommended lo
2929
<{Log Level}> {Timestamp} {Message Text}
3030
```
3131

32-
`{Timestamp}` should be formatted as `yyyy-MM-dd HH:mm:ss.fff zzz`, and `{Log Level}` should follow the table below, which derives its severity levels from the [Severity code in the Syslog standard](https://wikipedia.org/wiki/Syslog#Severity_level).
32+
`{Timestamp}` should be formatted as `yyyy-MM-dd HH:mm:ss.fff zzz`, and `{Log Level}` should use the following table, which derives its severity levels from the [Severity code in the Syslog standard](https://wikipedia.org/wiki/Syslog#Severity_level).
3333

3434
| Value | Severity |
3535
|-|-|
@@ -79,7 +79,7 @@ This method accepts a JSON payload with the following schema:
7979
|-|-|-|
8080
| schemaVersion | string | Set to `1.0` |
8181
| items | JSON array | An array with `id` and `filter` tuples. |
82-
| id | string | A regular expression that supplies the module name. It can match multiple modules on an edge device. [.NET Regular Expressions](/dotnet/standard/base-types/regular-expressions) format is expected. In case there are multiple items whose ID matches the same module, only the filter options of the first matching ID will be applied to that module. |
82+
| id | string | A regular expression that supplies the module name. It can match multiple modules on an edge device. [.NET Regular Expressions](/dotnet/standard/base-types/regular-expressions) format is expected. In case there are multiple items whose ID matches the same module, only the filter options of the first matching ID is applied to that module. |
8383
| filter | JSON section | Log filters to apply to the modules matching the `id` regular expression in the tuple. |
8484
| tail | integer | Number of log lines in the past to retrieve starting from the latest. OPTIONAL. |
8585
| since | string | Only return logs since this time, as an rfc3339 timestamp, UNIX timestamp, or a duration (days (d) hours (h) minutes (m)). For example, a duration for one day, 12 hours, and 30 minutes can be specified as *1 day 12 hours 30 minutes* or *1d 12h 30m*. If both `tail` and `since` are specified, the logs are retrieved using the `since` value first. Then, the `tail` value is applied to the result, and the final result is returned. OPTIONAL. |
@@ -399,7 +399,7 @@ In the Azure portal, invoke the method with the method name `GetTaskStatus` and
399399
}
400400
```
401401

402-
:::image type="content" source="./media/how-to-retrieve-iot-edge-logs/invoke-get-task-status.png" alt-text="Screenshot showing how to invoke direct method GetTaskStatus in Azure portal .":::
402+
:::image type="content" source="./media/how-to-retrieve-iot-edge-logs/invoke-get-task-status.png" alt-text="Screenshot showing how to invoke direct method GetTaskStatus in Azure portal.":::
403403

404404
## Next steps
405405

0 commit comments

Comments
 (0)