From bfe3151cc18f4b0cac6afa6e53ccc9ee0349b9f3 Mon Sep 17 00:00:00 2001 From: Aubeauch <56983326+Aubeauch@users.noreply.github.com> Date: Mon, 6 Apr 2026 17:31:43 -0700 Subject: [PATCH 1/2] Update deprecation management document with warning Added warning about deprecated Microsoft Sentinel solutions. --- articles/sentinel/sentinel-solution-deprecation.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/articles/sentinel/sentinel-solution-deprecation.md b/articles/sentinel/sentinel-solution-deprecation.md index 95a6e58d4b522..f4291e4b1f5fb 100644 --- a/articles/sentinel/sentinel-solution-deprecation.md +++ b/articles/sentinel/sentinel-solution-deprecation.md @@ -14,6 +14,9 @@ ms.date: 12/30/2024 The document explains how to manage the lifecycle of out-of-the-box solutions in Microsoft Sentinel that the solution author no longer supports. This document explains how to identify the solutions that are marked for deprecation and what actions to take on those solutions. +> [!Warning] +> Microsoft Sentinel solutions that are deprecated are no longer supported by Microsoft. They do not receive updates or bug fixes, and functionality or reliability may degrade over time. Continued use should be carefully evaluated, and migration to a supported alternative is recommended. + ## Reasons for solution deprecation Here are some of the primary reasons why Solutions are sometimes deprecated in Microsoft Sentinel: - The software service provider stopped supporting the product or service that sends data to Microsoft Sentinel. @@ -42,4 +45,4 @@ Solutions that are marked as deprecated can be identified using the **DEPRECATED ## Related content -[Discover and manage Microsoft Sentinel out-of-the-box content](/azure/sentinel/sentinel-solutions-deploy?tabs=azure-portal#discover-content) \ No newline at end of file +[Discover and manage Microsoft Sentinel out-of-the-box content](/azure/sentinel/sentinel-solutions-deploy?tabs=azure-portal#discover-content) From ac6dd4e035864ed4e39bb9d1735f9549bbbfa4e8 Mon Sep 17 00:00:00 2001 From: Aubeauch <56983326+Aubeauch@users.noreply.github.com> Date: Tue, 7 Apr 2026 08:20:34 -0700 Subject: [PATCH 2/2] Update articles/sentinel/sentinel-solution-deprecation.md Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> --- articles/sentinel/sentinel-solution-deprecation.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/articles/sentinel/sentinel-solution-deprecation.md b/articles/sentinel/sentinel-solution-deprecation.md index f4291e4b1f5fb..9891695902747 100644 --- a/articles/sentinel/sentinel-solution-deprecation.md +++ b/articles/sentinel/sentinel-solution-deprecation.md @@ -15,7 +15,7 @@ ms.date: 12/30/2024 The document explains how to manage the lifecycle of out-of-the-box solutions in Microsoft Sentinel that the solution author no longer supports. This document explains how to identify the solutions that are marked for deprecation and what actions to take on those solutions. > [!Warning] -> Microsoft Sentinel solutions that are deprecated are no longer supported by Microsoft. They do not receive updates or bug fixes, and functionality or reliability may degrade over time. Continued use should be carefully evaluated, and migration to a supported alternative is recommended. +> Microsoft Sentinel solutions that are deprecated are no longer supported by Microsoft. They do not receive updates or bug fixes, and functionality or reliability may degrade over time. Continued use should be carefully evaluated, and migration to a supported alternative is recommended. For recommended next steps, see [Actions to take on solutions that are marked as deprecated](#actions-to-take-on-solutions-that-are-marked-as-deprecated). ## Reasons for solution deprecation Here are some of the primary reasons why Solutions are sometimes deprecated in Microsoft Sentinel: