Skip to content

Commit 9a53234

Browse files
authored
Update CMK workspace - add step and considerations
@austinmccollum ------- cc: @yelevin
1 parent 0256cde commit 9a53234

File tree

1 file changed

+7
-2
lines changed

1 file changed

+7
-2
lines changed

articles/sentinel/customer-managed-keys.md

Lines changed: 7 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ This article provides background information and steps to configure a [customer-
1616

1717
- 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.
1818

19-
- After you complete the steps in this guide and before you use the workspace, for onboarding confirmation, contact the [Microsoft Sentinel Product Group](mailto:[email protected]).
19+
- After you complete the steps in this guide and before you use the workspace, you must contact the [Microsoft Sentinel Product Group](mailto:[email protected]) for onboarding confirmation.
2020

2121
- Learn about [Log Analytics Dedicated Cluster Pricing](../azure-monitor/logs/logs-dedicated-clusters.md#cluster-pricing-model).
2222

@@ -43,6 +43,7 @@ This article provides background information and steps to configure a [customer-
4343
- Changing the customer-managed key to another key (with another URI) currently *isn't supported*. You should change the key by [rotating it](../azure-monitor/logs/customer-managed-keys.md#key-rotation).
4444

4545
- Before you make any CMK changes to a production workspace or to a Log Analytics cluster, contact the [Microsoft Sentinel Product Group](mailto:[email protected]).
46+
- CMK enabled workspaces don't support [search jobs](investigate-large-datasets.md).
4647

4748
## How CMK works
4849

@@ -97,7 +98,11 @@ Follow the instructions to [Register the Azure Cosmos DB Resource Provider](../c
9798

9899
Make sure to add access from Azure Cosmos DB to your Azure Key Vault instance. Follow the Azure Cosmos DB instructions to [add an access policy to your Azure Key Vault instance](../cosmos-db/how-to-setup-cmk.md#add-access-policy) with an Azure Cosmos DB principal.
99100

100-
### STEP 5: Onboard the workspace to Microsoft Sentinel via the onboarding API
101+
### STEP 5: Contact the Microsoft Sentinel Product group to confirm onboarding
102+
103+
You must confirm onboarding of your CMK enabled workspace by contacting the [Microsoft Sentinel Product Group](mailto:[email protected]).
104+
105+
### STEP 6: Onboard the workspace to Microsoft Sentinel via the onboarding API
101106

102107
Onboard the workspace to Microsoft Sentinel via the [Onboarding API](https://github.com/Azure/Azure-Sentinel/raw/master/docs/Azure%20Sentinel%20management.docx).
103108

0 commit comments

Comments
 (0)