Skip to content

Commit dc9c1d8

Browse files
authored
Update customer-managed-keys.md
1 parent 35145dc commit dc9c1d8

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

articles/sentinel/customer-managed-keys.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,10 @@
11
---
22
title: Set up customer-managed keys in Microsoft Sentinel| Microsoft Docs
33
description: Learn how to set up customer-managed key (CMK) in Microsoft Sentinel.
4-
author: yelevin
4+
author: batamig
55
ms.topic: how-to
6-
ms.date: 06/08/2023
7-
ms.author: yelevin
6+
ms.date: 07/29/2025
7+
ms.author: bagol
88
appliesto:
99
- Microsoft Sentinel in the Microsoft Defender portal
1010
- Microsoft Sentinel in the Azure portal
@@ -39,7 +39,7 @@ This article provides background information and steps to configure a [customer-
3939
- Setting a Sentinel-onboarded, CMK-enabled workspace as a non-CMK workspace by unlinking it from its CMK-enabled dedicated cluster.
4040
- Disabling CMK on a CMK-enabled Log Analytics dedicated cluster.
4141

42-
- Microsoft Sentinel is available in the Defender portal, including for customers without Microsoft Defender XDR or an E5 license. After onboarding your workspace to Defender, ingested workspace data/logs remain encrypted with CMK. Other data isn't encrypted with CMK and uses a Microsoft-managed key.
42+
- [Microsoft Sentinel is available in the Defender portal](microsoft-sentinel-defender-portal.md), including for customers without Microsoft Defender XDR or an E5 license. If you onboard your Microsoft Sentinel-enabled workspace to the Defender portal, ingested workspace data/logs remain encrypted with CMK. Other data isn't encrypted with CMK and uses a Microsoft-managed key.
4343

4444
- Microsoft Sentinel supports System Assigned Identities in CMK configuration. Therefore, the dedicated Log Analytics cluster's identity should be of **System Assigned** type. We recommend that you use the identity that's automatically assigned to the Log Analytics cluster when it's created.
4545

0 commit comments

Comments
 (0)