Skip to content

Commit cb7d611

Browse files
Amitbergmanyelevin
andauthored
Update articles/sentinel/customer-managed-keys.md
Co-authored-by: Yechiel Levin <[email protected]>
1 parent f091e0f commit cb7d611

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/sentinel/customer-managed-keys.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -62,7 +62,7 @@ To provision CMK, follow these steps:
6262
1. Onboard the workspace to Microsoft Sentinel via the [Onboarding API](/rest/api/securityinsights/preview/sentinel-onboarding-states/create).
6363
1. Contact the Microsoft Sentinel Product group to confirm onboarding.
6464

65-
### Step 1: CMK log analytics workspace
65+
### Step 1: Configure CMK on a Log Analytics workspace on a dedicated cluster
6666

6767
As mentioned in the [prerequisites](#prerequisites), to onboard a Log Analytics workspace with CMK to Microsoft Sentinel, this workspace must first be linked to a dedicated Log Analytics cluster on which CMK is enabled.
6868
Sentinel will use the same key which is used by the dedicated cluster.

0 commit comments

Comments
 (0)