Microsoft Defender for IoT: OT security retirement

The operational technology (OT) security component of Microsoft Defender for IoT is fully deprecated at the retirement date, after a three-year transition period. The change applies only to Defender for IoT OT Security: Enterprise IoT capabilities in Microsoft Defender for Endpoint are not affected, and device discovery and vulnerability assessment continue to be available. During the transition the service stays supported with routine security updates and bug fixes, but it receives no new OT-specific capabilities or feature investments. Existing customer agreements and renewals are honored until the retirement date.

1. Review existing OT deployments, sensors, integrations, licenses, contracts, and security requirements.
2. Select an alternative OT security solution. Microsoft offers connectors for Armis, Dragos, and Forescout, and does not require a specific provider. See OT data connectors.
3. Plan separate licensing and deployment for any third-party solution.
4. Build a transition plan that covers procurement, testing, operational validation, continuity, data export, and sensor decommissioning, with migration completed before the retirement date.
5. Contact OT security providers directly, or ask the Microsoft account team to help coordinate an introduction.