Merge pull request #289471 from tarTech23/legacy

prmerger-automator[bot] · web-flow · commit 5d2b9dcf9d05 · 2024-11-05T13:25:53.000Z
add deprecated to important
diff --git a/articles/defender-for-iot/organizations/integrations/on-premises-sentinel.md b/articles/defender-for-iot/organizations/integrations/on-premises-sentinel.md
@@ -12,6 +12,8 @@ ms.custom: template-how-to-pattern
 This article describes the legacy method for connecting your OT sensor or on-premises management console to Microsoft Sentinel. Stream data into Microsoft Sentinel whenever you want to use Microsoft Sentinel's advanced threat hunting, security analytics, and automation features when responding to security incidents and threats across your network.
 
 > [!IMPORTANT]
+> This feature will be deprecated in **January 2025**.
+>
 > If you're using a cloud connected sensor, we recommend that you connect Defender for IoT data using the Microsoft Sentinel solution instead of the legacy integration method. For more information, see:
 >
 > - [OT threat monitoring in enterprise SOCs](../concept-sentinel-integration.md)

Original file line number	Diff line number	Diff line change
`@@ -12,6 +12,8 @@ ms.custom: template-how-to-pattern`
`12`	`12`	`This article describes the legacy method for connecting your OT sensor or on-premises management console to Microsoft Sentinel. Stream data into Microsoft Sentinel whenever you want to use Microsoft Sentinel's advanced threat hunting, security analytics, and automation features when responding to security incidents and threats across your network.`
`13`	`13`
`14`	`14`	`> [!IMPORTANT]`
	`15`	`+> This feature will be deprecated in January 2025.`
	`16`	`+>`
`15`	`17`	`> If you're using a cloud connected sensor, we recommend that you connect Defender for IoT data using the Microsoft Sentinel solution instead of the legacy integration method. For more information, see:`
`16`	`18`	`>`
`17`	`19`	`> - [OT threat monitoring in enterprise SOCs](../concept-sentinel-integration.md)`