Skip to content

Commit 96dc9c7

Browse files
Merge pull request #265407 from ManoharLakkoju-MSFT/patch-107
(AzureCXP) fixes MicrosoftDocs/azure-docs#119505
2 parents dc35fe5 + cf659ad commit 96dc9c7

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

1414
## Prerequisites
1515

16-
1. Configure a Log Analytics dedicated cluster with at least a 500 GB/day commitment tier. When multiple workspaces are linked to the same dedicated cluster, they share the same customer-managed key. Learn about [Log Analytics Dedicated Cluster Pricing](../azure-monitor/logs/logs-dedicated-clusters.md#cluster-pricing-model).
16+
1. Configure a Log Analytics dedicated cluster with at least a 100 GB/day commitment tier. When multiple workspaces are linked to the same dedicated cluster, they share the same customer-managed key. Learn about [Log Analytics Dedicated Cluster Pricing](../azure-monitor/logs/logs-dedicated-clusters.md#cluster-pricing-model).
1717
1. Configure the CMK within Azure Monitor. Don't onboard the workspace to Sentinel yet. Learn about the [CMK provisioning steps](../azure-monitor/logs/customer-managed-keys.md?tabs=portal#customer-managed-key-provisioning-steps).
1818
1. Contact the [Microsoft Sentinel Product Group](mailto:[email protected]) - you must receive onboarding confirmation as part of completing the steps in this guide before you use the workspace.
1919

0 commit comments

Comments
 (0)