Merge pull request #191896 from SGSneha/16Mar-HRW-RESTAPI

edited the steps in HRW-RESTAPI procedure

Author: PRMerger10

articles/automation/extension-based-hybrid-runbook-worker-install.md

@@ -3,7 +3,7 @@ title: Deploy an extension-based Windows or Linux User Hybrid Runbook Worker in
 description: This article tells how to deploy an extension-based Windows or Linux Hybrid Runbook Worker that you can use to run runbooks on Windows-based machines in your local datacenter or cloud environment.
 services: automation
 ms.subservice: process-automation
-ms.date: 09/28/2021
+ms.date: 03/17/2021
 ms.topic: how-to
 #Customer intent: As a developer, I want to learn about extension so that I can efficiently deploy Hybrid Runbook Workers.
 ---
@@ -571,7 +571,6 @@ To install and use Hybrid Worker extension using REST API, follow these steps. T
    {
    "properties": {"vmResourceId": "{VmResourceId}"}
    }
-
    ```
 
    Response of PUT call confirms if the Hybrid worker is created or not. To reconfirm, you would have to make another GET call on Hybrid worker as follows.
@@ -592,49 +591,54 @@ To install and use Hybrid Worker extension using REST API, follow these steps. T
 
    The API call will provide the value with the key: `AutomationHybridServiceUrl`. Use the URL in the next step to enable extension on the VM.
 
-1. Install the Hybrid Worker Extension  on the VM by running the following PowerShell cmdlet 
-  `(Required module: Az.Compute)`. Use the *properties.automationHybridServiceUrl* provided by the above API call.
-    ```azurepowershell-interactive
+1. Install the Hybrid Worker Extension on Azure VM by using the following API call. 
+  
+    ```http
+    PUT https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Compute/virtualMachines/{vmName}/extensions/{vmExtensionName}?api-version=2021-11-01
 
-    $settings = @{
-    "AutomationAccountURL" = <AutomationHybridServiceUrl>;
-    };
-    Set-AzVMExtension -ResourceGroupName <VMResourceGroupName> -Location <VMLocation> -VMName <VMName> -Name "HybridWorkerExtension" -Publisher "Microsoft.Azure.Automation.HybridWorker" -ExtensionType <HybridWorkerForWindows/HybridWorkerForLinux> -TypeHandlerVersion 0.1 -Settings $settings
-    ``` 
+    ```
+   
+   The request body should contain the following information:
 
-    For ARC VMs, use the below cmdlet for enabling the extension.
+    ```json
+    {
+    "location": "<VMLocation>",
+    "properties": {
+    "publisher": "Microsoft.Azure.Automation.HybridWorker",
+    "type": "<HybridWorkerForWindows/HybridWorkerForLinux>",
+    "typeHandlerVersion": <version>,
+    "settings": {
+      "AutomationAccountURL" = "<AutomationHybridServiceUrl>"
+      }
+     }
+    }
 
-   ```azurepowershell-interactive
-    New-AzConnectedMachineExtension -ResourceGroupName <VMResourceGroupName> -Location <VMLocation> -VMName <VMName> -Name "HybridWorkerExtension" -Publisher "Microsoft.Azure.Automation.HybridWorker" -ExtensionType <HybridWorkerForWindows/HybridWorkerForLinux> -TypeHandlerVersion 0.1 -Settings $settings 
-   ```
-   The Output of the above commands will confirm if the extension is successfully installed or not on the targeted VM. You can also go to the VM in the Azure portal, and check status of extensions installed on the target VM under **Extensions** tab.
+    ```
+   
+   For ARC VMs, use the below API call for enabling the extension:
 
-1. Go to the **Portal** page of the VM and in the **Extensions** tab, you can check the status of the Hybrid Worker Extension installation.
- 
-1. Run the below API call to start executing jobs on the new Hybrid worker.
-  
-  ```http
-  PUT
-  https://westcentralus.management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Automation/automationAccounts/{automationAccountName}/jobs/{jobName}?api-version=2017-05-15-preview
- 
-  ```
+    ```http
+    PUT https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.HybridCompute/machines/{machineName}/extensions/{extensionName}?api-version=2021-05-20
 
+    ```
+      
    The request body should contain the following information:
 
-   ```
-     {
-       "properties": {
-       "runbook": {
-       "name": "{RunbookName}"
-     },
-       "parameters": {
-       "key01": "value01",
-       "key02": "value02"
-     },
-       "runOn": "{hybridRunbookWorkerGroupName}"
+    ```json
+    {
+    "location": "<VMLocation>",
+    "properties": {
+    "publisher": "Microsoft.Azure.Automation.HybridWorker",
+    "type": "<HybridWorkerForWindows/HybridWorkerForLinux>",
+    "typeHandlerVersion": <version>,
+    "settings": {
+      "AutomationAccountURL" = "<AutomationHybridServiceUrl>"
+      }
      }
-     } 
-   ```
+    }
+    ```
+   Response of the *PUT* call will confirm if the extension is successfully installed or not on the targeted VM. You can also go to the VM in the Azure portal, and check status of extensions installed on the target VM under **Extensions** tab.
+
 
 ## Manage Role permissions for Hybrid Worker Groups and Hybrid Workers