Skip to content

Commit 84901f7

Browse files
authored
Merge pull request #102790 from yossi-y/patch-43
Added association verification
2 parents 9e29988 + a6d2f12 commit 84901f7

File tree

1 file changed

+40
-1
lines changed

1 file changed

+40
-1
lines changed

articles/azure-monitor/platform/customer-managed-keys.md

Lines changed: 40 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ ms.date: 01/11/2020
1313

1414
This article provides background information and steps to configure Customer-Managed Keys (CMK) for your Log Analytics workspaces and Application Insights components. Once configured, any data sent to your workspaces or components is encrypted with your Azure Key Vault key.
1515

16-
We recommend you review [Limitations and constraints](#Limitations and constraints) below before configuration.
16+
We recommend you review [Limitations and constraints](#limitations-and-constraints) below before configuration.
1717

1818
## Disclaimers
1919

@@ -399,6 +399,45 @@ Content-type: application/json
399399
After the association, data that is sent to your workspaces is stored
400400
encrypted with your managed key.
401401

402+
### Workspace association verification
403+
You can verify if a workspace is associated to a *Custer* resource by looking at the [Workspaces – Get](https://docs.microsoft.com/rest/api/loganalytics/workspaces/get) response. Associated workspace will have a 'clusterResourceId' property with the *Cluster* resource ID.
404+
405+
```rest
406+
GET https://management.azure.com/subscriptions/<subscription-id>/resourcegroups/<resource-group-name>/providers/microsoft.operationalInsights/workspaces/<workspace-name>?api-version=2015-11-01-preview
407+
```
408+
409+
**Response**
410+
411+
```json
412+
{
413+
"properties": {
414+
"source": "Azure",
415+
"customerId": "workspace-name",
416+
"provisioningState": "Succeeded",
417+
"sku": {
418+
"name": "pricing-tier-name",
419+
"lastSkuUpdate": "Tue, 28 Jan 2020 12:26:30 GMT"
420+
},
421+
"retentionInDays": days,
422+
"features": {
423+
"legacy": 0,
424+
"searchVersion": 1,
425+
"enableLogAccessUsingOnlyResourcePermissions": true/false,
426+
"clusterResourceId": "/subscriptions/subscription-id/resourceGroups/resource-group-name/providers/Microsoft.OperationalInsights/clusters/cluster-name"
427+
},
428+
"workspaceCapping": {
429+
"dailyQuotaGb": -1.0,
430+
"quotaNextResetTime": "Tue, 28 Jan 2020 14:00:00 GMT",
431+
"dataIngestionStatus": "RespectQuota"
432+
}
433+
},
434+
"id": "/subscriptions/subscription-id/resourcegroups/resource-group-name/providers/microsoft.operationalinsights/workspaces/workspace-name",
435+
"name": "workspace-name",
436+
"type": "Microsoft.OperationalInsights/workspaces",
437+
"location": "region-name"
438+
}
439+
```
440+
402441
## CMK (KEK) revocation
403442

404443
Azure Monitor Storage will always respect changes in key permissions

0 commit comments

Comments
 (0)