OT security in Microsoft Defender for IoT will be deprecated in October 2029

[What and Why:]

Microsoft is deprecating the operational technology (OT) security component of Microsoft Defender for IoT. Customers will have a three-year transition period to evaluate and migrate to an alternative OT security solution that meets their organization’s requirements, and the service will be fully deprecated in October 2029.

This change applies only to the OT Security component of Microsoft Defender for IoT. Enterprise IoT capabilities in Microsoft Defender for Endpoint are not affected, and device discovery and vulnerability assessment will continue to be available.

This notice begins the transition period and does not require you to immediately stop using your existing deployment. Complete your migration to an alternative OT security solution before retirement in October 2029.

[Rollout Schedule:]

General Availability (Worldwide): We will begin rolling out in late October 2026 and expect to complete by late October 2029.

[Impact on Your Organization:]

Who is affected:

• Organizations using the OT Security component of Microsoft Defender for IoT.

Platforms/Services:

• Microsoft Defender for IoT (OT Security)

What will happen:

• During the three-year transition period, the OT Security service will remain supported, including routine security updates and bug fixes, but no new OT-specific capabilities or feature investments will be introduced.
• Existing customer agreements and renewals will be honored through October 2029.
• Organizations will need to transition to an alternative OT security solution before the service is retired in October 2029.

[Action Required/Recommendations:]

Action is required to prepare for this retirement:

1. Assess your environment. Review your existing OT deployments, sensors, integrations, licenses, contracts, and security requirements.
2. Evaluate your options. Compare OT security solutions based on your industrial environments, protocols, coverage, deployment requirements, and security needs. Microsoft offers connectors for OT security solutions from Armis, Dragos, and Forescout, but you are not required to use a specific provider.
3. Understand Microsoft integrations. If you choose a supported provider and want to bring OT asset and vulnerability context into Microsoft Security Exposure Management and the Defender portal, review the available connector capabilities and integration requirements. Microsoft connectors complement third-party OT security solutions — they are not standalone OT security solutions, and third-party solutions require separate licensing and deployment.
4. Build your transition plan. Account for procurement, testing, maintenance windows, operational validation, continuity, data export, and sensor decommissioning, and plan to complete the transition before retirement in October 2029.
5. Engage early. Contact OT security providers directly or work with your Microsoft account team to coordinate an introduction.

Learn more:

• OT data connectors
• Enterprise IoT

[Compliance considerations:]

No compliance considerations identified. Review as appropriate for your organization.