Skip to content

Commit e24c3bd

Browse files
Merge pull request #247090 from arielsaghiv/patch-145
Update how-to-manage-individual-sensors.md
2 parents 5aab181 + 44ef08c commit e24c3bd

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

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

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -107,6 +107,10 @@ You'll receive an error message if the activation file couldn't be uploaded. The
107107

108108
- **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.
109109

110+
> [!NOTE]
111+
> Activation files are valid for 14 days after creation. New activation files must be created if yours are expired.
112+
>
113+
110114
## Manage SSL/TLS certificates
111115

112116
If you're working with a production environment, you'd deployed a CA-signed SSL/TLS certificate as part of your [OT sensor deployment](ot-deploy/activate-deploy-sensor.md#define-ssltls-certificate-settings). We recommend using self-signed certificates only for testing purposes.

0 commit comments

Comments
 (0)