Skip to content

Commit 3cfe203

Browse files
authored
Additional changes to clarify and also feedback
1 parent 60207cd commit 3cfe203

File tree

1 file changed

+17
-21
lines changed

1 file changed

+17
-21
lines changed

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

Lines changed: 17 additions & 21 deletions
Original file line numberDiff line numberDiff line change
@@ -132,7 +132,7 @@ https://management.azure.com/subscriptions/{subscriptionId}/resourcegroups/{reso
132132
Authorization: Bearer eyJ0eXAiO....
133133
```
134134

135-
where *eyJ0eXAiO....* represents the full Authorization token.
135+
Where *eyJ0eXAiO....* represents the full Authorization token.
136136

137137
You can acquire the token using one of these methods:
138138

@@ -158,26 +158,26 @@ Create an Azure Key Vault resource, then generate or import a key to be used for
158158

159159
The Azure Key Vault must be configured as recoverable to protect your key and the access to your Azure Monitor data.
160160

161-
To [Turn on recovery options](https://docs.microsoft.com/azure/key-vault/key-vault-best-practices#turn-on-recovery-options):
161+
These settings are available via CLI and PowerSell:
162162
- [Soft Delete](https://docs.microsoft.com/azure/key-vault/key-vault-ovw-soft-delete)
163163
must be turned on
164-
- Purge protection should be turned on to guard against force deletion of the secret / vault even after soft delete
164+
- [Purge protection](https://docs.microsoft.com/azure/key-vault/key-vault-ovw-soft-delete#purge-protection) should be turned on to guard against force deletion of the secret / vault even after soft delete
165165

166166
### Create *Cluster* resource
167167

168-
This resource is used as intermediate identity connection between your Key Vault and your workspaces. Only after you receive confirmation that your subscriptions were whitelisted, create a Log Analytics *Cluster* resource at the region where your workspaces are located.
168+
This resource is used as intermediate identity connection between your Key Vault and your workspaces. Only after you receive confirmation that your subscriptions were whitelisted, create a Log Analytics *Cluster* resource at the region where your workspaces are located. Application Insights and Log Analytics require separate Cluster resources. The type of the Cluster resource is defined at creation time by setting the “clusterType” property to either ‘LogAnalytics’, or ‘ApplicationInsights’. The Cluster resource type can’t be altered.
169169

170170
**Create**
171171

172-
```json
172+
```rst
173173
PUT https://management.azure.com/subscriptions/{subscription-id}/resourceGroups/{resource-group-name}/providers/Microsoft.OperationalInsights/clusters/{cluster-name}?api-version=2019-08-01-preview
174174
Authorization: Bearer <token>
175175
Content-type: application/json
176176
177177
{
178178
"location": "region-name",
179179
"properties": {
180-
"clusterType": "LogAnalytics"
180+
"clusterType": "LogAnalytics" //Should be "ApplicationInsights" for Application Insights CMK
181181
},
182182
"identity": {
183183
"type": "systemAssigned"
@@ -211,7 +211,7 @@ Identity is assigned to the *Cluster* resource at creation time.
211211

212212
If you what to delete the *Cluster* resource for any reason (for example, create it with a different name) use this API call:
213213

214-
```
214+
```rst
215215
DELETE
216216
https://management.azure.com/subscriptions/{subscription-id}/resourceGroups/{resource-group-name}/providers/Microsoft.OperationalInsights/clusters/{cluster-name}?api-version=2019-08-01-preview
217217
```
@@ -248,7 +248,7 @@ details.
248248

249249
**Update**
250250

251-
```json
251+
```rst
252252
PUT https://management.azure.com/subscriptions/{subscription-id}/resourceGroups/{resource-group-name}/providers/Microsoft.OperationalInsights/clusters/{cluster-name}?api-version=2019-08-01-preview
253253
Authorization: Bearer <token>
254254
Content-type: application/json
@@ -303,17 +303,11 @@ following details:
303303

304304
1. Confirmation that the steps above where completed
305305

306-
2. The *Cluster* resource ID that you got in the response looks like this:
307-
308-
```
309-
"id": "/subscriptions/subscription-id/resourceGroups/resource-group-name/providers/Microsoft.OperationalInsights/clusters/cluster-name"
310-
```
311-
312-
The *Cluster* resource ID can be retrieved at any time by using a Get API call.
306+
2. The Cluster resource API response. it can be retrieved at any time by using a Get API call.
313307

314308
**Read the *Cluster* resource ID**
315309

316-
```
310+
```rst
317311
GET https://management.azure.com/subscriptions/{subscription-id}/resourceGroups/{resource-group-name}/providers/Microsoft.OperationalInsights/clusters/{cluster-name}?api-version=2019-08-01-preview
318312
Authorization: Bearer <token>
319313
```
@@ -354,7 +348,7 @@ Authorization: Bearer <token>
354348
355349
**Associate a workspace to a *Cluster* resource using [Workspaces - Create Or Update](https://docs.microsoft.com/rest/api/loganalytics/workspaces/createorupdate) API**
356350

357-
```json
351+
```rst
358352
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
359353
Authorization: Bearer <token>
360354
Content-type: application/json
@@ -462,6 +456,8 @@ with Key Identifier details" step.
462456
- 'Do Not Purge' is turned on to guard against force deletion of
463457
the secret / vault even after soft delete
464458

459+
- Application Insights and Log Analytics require separate *Cluster* resources. The type of the *Cluster* resource is defined at creation time by setting the “clusterType” property to either ‘LogAnalytics’, or ‘ApplicationInsights’. The *Cluster* resource type can’t be altered.
460+
465461
- *Cluster* resource move to another resource group or subscription
466462
isn't supported currently.
467463

@@ -536,7 +532,7 @@ with Key Identifier details" step.
536532

537533
- Get all *Cluster* resources for a subscription
538534

539-
```
535+
```rst
540536
GET https://management.azure.com/subscriptions/{subscription-id}/providers/Microsoft.OperationalInsights/clusters?api-version=2019-08-01-preview
541537
Authorization: Bearer <token>
542538
```
@@ -548,7 +544,7 @@ The same as response as for '*Cluster* resources for a resource group', but in s
548544
- Delete a *Cluster* resource -- You need to delete all the associated workspaces before you can delete
549545
your *Cluster* resource:
550546

551-
```
547+
```rst
552548
DELETE
553549
https://management.azure.com/subscriptions/{subscription-id}/resourceGroups/{resource-group-name}/providers/Microsoft.OperationalInsights/clusters/{cluster-name}?api-version=2019-08-01-preview
554550
Authorization: Bearer <token>
@@ -594,7 +590,7 @@ This resource is used as intermediate identity connection between your Key Vault
594590

595591
**Create**
596592

597-
```json
593+
```rst
598594
PUT https://management.azure.com/subscriptions/{subscription-id}/resourceGroups/{resource-group-name}/providers/Microsoft.OperationalInsights/clusters/{cluster-name}?api-version=2019-08-01-preview
599595
Authorization: Bearer <token>
600596
Content-type: application/json
@@ -636,7 +632,7 @@ Identity is assigned to the *Cluster* resource at creation time.
636632

637633
### Associate a component to a *Cluster* resource
638634

639-
```json
635+
```rst
640636
PUT https://management.azure.com/subscriptions/{subscription-id}/resourceGroups/{resource-group-name}/providers/Microsoft.Insights/components/{component-name}?api-version=2015-05-01
641637
Authorization: Bearer <token>
642638
Content-type: application/json

0 commit comments

Comments
 (0)