added new info

Author: SnehaSudhirG

articles/automation/automation-hrw-run-runbooks.md

@@ -3,7 +3,7 @@ title: Run Azure Automation runbooks on a Hybrid Runbook Worker
 description: This article describes how to run runbooks on machines in your local datacenter or other cloud provider with the Hybrid Runbook Worker.
 services: automation
 ms.subservice: process-automation
-ms.date: 11/18/2022
+ms.date: 03/17/2023
 ms.topic: conceptual 
 ms.custom: devx-track-azurepowershell
 ---
@@ -24,29 +24,80 @@ Enabling the Azure Firewall on [Azure Storage](../storage/common/storage-network
 
 ## Plan runbook job behavior
 
-Azure Automation handles jobs on Hybrid Runbook Workers differently from jobs run in Azure sandboxes. If you have a long-running runbook, make sure that it's resilient to possible restart. For details of the job behavior, see [Hybrid Runbook Worker jobs](automation-hybrid-runbook-worker.md#hybrid-runbook-worker-jobs).
+Azure Automation handles jobs on Hybrid Runbook Workers differently from jobs run in cloud sandboxes. If you have a long-running runbook, make sure that it's resilient to possible restart. For details of the job behavior, see [Hybrid Runbook Worker jobs](automation-hybrid-runbook-worker.md#hybrid-runbook-worker-jobs).
 
 ## Service accounts
 
-### Windows 
+### Windows Hybrid Worker
 
 Jobs for Hybrid Runbook Workers run under the local **System** account.
+
 >[!NOTE]
->  To run PowerShell 7.x on a Windows Hybrid Runbook Worker, see [Installing PowerShell on Windows](/powershell/scripting/install/installing-powershell-on-windows).
->  We support [Hybrid worker extension based](./extension-based-hybrid-runbook-worker-install.md) and [agent based](./automation-windows-hrw-install.md) onboarding. 
->  For agent based onboarding, ensure the Windows Hybrid Runbook worker version is 7.3.1296.0 or above.
+>- PowerShell 5.1, PowerShell 7.1(preview), Python 2.7, and Python 3.8(preview) runbooks are supported on both extension-based and agent-based Windows Hybrid Runbook Workers. For agent based workers, ensure the Windows Hybrid worker version is 7.3.12960 or above.
+>- PowerShell 7.2 (preview) and Python 3.10 (preview) runbooks are supported on extension-based Windows Hybrid Workers only. Ensure the Windows Hybrid worker extension version is 1.1.11 or above.
+
+#### [Extension-based Hybrid Workers](#tab/win-extn-hrw)
+
+Make sure the path where the *pwsh.exe* executable is located and is added to the PATH environment variable. Restart the Hybrid Runbook Worker after installation is completed.
+
+**PowerShell 7.1**
+ Make sure the path where the *pwsh.exe* executable is located and is added to the PATH environment variable. Restart the Hybrid Runbook Worker after the installation completes.
+
+**Python 2.x, Python 3.x upto 3.8**
+Make sure the path where the *python.exe* executable is located and is added to the PATH environment variable. Restart the Hybrid Runbook Worker after the installation completes.
+
+**PowerShell 7.2**
+To run PowerShell 7.2 runbooks on a Windows Hybrid Worker, install *pwsh.exe* on the Hybrid Worker. See [Installing PowerShell on Windows]().
+
+After PowerShell 7.2 installation is complete, create an environment variable with Variable name as powershell_7_2_path and Variable value as location of the executable *pwsh.exe*. Restart the Hybrid Runbook Worker after environment variable is created successfully. 
 
-Make sure the path where the *pwsh.exe* executable is located and is added to the PATH environment variable. Restart the Hybrid Runbook Worker after installation completes.
+**Python 3.10**
+To run Python 3.10 runbooks on a Windows Hybrid Worker, install *python.exe* on the Hybrid Worker. See [Installing Python on Windows]().  
+
+After Python 3.10 installation is complete, create an environment variable with Variable name as python_3_10_path and Variable value as location of the executable *python.exe*. Restart the Hybrid Runbook Worker after environment variable is created successfully.
+
+#### [Agent-based Hybrid Workers](#tab/win-agt-hrw)
+
+**PowerShell 7.1**
+Make sure the path where the *pwsh.exe* executable is located and is added to the PATH environment variable. Restart the Hybrid Runbook Worker after the installation completes.
+
+**Python 2.x, Python 3.x upto 3.8**
+Make sure the path where the *python.exe executable is located and is added to the PATH environment variable. Restart the Hybrid Runbook Worker after the installation completes.
+
+---
 
-### Linux
+### Linux Hybrid Worker
 
 >[!NOTE]
-> To run PowerShell 7.x on a Linux Hybrid Runbook Worker, see [Installing PowerShell on Linux](/powershell/scripting/install/installing-powershell-on-linux).
->  We support [Hybrid worker extension based](./extension-based-hybrid-runbook-worker-install.md) and [agent based](./automation-linux-hrw-install.md) onboarding.
->  For agent based onboarding, ensure the Linux Hybrid Runbook worker version is 1.7.5.0 or above.
+>- PowerShell 5.1, PowerShell 7.1(preview), Python 2.7, Python 3.8 (preview) runbooks are supported on both extension-based and agent-based Linux Hybrid Runbook Workers. For agent-based workers, ensure the Linux Hybrid Runbook worker version is 1.7.5.0 or above.
+>- PowerShell 7.2 (preview) and Python 3.10 (preview) runbooks are supported on extension-based Linux Hybrid Workers only. Ensure the Linux Hybrid worker extension version is 1.1.11 or above.
 
+#### [Extension-based Hybrid Workers](#tab/Lin-extn-hrw)
 
-Service accounts **nxautomation** and **omsagent** are created. The creation and permission assignment script can be viewed at [https://github.com/microsoft/OMS-Agent-for-Linux/blob/master/installer/datafiles/linux.data](https://github.com/microsoft/OMS-Agent-for-Linux/blob/master/installer/datafiles/linux.data). The accounts, with the corresponding sudo permissions, must be present during [installation of a Linux Hybrid Runbook worker](automation-linux-hrw-install.md). If you try to install the worker, and the account is not present or doesn't have the appropriate permissions, the installation fails. Do not change the permissions of the `sudoers.d` folder or its ownership. Sudo permission is required for the accounts and the permissions shouldn't be removed. Restricting this to certain folders or commands may result in a breaking change. The **nxautomation** user enabled as part of Update Management executes only signed runbooks.
+>[!NOTE]
+> Create environment variable in Linux systems: </br> 1. Open /etc/environment. </br> 2. Create a new Environment variable by adding VARIABLE_NAME="variable_value" in a new line in /etc/environment (VARIABLE_NAME is the name of the new Environment variable and variable_value represents the value it is to be assigned). </br> 3. Either restart the VM or logout from current user and login again after saving the changes to /etc/environment to ensure environment variable changes take place.
+
+**Python 2.x, Python 3.x upto 3.8**
+Make sure the path where the **python.exe* executable file is located and added to the PATH environment variable. Restart the Hybrid Runbook Worker after the installation is complete.
+
+**PowerShell 7.2**
+To run PowerShell 7.2 runbooks on a Linux Hybrid Worker, install *pwsh.exe* file on the Hybrid Worker. For more information, see [Installing PowerShell on Linux](https://learn.microsoft.com/powershell/scripting/install/installing-powershell-on-linux?view=powershell-7.3).
+
+After PowerShell 7.2 installation is complete, create an environment variable with **Variable name** as *powershell_7_2_path* and **Variable value** as location of the executable *pwsh.exe*.
+
+Restart the Hybrid Runbook Worker after an environment variable is created successfully.
+
+**Python 3.10**
+To run Python 3.10 runbooks on a Linux Hybrid Worker, install *python.exe* on the Hybrid Worker. For more information, see [Installing Python 3.10 on Linux]()
+
+After Python 3.10 installation is complete, create an environment variable with **Variable name** as *python_3_10_path* and **Variable value** as location of the executable *python.exe* file. Restart the Hybrid Runbook Worker after environment variable is created successfully.
+
+
+#### [Agent-based Hybrid Workers](#tab/Lin-agt-hrw)
+
+Create Service accounts **nxautomation** and **omsagent** for agent-based Hybrid Workers. The creation and permission assignment script can be viewed at [https://github.com/microsoft/OMS-Agent-for-Linux/blob/master/installer/datafiles/linux.data](https://github.com/microsoft/OMS-Agent-for-Linux/blob/master/installer/datafiles/linux.data). The accounts, with the corresponding sudo permissions, must be present during [installation of a Linux Hybrid Runbook worker](automation-linux-hrw-install.md). 
+
+If you try to install the worker, and the account is not present or doesn't have the appropriate permissions, the installation fails. Do not change the permissions of the `sudoers.d` folder or its ownership. Sudo permission is required for the accounts and the permissions shouldn't be removed. Restricting this to certain folders or commands may result in a breaking change. The **nxautomation** user enabled as part of Update Management executes only signed runbooks.
 
 To ensure the service accounts have access to the stored runbook modules:
 
@@ -55,7 +106,7 @@ To ensure the service accounts have access to the stored runbook modules:
 
 The Automation worker log is located at `/var/opt/microsoft/omsagent/run/automationworker/worker.log`.
 
-The service accounts are removed when the machine is removed as a Hybrid Runbook Worker.
+---
 
 ## Configure runbook permissions