Added Approach 2 and 3

Author: Sreekanth Iyer (Ushta Te Consultancy Services)

articles/hdinsight/azure-monitor-agent.md

@@ -92,11 +92,146 @@ Activate the new integration by going to your cluster's portal page and scrollin
 
 1. Select Save once precondition steps are complete.
 
-### Approach 2: Enable Azure monitor agent using Azure CLI
+### Approach 2: Enable Azure monitor agent using Azure Powershell 
 
 1. Enable system-assigned MSI 
 
-   1. First get cluster information to check the MSI of cluster 
+    1. First get cluster information to check the MSI of cluster.
+    
+    
+        `Get-AzHDInsightCluster -ResourceGroupName $resourceGroup –ClusterName $cluster` 
+    
+     
+
+    1. If this cluster has no MSI, directly enable system assigned MSI 
+    
+        `Update-AzHDInsightCluster -ResourceGroupName $resourceGroup -ClusterName $cluster -IdentityType "SystemAssigned"` 
+    
+    
+    1. If this cluster only has user assigned MSI, add system assigned MSI to identity.
+     
+    
+        `Update-AzHDInsightCluster -ResourceGroupName $resourceGroup -ClusterName $cluster -IdentityType "SystemAssigned,UserAssigned" -IdentityId "$userAssignedIdentityResourceId"` 
+    
+     
+
+1. If this cluster already system assigned MSI, no need to anything. 
+
+
+1. Creation of DCR 
+
+    For more information, see [Create and edit data collection rules (DCRs)](/azure/azure-monitor/essentials/data-collection-rule-create-edit?tabs=powershell#create-a-dcr).
+
+    ```
+    # The URL of the DCR template file, change {HDIClusterType} to your cluster type. 
+    
+    # The valid types are: hadoop, hbase, interactivehive, kafka, llap, spark 
+    
+    $dcrTemplatejsonUrl = "https://hdiconfigactions.blob.core.windows.net/azuremonitoriningagent/DCR/{HDIClusterType}_dcr_template.json" 
+    
+    $dcrJsonContent = Invoke-RestMethod -Uri $dcrTemplatejsonUrl 
+    
+      
+    
+    # Get details of your Log Analytics workspace, if your workspace is in another subscription, you need to change context to the subscription 
+    
+    $workspaceResourceGroupName = "{yourWorkspaceResourceGroup}" 
+    
+    $workspaceName = {yourWorkspaceName} 
+    
+    $workspace = Get-AzOperationalInsightsWorkspace -ResourceGroupName $workspaceResourceGroupName -Name $workspaceName 
+    
+      
+    
+    # Customize the DCR content 
+    
+    $dcrJsonContent.properties.destinations.logAnalytics[0].workspaceResourceId = $workspace.ResourceId 
+    
+    $dcrJsonContent.properties.destinations.logAnalytics[0].workspaceId = $workspace.CustomerId 
+    
+    $dcrJsonContent.location = $workspace.Location 
+    
+      
+    
+    # Create the DCR using the customized JSON (DCR needs to be in the same location as Log Analytics workspace).  
+    
+    # If your HDInsight cluster is in another subscription, you need to change context to your cluster’s subscription 
+    
+    $dcrName = " {yourDcrName} " 
+    
+    $resourceGroupName = " {YourDcrResourceGroup} " 
+    
+    $dcrStr = $dcrJsonContent | ConvertTo-Json -Depth 10 
+    
+    $dcr = New-AzDataCollectionRule -Name $dcrName -ResourceGroupName $resourceGroupName -JsonString $dcrStr 
+    ```
+     
+
+1. Association of DCR.
+
+    For more information, see [Set up the Azure Monitor agent on Windows client devices](/azure/azure-monitor/agents/azure-monitor-agent-windows-client#create-and-associate-a-monitored-object).
+    
+      
+    ```
+    # Associate DCR to HDInsight cluster 
+    
+    $hdinsightClusterResourceId = "/subscriptions/{subscription}/resourceGroups/{resourceGroup}/providers/Microsoft.HDInsight/clusters/{clusterName}" 
+    
+    $dcrAssociationName = "dcrAssociationName {yourDcrAssociation} " 
+    
+    New-AzDataCollectionRuleAssociation -AssociationName $dcrAssociationName -ResourceUri $hdinsightClusterResourceId -DataCollectionRuleId $dcr.Id 
+    ```
+
+1. Enabling Azure Monitor Agent.
+
+    ```
+    # Enter user information 
+    
+    $resourceGroup = "<your-resource-group>" 
+    
+    $cluster = "<your-cluster>" 
+    
+    $LAW = "<your-Log-Analytics-workspace>" 
+    
+    # End of user input 
+     
+    
+    # obtain workspace id for defined Log Analytics workspace 
+    
+    $WorkspaceId = (Get-AzOperationalInsightsWorkspace -ResourceGroupName $resourceGroup -Name $LAW).CustomerId 
+    
+      
+    
+    # obtain primary key for defined Log Analytics workspace 
+    
+    $PrimaryKey = (Get-AzOperationalInsightsWorkspace -ResourceGroupName $resourceGroup -Name $LAW | Get-AzOperationalInsightsWorkspaceSharedKeys).PrimarySharedKey 
+    
+      
+    
+    # Enables monitoring and relevant logs will be sent to the specified workspace. 
+    
+    Enable-AzHDInsightAzureMonitorAgent -ResourceGroupName $resourceGroup -ClusterName $cluster -WorkspaceId $WorkspaceId -PrimaryKey $PrimaryKey 
+    
+      
+    
+    # Gets the status of monitoring installation on the cluster. 
+    
+    Get-AzHDInsightAzureMonitorAgent -ResourceGroupName $resourceGroup -ClusterName $cluster 
+    ```
+     
+
+1. (Optional) disabling Azure Monitor Agent. 
+
+    ```
+    Disable-AzHDInsightAzureMonitorAgent -ResourceGroupName $resourceGroup -ClusterName $cluster 
+    ```
+     
+
+### Approach 3: Enable Azure monitor agent using Azure CLI
+
+1. Enable system-assigned MSI.
+
+   1. First get cluster information to check the MSI of cluster.
 
     
         ```
@@ -109,7 +244,7 @@ Activate the new integration by going to your cluster's portal page and scrollin
         url="https://management.azure.com/subscriptions/${subscriptionId}/resourcegroups/${resourceGroupName}/providers/Microsoft.HDInsight/clusters/${clusterName}?api-version=2024-08-01-preview" 
         ```
         
-    1. If this cluster has no MSI, directly enable system assigned MSI via rest API 
+    1. If this cluster has no MSI, directly enable system assigned MSI via rest API.
     
        ```
         body="{\"identity\": {\"type\": \"SystemAssigned\"}}" 
@@ -124,12 +259,12 @@ Activate the new integration by going to your cluster's portal page and scrollin
         ```
  
 
-    1. If this cluster already system assigned MSI, no need to anything .
+    1. If this cluster already system assigned MSI, no need to anything.
     
 
-1. Creation of DCR 
+1. Creation of DCR. 
 
-    For more insormation, see [Create and edit data collection rules (DCRs)](/azure/azure-monitor/essentials/data-collection-rule-create-edit?tabs=CLI#create-a-dcr) 
+    For more information, see [Create and edit data collection rules (DCRs)](/azure/azure-monitor/essentials/data-collection-rule-create-edit?tabs=CLI#create-a-dcr) 
     
     ```
     # The URL of the DCR template file, change {HDIClusterType} to your cluster type. 
@@ -254,12 +389,11 @@ Activate the new integration by going to your cluster's portal page and scrollin
     ```    
      
 
-1. (Optional) disabling Azure Monitor Agent 
+1. (Optional) disabling Azure Monitor Agent. 
 
     ```
     az hdinsight azure-monitor-agent disable --name $cluster --resource-group $resourceGroup 
     ```
-     
 
 ### Enable Azure Monitor Agent logging for Spark cluster  
 
@@ -281,7 +415,7 @@ The following steps describe how customers can enable the new Azure Monitor Agen
 
 There are two ways you can access the new tables. 
 
-#### Approach 1: 
+#### Approach 1 
 
 1. The first way to access the new tables is through the Log Analytics workspace. 
 
@@ -296,7 +430,7 @@ There are two ways you can access the new tables.
 > [!NOTE]
 >This process describes how the logs were accessed in the old integration. This requires the user to have access to the workspace. 
 
-#### Approach 2: 
+#### Approach 2 
 
 The second way to access the new tables is through Cluster portal access. 
 
@@ -356,7 +490,7 @@ We provide a [mapping table](./log-analytics-migration.md#appendix-table-mappi
 
 ### Update dashboards for HDInsight clusters
 
-If you build multiple dashboards to monitor your HDInsight clusters, you need to adjust the query behind the table once you enable the new Azure Monitor integration. The table name or the field name might change in the new integration, but all the information you have in old integration is included. 
+If you build multiple dashboards to monitor your HDInsight clusters, you need to adjust the query behind the table once you enable the new Azure Monitor integration. The table name or the field name might change in the new integration, but all the information you have in old integration is included.
 
 Refer to the [mapping table](log-analytics-migration.md#appendix-table-mapping) between the old table/schema to the new table/schema to update the query behind the dashboards