Merge pull request #314921 from MicrosoftDocs/main

Auto Publish – main to live - 2026-04-20 11:00 UTC

Author: learn-build-service-prod[bot]

articles/app-testing/load-testing/how-to-configure-load-test-cicd.md

@@ -296,6 +296,7 @@ Update your Azure Pipelines workflow to run a load test for your Azure load test
     ```
 
     Optionally, you can pass parameters or secrets to the load test by using the `env` or `secrets` property.
+    Set *`waitForCompletion: false`* to if you want to proceed without waiting for the load test run to complete.
 
 1. Use the `publish` task to publish the test results as artifacts in your Azure Pipelines workflow run.
 
@@ -349,6 +350,7 @@ Update your GitHub Actions workflow to run a load test for your Azure load testi
     ```
 
     Optionally, you can pass parameters or secrets to the load test by using the `env` or `secrets` property.
+    Set *`waitForCompletion: false`* to if you want to proceed without waiting for the load test run to complete.
 
 1. Use the `actions/upload-artifact` action to publish the test results as artifacts in your GitHub Actions workflow run.
 

articles/app-testing/load-testing/how-to-test-secured-endpoints.md

@@ -246,8 +246,32 @@ When you run your load test, Azure Load Testing retrieves the client certificate
 For Locust-based tests, you can retrieve the certificate and use it in your tests script. The certificate configured in the load test configuration are available in the `ALT_CERTIFICATES_DIR`. 
 
 ```Python
+endpoint = os.getenv("endpoint") or "localhost"
 cert_dir = os.getenv("ALT_CERTIFICATES_DIR")
-cert_file = open(os.path.join(cert_dir), "cert_name_in_keyvault.pfx")
+
+base_url = "https://" + endpoint
+
+key_path = "client.key.pem"
+crt_path = "client.crt.pem"
+
+
+@events.test_start.add_listener
+def on_test_start(environment, **kwargs):
+    pfx_path = open(os.path.join(cert_dir, "cert_name_in_keyvault.pfx"))
+
+    # Generate the private key
+    subprocess.check_output(
+        f'openssl pkcs12 -in "{pfx_path}" -out "{key_path}" -nocerts -nodes -passin pass:',
+        shell=True,
+        stderr=subprocess.STDOUT,
+    )
+
+    # Generate the public certificate
+    subprocess.check_output(
+        f'openssl pkcs12 -in "{pfx_path}" -out "{crt_path}" -clcerts -nokeys -passin pass:',
+        shell=True,
+        stderr=subprocess.STDOUT,
+    )
 ```
 
 ## Authenticate with a managed identity

articles/automation/add-user-assigned-identity.md

@@ -4,7 +4,7 @@ description: This article describes how to set up a user-assigned managed identi
 services: automation
 ms.subservice: process-automation
 ms.custom: devx-track-azurepowershell
-ms.date: 11/17/2025
+ms.date: 04/14/2026
 ms.topic: how-to 
 ms.service: azure-automation
 ms.author: v-rochak2
@@ -420,7 +420,7 @@ print(response.text)
 
 ## Next steps
 
-- If your runbooks aren't completing successfully, review [Troubleshoot Azure Automation managed identity issues](troubleshoot/managed-identity.md).
+- For troubleshooting issues related to user assigned managed identity, see  [Troubleshoot Azure Automation managed identity issues](troubleshoot/managed-identity.md).
 
 - If you need to disable a managed identity, see [Disable your Azure Automation account managed identity](disable-managed-identity-for-automation.md).
 

articles/automation/automation-dsc-compile.md

@@ -3,7 +3,7 @@ title: Compile DSC configurations in Azure Automation State Configuration
 description: This article tells how to compile Desired State Configuration (DSC) configurations for Azure Automation.
 services: automation
 ms.subservice: desired-state-config
-ms.date: 11/17/2025
+ms.date: 04/15/2026
 ms.topic: how-to
 ms.custom: devx-track-azurepowershell
 ms.service: azure-automation
@@ -347,6 +347,7 @@ Import-AzAutomationDscNodeConfiguration @importAzAutomationDscNodeConfigurationS
 - For pricing information, see [Azure Automation State Configuration pricing][23].
 - For an example of using State Configuration in a continuous deployment pipeline, see
   [Setup continuous deployment with Chocolatey][20].
