You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
2. Customer’s Log Analytics Cluster resource having managed identity with permissions to Key Vault – The identity is supported at the data-store (ADX cluster) level.
@@ -170,14 +170,14 @@ This resource is used as intermediate identity connection between your Key Vault
170
170
**Create**
171
171
172
172
```rst
173
-
PUT https://management.azure.com/subscriptions/{subscription-id}/resourceGroups/{resource-group-name}/providers/Microsoft.OperationalInsights/clusters/{cluster-name}?api-version=2019-08-01-preview
173
+
PUT https://management.azure.com/subscriptions/<subscription-id>/resourceGroups/<resource-group-name>/providers/Microsoft.OperationalInsights/clusters/<cluster-name>?api-version=2019-08-01-preview
174
174
Authorization: Bearer <token>
175
175
Content-type: application/json
176
176
177
177
{
178
-
"location": "region-name",
178
+
"location": "<region-name>",
179
179
"properties": {
180
-
"clusterType": "LogAnalytics" //Should be "ApplicationInsights" for Application Insights CMK
180
+
"clusterType": "LogAnalytics" //Should be "ApplicationInsights" for Application Insights CMK
181
181
},
182
182
"identity": {
183
183
"type": "systemAssigned"
@@ -194,36 +194,40 @@ Identity is assigned to the *Cluster* resource at creation time.
194
194
"identity": {
195
195
"type": "SystemAssigned",
196
196
"tenantId": "tenant-id",
197
-
"principalId": "principle-id"//A GUID that was generated by the managed identity service
197
+
"principalId": "principle-id"//A GUID that was generated by the managed identity service
198
198
},
199
199
"properties": {
200
200
"provisioningState": "Succeeded",
201
201
"clusterType": "LogAnalytics",
202
-
"clusterId": "cluster-id"//A GUID that Log Analytics generates for the cluster
202
+
"clusterId": "cluster-id"//A GUID that Log Analytics generates for the cluster
203
203
},
204
-
"id": "/subscriptions/subscription-id/resourceGroups/resource-group-name/providers/Microsoft.OperationalInsights/clusters/cluster-name", //The cluster resource Id
204
+
"id": "/subscriptions/subscription-id/resourceGroups/resource-group-name/providers/Microsoft.OperationalInsights/clusters/cluster-name", //The cluster resource Id
205
205
"name": "cluster-name",
206
206
"type": "Microsoft.OperationalInsights/clusters",
207
207
"location": "region-name"
208
208
}
209
209
210
210
```
211
+
> [!IMPORTANT]
212
+
> Copy and keep the "cluster-id" since you will need it in next steps.
211
213
212
214
If you what to delete the *Cluster* resource for any reason (for example, create it with a different name) use this API call:
Update your Key Vault and add access policy with 'Get', 'Wrap Key' and
222
-
'Unwrap Key' permissions to the *Cluster* resource ID, or *Cluster*
223
-
resource name. These permissions will be propagated to the underlaying
224
-
Azure Monitor Storage.
223
+
Update your Key Vault and add access policy for the Cluster resource. Permissions to your Key Vault are then propagated to the underlaying Azure Monitor Storage to be used for data encryption.
224
+
Open your Key Vault in Azure portal and click “Access Policies” then “+ Add Access Policy” to create a new policy with these settings:
The *Get* permission is required to verify that your Key Vault is
229
233
configured as recoverable to protect your key and the access to your
@@ -236,10 +240,9 @@ It takes a few minutes until the *Cluster* resource is propagated in
236
240
237
241
### Update Cluster resource with Key Identifier details
238
242
239
-
When you create a new version of a key, you need to update the Cluster
240
-
resource with Azure Key Vault Key identifier details, to allow Azure
241
-
Monitor Storage to use the new version. To get the Key Identifier,
242
-
select the current version of your key in Azure Key Vault:
243
+
This procedure also applies when you create a new version of a key.
244
+
245
+
Update the Cluster resource with Azure Key Vault Key identifier details, to allow Azure Monitor Storage to use the new key version. Select the current version of your key in Azure Key Vault to get the Key Identifier details:
PUT https://management.azure.com/subscriptions/{subscription-id}/resourceGroups/{resource-group-name}/providers/Microsoft.OperationalInsights/clusters/{cluster-name}?api-version=2019-08-01-preview
255
+
PUT https://management.azure.com/subscriptions/<subscription-id>/resourceGroups/<resource-group-name>/providers/Microsoft.OperationalInsights/clusters/<cluster-name>?api-version=2019-08-01-preview
"id": "/subscriptions/subscription-id/resourceGroups/resource-group-name/providers/Microsoft.OperationalInsights/clusters/cluster-name", //The cluster resource Id
293
+
"id": "/subscriptions/subscription-id/resourceGroups/resource-group-name/providers/Microsoft.OperationalInsights/clusters/cluster-name", //The cluster resource Id
291
294
"name": "cluster-name",
292
295
"type": "Microsoft.OperationalInsights/clusters",
293
-
"location": "region-name"//Example: Switzerland North
296
+
"location": "region-name"//Example: Switzerland North
294
297
}
295
298
```
296
299
@@ -308,7 +311,7 @@ following details:
308
311
**Read the *Cluster* resource ID**
309
312
310
313
```rst
311
-
GET https://management.azure.com/subscriptions/{subscription-id}/resourceGroups/{resource-group-name}/providers/Microsoft.OperationalInsights/clusters/{cluster-name}?api-version=2019-08-01-preview
314
+
GET https://management.azure.com/subscriptions/<subscription-id>/resourceGroups/<resource-group-name>/providers/Microsoft.OperationalInsights/clusters/<cluster-name>?api-version=2019-08-01-preview
**Associate a workspace to a *Cluster* resource using [Workspaces - Create Or Update](https://docs.microsoft.com/rest/api/loganalytics/workspaces/createorupdate) API**
350
353
351
354
```rst
352
-
PUT https://management.azure.com/https://management.azure.com.resources.windows-int.net/Customer.svc/subscriptions/{subscription-id}/resourcegroups/{resource-group-name}/providers/microsoft.operationalinsights/workspaces/{workspace-name}?api-version=2015-11-01-preview
355
+
PUT https://management.azure.com/subscriptions/<subscription-id>/resourcegroups/<resource-group-name>/providers/microsoft.operationalinsights/workspaces/<workspace-name>?api-version=2015-11-01-preview
353
356
Authorization: Bearer <token>
354
357
Content-type: application/json
355
358
356
359
{
357
360
"properties": {
358
361
"source": "Azure",
359
-
"customerId": {workspace-id}, //Available in Azure portal under Log Analytics workspace Overview section
362
+
"customerId": "<workspace-id>", //Available in Azure portal under Log Analytics workspace Overview section
360
363
"features": {
361
-
"clusterDefinitionId": "cluster-id" //The id of the Cluster resource
364
+
"clusterDefinitionId": "<cluster-id>" //It's the "clusterId" value provided in the respond from the previous step
@@ -495,8 +498,8 @@ with Key Identifier details" step.
495
498
496
499
- Get all *Cluster* resources for a resource group:
497
500
498
-
```
499
-
GET https://management.azure.com/subscriptions/{subscription-id}/resourceGroups/{resource-group-name}/providers/Microsoft.OperationalInsights/clusters?api-version=2019-08-01-preview
501
+
```rst
502
+
GET https://management.azure.com/subscriptions/<subscription-id>/resourceGroups/<resource-group-name>/providers/Microsoft.OperationalInsights/clusters?api-version=2019-08-01-preview
500
503
Authorization: Bearer <token>
501
504
```
502
505
@@ -512,16 +515,16 @@ with Key Identifier details" step.
@@ -591,12 +594,12 @@ This resource is used as intermediate identity connection between your Key Vault
591
594
**Create**
592
595
593
596
```rst
594
-
PUT https://management.azure.com/subscriptions/{subscription-id}/resourceGroups/{resource-group-name}/providers/Microsoft.OperationalInsights/clusters/{cluster-name}?api-version=2019-08-01-preview
597
+
PUT https://management.azure.com/subscriptions/<subscription-id>/resourceGroups/<resource-group-name>/providers/Microsoft.OperationalInsights/clusters/<cluster-name>?api-version=2019-08-01-preview
595
598
Authorization: Bearer <token>
596
599
Content-type: application/json
597
600
598
601
{
599
-
"location": "region-name",
602
+
"location": "<region-name>",
600
603
"properties": {
601
604
"clusterType":"ApplicationInsights"
602
605
},
@@ -616,12 +619,12 @@ Identity is assigned to the *Cluster* resource at creation time.
616
619
"identity": {
617
620
"type": "SystemAssigned",
618
621
"tenantId": "tenant-id",
619
-
"principalId": "principle-id"//A GUID that was generated by the managed identity service
622
+
"principalId": "principle-id"//A GUID that was generated by the managed identity service
620
623
},
621
624
"properties": {
622
625
"provisioningState": "Succeeded",
623
-
"clusterType": "ApplicationInsights", //The value is ‘ApplicationInsights’ for Application Insights CMK
624
-
"clusterId": "cluster-id"//A GUID that Log Analytics generates for the cluster
626
+
"clusterType": "ApplicationInsights", //The value is ‘ApplicationInsights’ for Application Insights CMK
627
+
"clusterId": "cluster-id"//A GUID that Log Analytics generates for the cluster - copy it since you need it for Key Vault and components association
625
628
},
626
629
"id": "/subscriptions/subscription-id/resourceGroups/resource-group-name/providers/Microsoft.OperationalInsights/clusters/cluster-name", //The cluster resource Id
0 commit comments