Updated minimum commitment tier for dedicated cluster

yossi-y · web-flow · commit 7640fe62d35f · 2021-09-05T10:06:25.000+03:00
diff --git a/articles/sentinel/customer-managed-keys.md b/articles/sentinel/customer-managed-keys.md
@@ -23,7 +23,7 @@ This article provides background information and steps to configure a [customer-
 
 ## Prerequisites
 
-- The CMK capability requires a Log Analytics dedicated cluster with at least a 1 TB/day commitment tier. Several workspaces can be linked to the same dedicated cluster, and they will share the same customer-managed key.
+- The CMK capability requires a Log Analytics dedicated cluster with at least a 500 GB/day commitment tier. Multiple workspaces can be linked to the same dedicated cluster, and they will share the same customer-managed key.
 
 - After you complete the steps in this guide and before you use the workspace, for onboarding confirmation, contact the [Azure Sentinel Product Group](mailto:azuresentinelCMK@microsoft.com).
 
@@ -142,4 +142,4 @@ Azure Sentinel does not support replacing a customer-managed key. You should use
 In this document, you learned how to set up a customer-managed key in Azure Sentinel. To learn more about Azure Sentinel, see the following articles:
 - Learn how to [get visibility into your data, and potential threats](get-visibility.md).
 - Get started [detecting threats with Azure Sentinel](./detect-threats-built-in.md).
-- [Use workbooks](monitor-your-data.md) to monitor your data.
+- [Use workbooks](monitor-your-data.md) to monitor your data.
