Skip to content

Commit 35145dc

Browse files
committed
typo
1 parent fd1d082 commit 35145dc

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
@@ -27,7 +27,7 @@ This article provides background information and steps to configure a [customer-
2727

2828
- Onboarding a CMK workspace to Microsoft Sentinel is supported only via REST API and the [Azure CLI](/cli/azure/sentinel/onboarding-state?view=azure-cli-latest#az-sentinel-onboarding-state-create), and not via the Azure portal. Azure Resource Manager templates (ARM templates) currently aren't supported for CMK onboarding.
2929

30-
- In the following cases, ingested workspace data and logs are encrypted with CMK, while other Microsoft Sentinel data, including security content like analytics rules, but also analytics rules, alerts, incidents, and more, are encrypted with Microsoft-managed keys:
30+
- In the following cases, ingested workspace data and logs are encrypted with CMK, while other Microsoft Sentinel data, including security content like analytics rules, but also alerts, incidents, and more, are encrypted with Microsoft-managed keys:
3131

3232
- Enabling CMK on a workspace that's already onboarded to Microsoft Sentinel.
3333
- Enabling CMK on a cluster that contains Microsoft Sentinel-enabled workspaces.

0 commit comments

Comments
 (0)