+- For troubleshooting issues related to compiling DSC configurations in Azure Automation State Configuration, see [Troubleshoot Azure Automation State Configuration issues](troubleshoot/desired-state-configuration.md).
 
 <!-- link references -->
 [01]: ./media/automation-dsc-compile/DSC_compiling_1.png

articles/automation/automation-dsc-getting-started.md

@@ -3,7 +3,7 @@ title: Get started with Azure Automation State Configuration
 description: This article tells how to do the most common tasks in Azure Automation State Configuration.
 services: automation
 ms.subservice: desired-state-config
-ms.date: 11/17/2025
+ms.date: 04/15/2026
 ms.topic: how-to
 ms.service: azure-automation
 ms.author: v-rochak2
@@ -243,7 +243,7 @@ The DSC node can take any of the following six values as follows:
 > [!NOTE]
 > - **RefreshFrequencyMins** - It defines the frequency of node contacting the agent service and can
 >   be provided as part of onboarding to DSC. It takes a maximum value of 10080 minutes.
-> - Node will be marked as **Unresponsive** if the node does not contact the agent service for 1440
+> - Node will be marked as **Unresponsive** if the node doesn't contact the agent service for 1440
 >   minutes (1 Day). We recommend that you use **RefreshFrequencyMins** value < 1440 minutes, else
 >   the node would show in a false **Unresponsive** state.
 
@@ -319,6 +319,7 @@ You can unregister a no if you no longer want State Configuration to manage it.
 - To understand PowerShell DSC, see [Windows PowerShell Desired State Configuration Overview][17].
 - For pricing information, see [Azure Automation State Configuration pricing][25].
 - For a PowerShell cmdlet reference, see [Az.Automation][20].
+- For troubleshooting issues related to Azure Automation State Configuration (DSC), see [Troubleshoot Azure Automation State Configuration issues](troubleshoot/desired-state-configuration.md).
 
 <!-- link references -->
 [01]: ./automation-security-overview.md

articles/automation/automation-dsc-onboarding.md

@@ -5,7 +5,7 @@ services: automation
 ms.service: azure-automation
 ms.subservice: desired-state-config
 ms.topic: how-to
-ms.date: 04/01/2025
+ms.date: 04/15/2026
 ms.custom:
 ms.author: v-rochak2
 author: RochakSingh-blr
@@ -421,7 +421,7 @@ To view the status of the Azure VM Desired State Configuration extension:
 - For pricing information, see [Azure Automation State Configuration pricing][20].
 - For an example of using Azure Automation State Configuration in a continuous deployment pipeline,
   see [Set up continuous deployment with Chocolatey][14].
-- For troubleshooting information, see [Troubleshoot Azure Automation State Configuration][03].
+- For troubleshooting issues related to enabling Azure Automation State Configuration, see [Troubleshoot Azure Automation State Configuration issues](troubleshoot/desired-state-configuration.md).
 
 <!-- link references -->
 [00]: /powershell/dsc/managing-nodes/metaConfig

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: 07/29/2025
+ms.date: 04/15/2026
 ms.topic: how-to
 ms.custom: devx-track-azurepowershell, linux-related-content
 ms.service: azure-automation
@@ -19,13 +19,13 @@ author: RochakSingh-blr
 > - Azure Automation Agent-based User Hybrid Runbook Worker (Windows and Linux) has retired on **31 August 2024** and is no longer supported. Follow the guidelines on how to [migrate from an existing Agent-based User Hybrid Runbook Workers to Extension-based Hybrid Workers](migrate-existing-agent-based-hybrid-worker-to-extension-based-workers.md)
 
 
-Runbooks that run on a [Hybrid Runbook Worker](automation-hybrid-runbook-worker.md) typically manage resources on the local computer or against resources in the local environment where the worker is deployed. Runbooks in Azure Automation typically manage resources in the Azure cloud. Even though they are used differently, runbooks that run in Azure Automation and runbooks that run on a Hybrid Runbook Worker are identical in structure.
+Runbooks that run on a [Hybrid Runbook Worker](automation-hybrid-runbook-worker.md) typically manage resources on the local computer or against resources in the local environment where the worker is deployed. Runbooks in Azure Automation typically manage resources in the Azure cloud. Even though they're used differently, runbooks that run in Azure Automation and runbooks that run on a Hybrid Runbook Worker are identical in structure.
 
 When you author a runbook to run on a Hybrid Runbook Worker, you should edit and test the runbook on the machine that hosts the worker. The host machine has all the PowerShell modules and network access required to manage the local resources. Once you test the runbook on the Hybrid Runbook Worker machine, you can then upload it to the Azure Automation environment, where it can be run on the worker.
 
 ## Plan for Azure services protected by firewall
 
