Skip to content

Commit 0ab8c16

Browse files
committed
Feedback
1 parent 3c6e993 commit 0ab8c16

File tree

2 files changed

+32
-35
lines changed

2 files changed

+32
-35
lines changed

articles/defender-for-iot/organizations/ot-deploy/on-premises-management-console-retirement.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -13,20 +13,20 @@ This article describes the retirement of the on-premises management console from
1313

1414
The on-premises management console will be retired on **January 1, 2025** with the following updates/changes:
1515

16-
- Sensor versions released after **January 1, 2025** won't be managed by an on-premises management console.
16+
- Sensor versions released after **January 1, 2025** won't connect to the on-premises management console.
1717
- For versions released prior to **January 1, 2025**:
1818
- You can still use the on-premises management console.
1919
- Defender for IoT no longer provides support service or maintains the on-premises management console.
2020

2121
For a list of supported versions, see [OT monitoring software versions](../release-notes.md)
2222

23-
- Following any version upgrade, you will no longer be able to use the on-premises management console. For example, if you're using the on-premises management console on version 24.1.2, and you upgrade to version 24.1.6, you can no longer use the on-premises management console.
24-
2523
## Air-gapped sensor support
2624

2725
Air-gapped sensor support isn't affected by the on-premises management console retirement. We continue to support air-gapped deployments and assist with the [transition to the cloud](transition-on-premises-management-console-to-cloud.md). The sensors retain a full user interface so that they can be used in "lights out" scenarios and continue to analyze and secure the network in the event of an outage.
2826

29-
Air-gapped sensors that can't connect to the cloud can be managed directly via the sensor console UI, CLI, or API.
27+
You can continue to manage air-gapped sensors using:
28+
- [The sensor console UI](../how-to-investigate-sensor-detections-in-a-device-inventory.md) or the [CLI](../cli-ot-sensor.md) to directly manage individual sensors.
29+
- [APIs](../references-work-with-defender-for-iot-apis.md) to send data to third-party management systems, such as a Security Information and Event Management (SIEM).
3030

3131
## Next steps
3232

articles/defender-for-iot/organizations/release-notes.md

Lines changed: 28 additions & 31 deletions
Original file line numberDiff line numberDiff line change
@@ -35,37 +35,34 @@ For more information, see [Update Defender for IoT OT monitoring software](updat
3535

3636
Cloud features may be dependent on a specific sensor version. Such features are listed below for the relevant software versions, and are only available for data coming from sensors that have the required version installed, or higher.
3737

38-
> [!NOTE]
39-
> The on-premises management console is being retired on **January 1, 2025**. The table below specifies whether each version includes the on-premises management console.
40-
> - For versions where the management console is specified as included, you can use the on-premises management console, but no support service or maintenance is available.
41-
> - For versions where the management console is specified as not included, you can't use or access the management console.
42-
>
43-
> For more information, see [On-premises management console retirement](ot-deploy/on-premises-management-console-retirement.md).
44-
45-
| Version / Patch | Release date | Scope | Supported until |Management console |
46-
| ------- | ------------ | ----------- | ------------------- | ------------------- |
47-
| **24.1** | | | | |
48-
| 24.1.7 |12/2024 | Minor |12/2025 |Included |
49-
| 24.1.6 |11/2024 | Minor |12/2025 |Included |
50-
| 24.1.5 |09/2024 | Minor |09/2025 |Included |
51-
| 24.1.4 |07/2024 | Minor |07/2025 |Included |
52-
| 24.1.3 |06/2024 | Minor |06/2025 |Included |
53-
| 24.1.2 |04/2024 | Minor |04/2025 |Included |
54-
| **23.2** | | | | |
55-
| 23.2.0 | 12/2023 | Major | 12/2024 |Included |
56-
| **23.1** | | | | |
57-
| 23.1.3 | 09/2023 | Patch | 08/2024 |Not included |
58-
| 23.1.2 | 07/2023 | Major | 06/2024 |Not included |
59-
| **22.3** | | | | |
60-
|22.3.10 | 07/2023 | Patch | 06/2024 |Not included |
61-
| 22.3.9 | 05/2023 | Patch | 04/2024 |Not included |
62-
| 22.3.8 | 04/2023 | Patch | 03/2024 |Not included |
63-
| 22.3.7 | 03/2023 | Patch | 02/2024 |Not included |
64-
| 22.3.6 | 03/2023 | Patch | 02/2024 |Not included |
65-
| 22.3.5 | 01/2023 | Patch | 12/2023 |Not included |
66-
| 22.3.4 | 01/2023 | Major | 12/2023 |Not included |
67-
| **22.2** | | | | |
68-
| 22.2.9 | 01/2023 | Patch | 12/2023 |Not included |
38+
> [!IMPORTANT]
39+
> The on-premises management console won't be supported or available for download after January 1st, 2025. For more information, see [On-premises management console retirement](on-premises-management-console-retirement.md).
40+
>
41+
42+
| Version / Patch | Release date | Scope | Supported until |
43+
| ------- | ------------ | ----------- | ------------------- |
44+
| **24.1** | | | |
45+
| 24.1.7 |12/2024 | Minor |12/2025 |
46+
| 24.1.6 |11/2024 | Minor |12/2025 |
47+
| 24.1.5 |09/2024 | Minor |09/2025 |
48+
| 24.1.4 |07/2024 | Minor |07/2025 |
49+
| 24.1.3 |06/2024 | Minor |06/2025 |
50+
| 24.1.2 |04/2024 | Minor |04/2025 |
51+
| **23.2** | | | |
52+
| 23.2.0 | 12/2023 | Major | 12/2024 |
53+
| **23.1** | | | |
54+
| 23.1.3 | 09/2023 | Patch | 08/2024 |
55+
| 23.1.2 | 07/2023 | Major | 06/2024 |
56+
| **22.3** | | | |
57+
|22.3.10 | 07/2023 | Patch | 06/2024 |
58+
| 22.3.9 | 05/2023 | Patch | 04/2024 |
59+
| 22.3.8 | 04/2023 | Patch | 03/2024 |
60+
| 22.3.7 | 03/2023 | Patch | 02/2024 |
61+
| 22.3.6 | 03/2023 | Patch | 02/2024 |
62+
| 22.3.5 | 01/2023 | Patch | 12/2023 |
63+
| 22.3.4 | 01/2023 | Major | 12/2023 |
64+
| **22.2** | | | |
65+
| 22.2.9 | 01/2023 | Patch | 12/2023 |
6966

7067
### Threat intelligence updates
7168

0 commit comments

Comments
 (0)