Merge Incident Cases Manually
In brief
The article no longer describes incident cases or the legacy experience as being in preview. It also adds an authoring metadata tag.
What Defender admins need to know
The documentation now presents incident cases as the recommended experience while noting that the legacy experience remains available. No administrator action is specified.
Summaries are generated from the documentation change itself.
Documentation change
The comparison below shows only the changed extract. Use the full-page view for complete context.
- tier1
- usx-security
ms.topic: how-to
ms.custom: sfi-image-
nochangenochange, msecd-doc-authoring-1030 ai-usage: ai-assisted locale: en-us document_id: 86b31e29-ceb7-2c02-d751-1bb07d6dabb7
Note
Incident cases are in preview and are the recommended experience for managing incidents in the Microsoft Defender portal. The legacy incident experience remains available during this preview.available.
Note
@@ -19,7 +19,7 @@ ms.collection: - tier1 - usx-security ms.topic: how-to-ms.custom: sfi-image-nochange+ms.custom: sfi-image-nochange, msecd-doc-authoring-1030 ai-usage: ai-assisted locale: en-us document_id: 86b31e29-ceb7-2c02-d751-1bb07d6dabb7@@ -53,7 +53,7 @@ Use manual merge to combine related incident cases. When incident cases are merg
Note
-Incident cases are in preview and are the recommended experience for managing incidents in the Microsoft Defender portal. The legacy incident experience remains available during this preview.
+Incident cases are the recommended experience for managing incidents in the Microsoft Defender portal. The legacy incident experience remains available.
Note
