Some modifications.

Author: yossi-y

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

@@ -187,9 +187,12 @@ The identity is assigned to the *Cluster* resource at creation time.
 
 202 Accepted. This is a standard Resource Manager response for asynchronous operations.
 
+>[!Important]
+> It takes the provisioning of the underly ADX cluster a few minutes to complete. You can verify the provisioning state when performing GET REST API call on the *Cluster* resource and looking at the *provisioningState* value. It is *ProvisioningAccount* while provisioning and "Succeeded" when completed.
+
 ### Azure Monitor data-store (ADX cluster) provisioning
 
-During the early access period of the feature, the ADX cluster is provisioned manually by the product team once the previous steps are completed. Use your Microsoft channel for the provisioning while providing the *Cluster* resource response. 
+During the early access period of the feature, the ADX cluster is provisioned manually by the product team once the previous steps are completed. Use your Microsoft channel for this step and provide the *Cluster* resource response. 
 
 ```rst
 GET https://management.azure.com/subscriptions/<subscription-id>/resourceGroups/<resource-group-name>/providers/Microsoft.OperationalInsights/clusters/<cluster-name>?api-version=2019-08-01-preview
@@ -224,9 +227,7 @@ Authorization: Bearer <token>
 }
 ```
 
->[!Important]
-> It takes the provisioning of the underly ADX cluster a few minutes to complete. The *provisioningState* value indicates its state, it is *ProvisioningAccount* while provisioning and "Succeeded" when provisioning is completed.
-> The "principalId" GUID is generated by the managed identity service for the *Cluster* resource.
+The "principalId" GUID is generated by the managed identity service for the *Cluster* resource.
 
 ### Grant Key Vault permissions
 
@@ -559,48 +560,27 @@ PUT https://management.azure.com/subscriptions/<subscription-id>/resourceGroups/
 Authorization: Bearer <token>
 Content-type: application/json
 
-{
-  "location": "<region-name>",
-  "properties": {
-      "clusterType":"ApplicationInsights"
-  },
-  "identity": {
-      "type": "systemAssigned"
-  }
-}
-```
-
-**Response**
-
-Identity is assigned to the *Cluster* resource at creation time.
-
-```json
-
 {
   "identity": {
-    "type": "SystemAssigned",
-    "tenantId": "tenant-id",
-    "principalId": "principle-id"
-  },
+    "type": "systemAssigned"
+    },
   "sku": {
     "name": "capacityReservation",
     "Capacity": 1000
     },
   "properties": {
-    "provisioningState": "Succeeded",
-    "clusterType": "ApplicationInsights", 
-    "clusterId": "cluster-id" 
+    "clusterType":"ApplicationInsights"
     },
-  "id": "/subscriptions/subscription-id/resourceGroups/resource-group-name/providers/Microsoft.OperationalInsights/clusters/cluster-name",
-  "name": "cluster-name",
-  "type": "Microsoft.OperationalInsights/clusters",
-  "location": "region-name"
+  "location": "<region-name>"
 }
 ```
-"principle-id" is a GUID that was generated by the managed identity service.
 
-> [!IMPORTANT]
-> Copy and keep the "principle-id" value since you will need it in next steps.
+**Response**
+
+202 Accepted. This is a standard Resource Manager response for asynchronous operations.
+
+>[!Important]
+> It takes the provisioning of the underly ADX cluster a few minutes to complete. You can verify the provisioning state when performing GET REST API call on the *Cluster* resource and looking at the *provisioningState* value. It is *ProvisioningAccount* while provisioning and "Succeeded" when completed.
 
 ### Associate a component to a *Cluster* resource using [Components - Create Or Update](https://docs.microsoft.com/rest/api/application-insights/components/createorupdate) API
 
@@ -648,6 +628,9 @@ Authorization: Bearer <token>
   }
 ```
 
+> [!IMPORTANT]
+> Copy and keep the "principle-id" value since you will need it in next steps.
+
 **Associate a component**
 
 ```rst