Skip to content

Commit 0411ae0

Browse files
committed
Feedback
1 parent 0ab8c16 commit 0411ae0

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ The on-premises management console will be retired on **January 1, 2025** with t
2424

2525
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.
2626

27-
You can continue to manage air-gapped sensors using:
27+
If your organization enforces a policy where sensors can't access the internet (air-gapped), you can continue to manage sensors using:
2828
- [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.
2929
- [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

0 commit comments

Comments
 (0)