Skip to content

Commit ad447d1

Browse files
Merge pull request #247230 from batamig/activation-file-expiration
D4IoT activation file expiration
2 parents a4e2192 + e9dfdf7 commit ad447d1

File tree

2 files changed

+12
-5
lines changed

2 files changed

+12
-5
lines changed

articles/defender-for-iot/organizations/how-to-manage-individual-sensors.md

Lines changed: 8 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -83,11 +83,15 @@ You need to upload a new activation file to your sensor if you want to switch se
8383

8484
**To add a new activation file:**
8585

86-
1. In [Defender for IoT on the Azure portal](https://portal.azure.com/#blade/Microsoft_Azure_IoT_Defender/IoTDefenderDashboard/Getting_Started) > **Sites and sensors**, locate and [delete](how-to-manage-sensors-on-the-cloud.md#sensor-maintenance-and-troubleshooting) your OT sensor.
86+
1. Do one of the following:
8787

88-
1. Select **Onboard OT sensor > OT** to onboard the sensor again from scratch and download the new activation file. For more information, see [Onboard OT sensors](onboard-sensors.md).
88+
- **Onboard your sensor from scratch**:
89+
90+
1. In [Defender for IoT on the Azure portal](https://portal.azure.com/#blade/Microsoft_Azure_IoT_Defender/IoTDefenderDashboard/Getting_Started) > **Sites and sensors**, locate and [delete](how-to-manage-sensors-on-the-cloud.md#sensor-maintenance-and-troubleshooting) your OT sensor.
8991

90-
Alternately, on the **Sites and sensors** page, locate the sensor you just added. Select the three dots (...) on the sensor's row and select **Download activation file**. Save the file in a location accessible to your sensor.
92+
1. Select **Onboard OT sensor > OT** to onboard the sensor again from scratch and download the new activation file. For more information, see [Onboard OT sensors](onboard-sensors.md).
93+
94+
- <a name="current"></a>**Download the current sensor's activation file**: On the **Sites and sensors** page, locate the sensor you just added. Select the three dots (...) on the sensor's row and select **Download activation file**. Save the file in a location accessible to your sensor.
9195

9296
[!INCLUDE [root-of-trust](includes/root-of-trust.md)]
9397

@@ -108,7 +112,7 @@ You'll receive an error message if the activation file couldn't be uploaded. The
108112
- **The activation file is valid but Defender for IoT rejected it:** If you can't resolve this problem, you can download another activation from the **Sites and sensors** page in the [Azure portal](https://portal.azure.com/#blade/Microsoft_Azure_IoT_Defender/IoTDefenderDashboard/Getting_Started). If this doesn't work, contact Microsoft Support.
109113

110114
> [!NOTE]
111-
> Activation files are valid for 14 days after creation. New activation files must be created if yours are expired.
115+
> Activation files expire 14 days after creation. If you onboarded your sensor but didn't upload the activation file before it expired, [download a new activation file](#current).
112116
>
113117
114118
## Manage SSL/TLS certificates

articles/defender-for-iot/organizations/ot-deploy/activate-deploy-sensor.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -24,11 +24,14 @@ To perform the procedures in this article, you need:
2424

2525
- An OT sensor [onboarded](../onboard-sensors.md) to Defender for IoT in the Azure portal.
2626

27+
- OT sensor software installed on your appliance. Make sure that you've either [installed](install-software-ot-sensor.md) the software yourself or [purchased](../ot-pre-configured-appliances.md) a preconfigured appliance.
28+
2729
- The sensor's activation file, which was downloaded after [onboarding your sensor](../onboard-sensors.md). You need a unique activation file for each OT sensor you deploy.
2830

2931
[!INCLUDE [root-of-trust](../includes/root-of-trust.md)]
3032

31-
- OT sensor software installed on your appliance. Make sure that you've either [installed](install-software-ot-sensor.md) the software yourself or [purchased](../ot-pre-configured-appliances.md) a preconfigured appliance.
33+
> [!NOTE]
34+
> Activation files expire 14 days after creation. If you onboarded your sensor but didn't upload the activation file before it expired, [download a new activation file](../how-to-manage-individual-sensors.md#current).
3235
3336
- A SSL/TLS certificate. We recommend using a CA-signed certificate, and not a self-signed certificate. For more information, see [Create SSL/TLS certificates for OT appliances](create-ssl-certificates.md).
3437

0 commit comments

Comments
 (0)