Merge pull request #299513 from SnehaSudhirG/08May-AutomationUpdate

prmerger-automator[bot] · web-flow · commit 11e70d5afbdd · 2025-05-08T08:57:41.000Z
Updated the info for 4 articles
diff --git a/articles/automation/delete-account.md b/articles/automation/delete-account.md
@@ -4,7 +4,7 @@ description: This article tells how to delete and your Automation account across
 services: automation
 ms.service: azure-automation
 ms.subservice: process-automation
-ms.date: 03/20/2025
+ms.date: 05/08/2025
 ms.topic: how-to 
 ---
 
@@ -93,6 +93,8 @@ While it attempts to unlink the Automation account, you can track the progress u
 
 After the Automation account is successfully unlinked from the workspace, perform the steps in the [standalone Automation account](#delete-a-standalone-automation-account) section to delete the account.
 
+Automation account deletion may still fail after successfully unlinking the Log Analytics workspace. Retry deletion after 24 hours.
+
 > [!NOTE]
 > A previously soft-deleted Log Analytics workspace can't be unlinked from the Automation account successfully. In this scenario, first recover and permanently delete it to forcefully remove the link. Learn [how to recover a workspace in a soft-delete state](/azure/azure-monitor/logs/delete-workspace#recover-a-workspace-in-a-soft-delete-state) and [delete it permanently](/azure/azure-monitor/logs/delete-workspace#delete-a-workspace-permanently).
 
diff --git a/articles/automation/extension-based-hybrid-runbook-worker-install.md b/articles/automation/extension-based-hybrid-runbook-worker-install.md
@@ -4,7 +4,7 @@ description: This article provides information about deploying the extension-bas
 services: automation
 ms.subservice: process-automation
 ms.custom: devx-track-azurepowershell, devx-track-azurecli, devx-track-bicep, linux-related-content
-ms.date: 04/22/2025
+ms.date: 05/08/2025
 ms.topic: how-to
 #Customer intent: As a developer, I want to learn about extension so that I can efficiently deploy Hybrid Runbook Workers.
 ms.service: azure-automation
@@ -37,7 +37,7 @@ Azure Automation stores and manages runbooks and then delivers them to one or mo
 
 | Windows (x64)  | Linux (x64) |
 |---|---|
-| &#9679; Windows Server 2022 (including Server Core) <br> &#9679; Windows Server 2019 (including Server Core) <br> &#9679; Windows Server 2016, version 1709, and 1803 (excluding Server Core) <br> &#9679; Windows Server 2012, 2012 R2 (excluding Server Core) <br> &#9679; Windows 10 Enterprise (including multi-session) and Pro <br> &#9679; Windows 11 Enterprise (including multi-session) and Pro | &#9679; Debian GNU/Linux 8, 9, 10, and 11 <br> &#9679; Ubuntu 18.04 LTS, 20.04 LTS, and 22.04 LTS <br> &#9679; SUSE Linux Enterprise Server 15.2, 15.3, 15.4, 15.5, and 15.6 <br> &#9679; Red Hat Enterprise Linux Server 7, 8, and 9 <br>  &#9679; Rocky Linux 9 </br> &#9679; Oracle Linux 7, 8, and 9 <br> *Hybrid Worker extension would follow support timelines of the OS vendor*.|
+| &#9679; Windows Server 2022 (including Server Core) <br> &#9679; Windows Server 2019 (including Server Core) <br> &#9679; Windows Server 2016, version 1709, and 1803 (excluding Server Core) <br> &#9679; Windows Server 2012, 2012 R2 (excluding Server Core) <br> &#9679; Windows 10 Enterprise (including multi-session) and Pro <br> &#9679; Windows 11 Enterprise (including multi-session) and Pro | &#9679; Debian GNU/Linux 8, 9, 10, and 11 <br> &#9679; Ubuntu 18.04 LTS, 20.04 LTS, and 22.04 LTS <br> &#9679; SUSE Linux Enterprise Server 15.2, 15.3, 15.4, 15.5, and 15.6 <br> &#9679; Red Hat Enterprise Linux Server 7, 8, and 9 <br>  &#9679; Rocky Linux 9 </br> &#9679; Oracle Linux 7, 8, and 9 <br> *Hybrid Worker extension would follow support timelines of the OS vendor*. </br> Python version 3.12+ are not supported for Linux Hybrid Runbook Worker. |
  
 
 ### Other Requirements
diff --git a/articles/automation/source-control-integration.md b/articles/automation/source-control-integration.md
@@ -3,7 +3,7 @@ title: Use source control integration in Azure Automation
 description: This article tells you how to synchronize Azure Automation source control with other repositories.
 services: automation
 ms.subservice: process-automation
-ms.date: 10/17/2024
+ms.date: 05/08/2025
 ms.topic: how-to 
 ms.custom: devx-track-azurepowershell
 ms.service: azure-automation
@@ -98,6 +98,7 @@ Use this procedure to configure source control using the Azure portal.
 > [!NOTE]
 > - The login for your source control repository might be different from your login for the Azure portal. Ensure that you are logged in with the correct account for your source control repository when configuring source control. If there is a doubt, open a new tab in your browser, log out from **dev.azure.com**, **visualstudio.com**, or **github.com**, and try reconnecting to source control. 
 > - Cross-tenant authentication isn't supported.
+> - Auto-sync may fail if Source Control was created over a year ago, as the webhook used to invoke the Source Control expires after one year. To resolve this issue, create a new Source Control in the Automation account with the same configuration, which will generate a new webhook with an extended expiry date.
 
 ### Configure source control in PowerShell
 
diff --git a/articles/automation/troubleshoot/extension-based-hybrid-runbook-worker.md b/articles/automation/troubleshoot/extension-based-hybrid-runbook-worker.md
@@ -2,7 +2,7 @@
 title: Troubleshoot extension-based Hybrid Runbook Worker issues in Azure Automation 
 description: This article tells how to troubleshoot and resolve issues that arise with Azure Automation extension-based Hybrid Runbook Workers.
 services: automation
-ms.date: 08/26/2024
+ms.date: 05/08/2025
 ms.topic: troubleshooting 
 ms.custom:
 ---
@@ -73,6 +73,54 @@ To help troubleshoot issues with extension-based Hybrid Runbook Workers:
     /home/hweautomation
     ```
 
+
+### Scenario: Jobs on Linux Hybrid Worker may get stuck in Running status
+
+#### Issue
+Jobs on Linux Hybrid Worker may get stuck in Running status while the CPU core usage is less than 25%.
+
+#### Cause
+Each CPU core has a default quota limit of 25% for Linux Hybrid Worker.
+
+#### Resolution
+You can remove this limit and make it unrestricted with the following steps:
+
+**Switch to sudo permissions** -
+  1. sudo su
+  1. systemctl status hwd.service // check and make sure hwd service is running well.
+
+**Update the setting in the below file in Hybrid Worker**
+  1. vi /lib/systemd/system/hwd.service
+  1. Update the setting from CPUQuota=25% to CPUQuota= as shown below to make the usage unrestricted.
+
+  ```
+    root@ubuntu2204:~# cat /lib/systemd/system/hwd.service
+    [Unit]
+    Description=HW Service
+    After=network.target
+    
+    [Service]
+    Type=simple
+    ExecStart=/usr/bin/python3 /var/lib/waagent/Microsoft.Azure.Automation.HybridWorker.HybridWorkerForLinux-1.1.16/HybridWorkerAgent/DaemonScripts/Scripts/3.x/automationWorkerStarterScript.py
+    TimeoutStartSec=5
+    Restart=always
+    RestartSec=10s
+    TimeoutStopSec=600
+    CPUQuota=
+    KillMode=process
+    
+    [Install]
+    WantedBy=multi-user.target
+    
+   ```
+
+**Restart hwd service**
+  1. systemctl daemon-reload
+  1. systemctl restart hwd.service
+
+For more information, see [Linux hybrid jobs get stuck in Running state even if each CPU core usage is less than 25% - Overview](https://supportability.visualstudio.com/AAAP_Code/_wiki/wikis/AAAP/1980067/KI-Linux-hybrid-jobs-get-stuck-in-Running-status-even-if-each-CPU-core-usage-is-less-than-25-).
+
+
 ### Scenario: Runbooks go into a suspended state on a Hybrid Runbook Worker when using a custom account on a server with User Account Control (UAC) enabled
 
 #### Issue
@@ -267,15 +315,15 @@ Sometimes the uninstallation process might get stuck.
    ```
 1. **Remove registry key**, if present: `HKLM:\Software\Microsoft\Azure\HybridWorker`
 
-   1. PowerShell code to remove the registry key along with any subkeys and values under it.:
+   1. PowerShell code to remove the registry key along with any sub keys and values under it.:
    
       ```powershell
       Get-Item HKLM:\Software\Microsoft\Azure\HybridWorker | Remove-Item -Recurse
       ```
       
 1. **Remove the registry key**, if present: `HKLM:\Software\Microsoft\HybridRunbookWorkerV2`
 
-   1. PowerShell code to remove the registry key along with any subkeys and values under it.:
+   1. PowerShell code to remove the registry key along with any sub keys and values under it.:
    
       ```powershell
       Get-Item HKLM:\Software\Microsoft\HybridRunbookWorkerV2 | Remove-Item -Recurse
