Skip to content

Commit 2258a3c

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

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
@@ -65,7 +65,7 @@ To provision CMK, follow these steps:
6565
### 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.
68-
Sentinel will use the same key which is used by the dedicated cluster.
68+
Microsoft Sentinel will use the same key used by the dedicated cluster.
6969
Follow the instructions in [Azure Monitor customer-managed key configuration](../azure-monitor/logs/customer-managed-keys.md) in order to create a CMK workspace that is used as the Microsoft Sentinel workspace in the following steps.
7070

7171
### Step 2: Register the Azure Cosmos DB Resource Provider

0 commit comments

Comments
 (0)