-Enabling the Azure Firewall on [Azure Storage](../storage/common/storage-network-security.md), [Azure Key Vault](/azure/key-vault/general/network-security), or [Azure SQL](/azure/azure-sql/database/firewall-configure) blocks access from Azure Automation runbooks for those services. Access will be blocked even when the firewall exception to allow trusted Microsoft services is enabled, as Automation is not a part of the trusted services list. With an enabled firewall, access can only be made by using a Hybrid Runbook Worker and a [virtual network service endpoint](../virtual-network/virtual-network-service-endpoints-overview.md).
+Enabling the Azure Firewall on [Azure Storage](../storage/common/storage-network-security.md), [Azure Key Vault](/azure/key-vault/general/network-security), or [Azure SQL](/azure/azure-sql/database/firewall-configure) blocks access from Azure Automation runbooks for those services. Access will be blocked even when the firewall exception to allow trusted Microsoft services is enabled, as Automation isn't a part of the trusted services list. With an enabled firewall, access can only be made by using a Hybrid Runbook Worker and a [virtual network service endpoint](../virtual-network/virtual-network-service-endpoints-overview.md).
 
 ## Plan runbook job behavior
 
@@ -79,14 +79,14 @@ After Python 3.10 installation is complete, create an environment variable with
 
 To run Python 3.8 runbooks on a Windows Hybrid Worker, install Python on the Hybrid Worker. See [Install Python on Windows](https://docs.python.org/3/using/windows.html). Create **environment variable** *PYTHON_3_PATH* for Python 3.8 runbooks and ensure to add the location of executable Python as **Variable value**. Restart the Hybrid Runbook Worker after the environment variable is created successfully.
 
-If the *Python* executable file is at the default location *C:\WPy64-3800\python-3.8.0.amd64\python.exe*, then you do not have to create the environment variable.
+If the *Python* executable file is at the default location *C:\WPy64-3800\python-3.8.0.amd64\python.exe*, then you don't have to create the environment variable.
 
 
 **Python 2.7**
 
 To run Python 2.7 runbooks on a Windows Hybrid Worker, install Python on the Hybrid Worker. See [Install Python on Windows](https://docs.python.org/3/using/windows.html). Create **environment variable** *PYTHON_2_PATH* for Python 2.7 runbooks and ensure to add the location of executable Python file as **Variable value**. Restart the Hybrid Runbook Worker after the environment variable is created successfully.
 
-If the *Python* executable file is at the default location *C:\Python27\python.exe*, then you do not have to create the environment variable.
+If the *Python* executable file is at the default location *C:\Python27\python.exe*, then you don't have to create the environment variable.
 
 
 ### Linux Hybrid Worker
@@ -101,7 +101,7 @@ If the *Python* executable file is at the default location *C:\Python27\python.e
 > [!NOTE]
 > To create environment variable in Linux systems, follow these steps:
 > 1. Open /etc/environment.
-> 1. 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).
+> 1. 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's to be assigned).
 > 1. Restart the VM or logout from current user and login after saving the changes to /etc/environment to implement environment variable changes.
 
 **PowerShell 7.4**
@@ -290,7 +290,7 @@ By default, the Hybrid jobs run under the context of System account. However, to
 1. Select **Settings**.
 1. Change the value of **Hybrid Worker credentials** from **Default** to **Custom**.
 1. Select the credential and select **Save**.
-1. If the following permissions are not assigned for Custom users, jobs might get suspended.
+1. If the following permissions aren't assigned for Custom users, jobs might get suspended.
 
   | **Resource type** | **Folder permissions** |
   | --- | --- |
@@ -302,7 +302,7 @@ By default, the Hybrid jobs run under the context of System account. However, to
 
 ## Start a runbook on a Hybrid Runbook Worker
 
-[Start a runbook in Azure Automation](start-runbooks.md) describes different methods for starting a runbook. Starting a runbook on a Hybrid Runbook Worker uses a **Run on** option that allows you to specify the name of a Hybrid Runbook Worker group. When a group is specified, one of the workers in that group retrieves and runs the runbook. If your runbook does not specify this option, Azure Automation runs the runbook as usual.
+[Start a runbook in Azure Automation](start-runbooks.md) describes different methods for starting a runbook. Starting a runbook on a Hybrid Runbook Worker uses a **Run on** option that allows you to specify the name of a Hybrid Runbook Worker group. When a group is specified, one of the workers in that group retrieves and runs the runbook. If your runbook doesn't specify this option, Azure Automation runs the runbook as usual.
 
 When you start a runbook in the Azure portal, you're presented with the **Run on** option for which you can select **Azure** or **Hybrid Worker**. Select **Hybrid Worker**, to choose the Hybrid Runbook Worker group from a dropdown.
 
@@ -388,7 +388,7 @@ To be able to work with signed runbooks, a Linux Hybrid Runbook Worker must have
 > [!IMPORTANT]
 > Once you've configured a Hybrid Runbook Worker to run only signed runbooks, unsigned runbooks fail to execute on the worker.
 
-You will perform the following steps to complete this configuration:
+You'll perform the following steps to complete this configuration:
 
 * Create a GPG keyring and keypair
 * Make the keyring available to the Hybrid Runbook Worker
@@ -413,7 +413,7 @@ To create the GPG keyring and keypair, use the Hybrid Runbook Worker:
     sudo su - nxautomation
     ```
 
-1. Once you are using **nxautomation**, generate the GPG keypair as root. GPG guides you through the steps. You must provide name, email address, expiration time, and passphrase. Then you wait until there is enough entropy on the machine for the key to be generated.
+1. Once you're using **nxautomation**, generate the GPG keypair as root. GPG guides you through the steps. You must provide name, email address, expiration time, and passphrase. Then you wait until there's enough entropy on the machine for the key to be generated.
 
     ```bash
     sudo gpg --generate-key
@@ -465,7 +465,8 @@ To help troubleshoot issues with your runbooks running on an extension-based hyb
 ## Next steps
 
 * For more information on Hybrid Runbook Worker, see [Automation Hybrid Runbook Worker](automation-hybrid-runbook-worker.md).
-* If your runbooks aren't completing successfully, review the troubleshooting guide for [runbook execution failures](troubleshoot/hybrid-runbook-worker.md#runbook-execution-fails).
 * For more information on PowerShell, including language reference and learning modules, see [PowerShell Docs](/powershell/scripting/overview).
 * Learn about [using Azure Policy to manage runbook execution](enforce-job-execution-hybrid-worker.md) with Hybrid Runbook Workers.
 * For a PowerShell cmdlet reference, see [Az.Automation](/powershell/module/az.automation).
+* For troubleshooting issues related to running Azure Automation runbooks on extension‑based Hybrid Runbook Workers, see [Troubleshoot VM extension-based Hybrid Runbook Worker issues in Automation](troubleshoot/extension-based-hybrid-runbook-worker.md).
+* For troubleshooting issues related to running Azure Automation runbooks on agent‑based Hybrid Runbook Workers, see [Troubleshoot agent-based Hybrid Runbook Worker issues in Automation](troubleshoot/hybrid-runbook-worker.md).

articles/automation/automation-limits-quotas.md

@@ -3,7 +3,7 @@ title: Manage Azure Automation subscription limits and quotas
 description: This article provides information on how to view automation limits and request for quota increase or decrease.
 services: automation
 ms.topic: how-to
-ms.date: 01/28/2025
+ms.date: 04/15/2026
 ms.service: azure-automation
 ms.author: v-rochak2
 author: RochakSingh-blr
@@ -71,5 +71,5 @@ Follow these steps to view current limits and request for quota increase:
 
 ## Next steps
 
-Learn more on [the default quotas or limits offered to different resources in Azure Automation](automation-subscription-limits-faq.md).
-
+- Learn more on [the default quotas or limits offered to different resources in Azure Automation](automation-subscription-limits-faq.md).
+- For troubleshooting issues related to Azure Automation account subscription limits and quotas,  see [Troubleshoot runbook issues](troubleshoot/runbooks.md).