Skip to content

Commit 332f665

Browse files
committed
removing outdated info
1 parent 85fc5ab commit 332f665

File tree

1 file changed

+3
-9
lines changed

1 file changed

+3
-9
lines changed

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

Lines changed: 3 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -73,11 +73,7 @@ For more information about when and how to use a new file, see [Upload new activ
7373

7474
### Upload new activation files
7575

76-
You might need to upload a new activation file for an onboarded sensor when:
77-
78-
- You want to work in a different sensor management mode.
79-
80-
- For sensors connected via an IoT Hub ([legacy](architecture-connections.md)), you want to assign a new Defender for IoT hub to a cloud-connected sensor.
76+
You might need to upload a new activation file for an onboarded sensor when you want to work in a different sensor management mode.
8177

8278
**To add a new activation file:**
8379

@@ -109,13 +105,11 @@ You might need to upload a new activation file for an onboarded sensor when:
109105

110106
You'll receive an error message if the activation file couldn't be uploaded. The following events might have occurred:
111107

112-
- **For locally connected sensors**: The activation file isn't valid. If the file isn't valid, go to [Defender for IoT in the Azure portal](https://portal.azure.com/#blade/Microsoft_Azure_IoT_Defender/IoTDefenderDashboard/Getting_Started). On the **Sensor Management** page, select the sensor with the invalid file, and download a new activation file.
113-
114-
- **For cloud-connected sensors**: The sensor can't connect to the internet. Check the sensor's network configuration. If your sensor needs to connect through a web proxy to access the internet, verify that your proxy server is configured correctly on the **Sensor Network Configuration** screen. Verify that the required endpoints are allowed in the firewall and/or proxy.
108+
- **The sensor can't connect to the internet:** Check the sensor's network configuration. If your sensor needs to connect through a web proxy to access the internet, verify that your proxy server is configured correctly on the **Sensor Network Configuration** screen. Verify that the required endpoints are allowed in the firewall and/or proxy.
115109

116110
For OT sensors version 22.x, download the list of required endpoints from the **Sites and sensors** page on the Azure portal. Select an OT sensor with a supported software version, or a site with one or more supported sensors. And then select **More actions** > **Download endpoint details**. For sensors with earlier versions, see [Sensor access to Azure portal](how-to-set-up-your-network.md#sensor-access-to-azure-portal).
117111

118-
- **For cloud-connected sensors**: 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.
112+
- **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.
119113

120114
## Manage certificates
121115

0 commit comments

Comments
 (0)