Merge pull request #2 from nolavime/nolavime-patch-1-1

Nolavime patch 1 1

Author: nolavime

articles/automation/start-runbooks.md

@@ -14,7 +14,7 @@ The following table helps you determine the method to start a runbook in Azure A
 | **Method** | **Characteristics** |
 | --- | --- |
 | [Azure portal](#start-a-runbook-with-the-azure-portal) |<li>Simplest method with interactive user interface.<br> <li>Form to provide simple parameter values.<br> <li>Easily track job state.<br> <li>Access authenticated with Azure sign in. |
-| [Windows PowerShell](/powershell/module/azurerm.automation/start-azurermautomationrunbook) |<li>Call from command line with Windows PowerShell cmdlets.<br> <li>Can be included in automated feature with multiple steps.<br> <li>Request is authenticated with certificate or OAuth user principal / service principal.<br> <li>Provide simple and complex parameter values.<br> <li>Track job state.<br> <li>Client required to support PowerShell cmdlets. |
+| [Windows PowerShell](/powershell/module/az.automation/start-azautomationrunbook) |<li>Call from command line with Windows PowerShell cmdlets.<br> <li>Can be included in automated feature with multiple steps.<br> <li>Request is authenticated with certificate or OAuth user principal / service principal.<br> <li>Provide simple and complex parameter values.<br> <li>Track job state.<br> <li>Client required to support PowerShell cmdlets. |
 | [Azure Automation API](/rest/api/automation/) |<li>Most flexible method but also most complex.<br> <li>Call from any custom code that can make HTTP requests.<br> <li>Request authenticated with certificate, or Oauth user principal / service principal.<br> <li>Provide simple and complex parameter values. *If you're calling a Python runbook using the API, the JSON payload must be serialized.*<br> <li>Track job state. |
 | [Webhooks](automation-webhooks.md) |<li>Start runbook from single HTTP request.<br> <li>Authenticated with security token in URL.<br> <li>Client can't override parameter values specified when webhook created. Runbook can define single parameter that is populated with the HTTP request details.<br> <li>No ability to track job state through webhook URL. |
 | [Respond to Azure Alert](../azure-monitor/alerts/alerts-overview.md) |<li>Start a runbook in response to Azure alert.<br> <li>Configure webhook for runbook and link to alert.<br> <li>Authenticated with security token in URL. |

articles/azure-monitor/alerts/alerts-create-new-alert-rule.md

@@ -144,12 +144,16 @@ To edit an existing alert rule:
 
         To use one of the predefined alert rule queries, expand the **Schema and filter** pane on the left of the **Logs** pane. Then select the **Queries** tab, and select one of the queries.
 
-    1. (Optional) If you're querying an ADX cluster, Log Analytics can't automatically identify the column with the event timestamp, so we recommend that you add a time range filter to the query. For example:
-        ```azurecli
+    1. (Optional) If you're querying an ADX or ARG cluster, Log Analytics can't automatically identify the column with the event timestamp, so we recommend that you add a time range filter to the query. For example:
+        ```KQL
          adx(cluster).table    
          | where MyTS >= ago(5m) and MyTS <= now()
         ```     
-
+         ```KQL
+         arg("").Resources
+         | where type =~ 'Microsoft.Compute/virtualMachines'
+         | project _ResourceId=tolower(id), tags
+        ```  
         :::image type="content" source="media/alerts-create-new-alert-rule/alerts-logs-conditions-tab.png" alt-text="Screenshot that shows the Condition tab when creating a new log alert rule.":::
 
     1. Select **Run** to run the alert.

articles/defender-for-cloud/concept-agentless-data-collection.md

@@ -43,4 +43,4 @@ This article explains how agentless scanning works and how it helps you collect
 
 - Learn more about how to [enable agentless scanning for VMs](enable-vulnerability-assessment-agentless.md).
 
-- Check out common questions about agentless scanning and [how it affects the subscription/account](faq-cspm.yml#how-does-scanning-affect-the-account-subscription-), [agentless data collection](faq-data-collection-agents.yml#agentless), and [permissions used by agentless](faq-permissions.yml#which-permissions-are-used-by-agentless-scanning-).
+- Check out common questions about agentless scanning and [how it affects the subscription/account](faq-cspm.yml#how-does-scanning-affect-the-account-subscription-), [agentless data collection](faq-data-collection-agents.yml#agentless), and [permissions used by agentless scanning](faq-permissions.yml#which-permissions-are-used-by-agentless-scanning-).

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

@@ -11,9 +11,13 @@ ms.date: 06/05/2023
 
 # Manually configure CI/CD for load tests in GitHub Actions or Azure Pipelines
 
-Get started with automating load tests in Azure Load Testing by adding it to a CI/CD pipeline. After running a load test in the Azure portal, you export the configuration files, and configure a CI/CD pipeline in GitHub Actions or Azure Pipelines.
+You can automate a load test in Azure Load Testing by creating a CI/CD pipeline. In this article, you learn how to manually configure GitHub Actions or Azure Pipelines to invoke an existing test in Azure Load Testing. Automate a load test to continuously validate your application performance and stability under load. 
 
-After you complete this quickstart, you have a CI/CD workflow that is configured to run a load test with Azure Load Testing.
+To add an existing load test to a CI/CD pipeline:
+
+- Configure service authentication to allow GitHub Actions or Azure Pipelines to connect to your Azure load testing resource.
+- Export the load test configuration files, such as the JMeter file and load test YAML configuration.
+- Update the CI/CD pipeline definition to invoke Azure Load Testing.
 
 ## Prerequisites
 
@@ -346,6 +350,6 @@ If you don't plan to use any of the resources that you created, delete them so y
 
 Advance to the next article to learn how to identify performance regressions by defining test fail criteria and comparing test runs.
 
-> [!div class="nextstepaction"]
-> [Tutorial: automate regression tests](./tutorial-identify-performance-regression-with-cicd.md)
-> [Define test fail criteria](./how-to-define-test-criteria.md)
+- [Tutorial: automate regression tests](./tutorial-identify-performance-regression-with-cicd.md)
+- [Define test fail criteria](./how-to-define-test-criteria.md)
+- [View performance trends over time](./how-to-compare-multiple-test-runs.md)