You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/defender-for-iot/organizations/ot-deploy/air-gapped-deploy.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -99,10 +99,10 @@ If you're an existing customer using an on-premises management console to manage
99
99
100
100
The on-premises management console retirement includes the following details:
101
101
102
-
- Sensor versions released after **January 1, 2025** won't be able to be managed by an on-premises management console.
103
102
- Sensor software versions released between **January 1st, 2024 – January 1st, 2025** will continue to support an on-premises management console release.
103
+
- Sensor versions released after **January 1, 2025** won't be able to be managed by an on-premises management console.
104
104
- Air-gapped sensors that cannot connect to the cloud can be managed directly via the sensor console, CLI, or API.
105
-
- Air-gapped sensor support isn't affected by the changes to on-premises management console support.
105
+
- Air-gapped sensor support isn't affected by the changes to on-premises management console support. We continue to support air-gapped deployments and assist with the transition to the cloud.
106
106
107
107
For more information, see [OT monitoring software versions](../release-notes.md).
0 commit comments