Merge pull request #273827 from MicrosoftDocs/main

Publish to live, Tuesday 4 AM PST, 4/30

Author: ttorble

articles/automation/whats-new.md

@@ -4,7 +4,7 @@ description: Significant updates to Azure Automation updated each month.
 services: automation
 ms.subservice:
 ms.topic: overview
-ms.date: 01/26/2024
+ms.date: 04/30/2024
 ms.custom: references_regions
 ---
 
@@ -21,6 +21,12 @@ Azure Automation receives improvements on an ongoing basis. To stay up to date w
 
 This page is updated monthly, so revisit it regularly. If you're looking for items older than six months, you can find them in [Archive for What's new in Azure Automation](whats-new-archive.md).
 
+## April 2024
+ 
+### Changes in Process Automation subscription and service limits and quotas
+ 
+Find the changes in Azure Automation limits and quotas [here](../azure-resource-manager/management/azure-subscription-service-limits.md#automation-limits). These changes are aimed towards improving the reliability and performance of the service by ensuring fair access to cloud resources for all users. We recommend to use other regions or other subscriptions within the same Azure geography to create more Automation accounts.
+
 ## January 2024
 
 ### Public Preview: Azure Automation Runtime environment & support for Azure CLI commands in runbooks

articles/azure-monitor/agents/data-collection-rule-azure-monitor-agent.md

@@ -65,7 +65,12 @@ You can define a data collection rule to send data from multiple machines to mul
     <!-- convertborder later -->
     :::image type="content" source="media/data-collection-rule-azure-monitor-agent/data-collection-rule-data-source-basic-updated.png" lightbox="media/data-collection-rule-azure-monitor-agent/data-collection-rule-data-source-basic-updated.png" alt-text="Screenshot that shows the Azure portal form to select basic performance counters in a data collection rule." border="false":::
 
-1. Select **Custom** to collect logs and performance counters that aren't [currently supported data sources](azure-monitor-agent-overview.md#data-sources-and-destinations) or to [filter events by using XPath queries](#filter-events-using-xpath-queries). You can then specify an [XPath](https://www.w3schools.com/xml/xpath_syntax.asp) to collect any specific values. For an example, see [Sample DCR](data-collection-rule-sample-agent.md).
+1. Select **Custom** to collect logs and performance counters that aren't [currently supported data sources](azure-monitor-agent-overview.md#data-sources-and-destinations) or to [filter events by using XPath queries](#filter-events-using-xpath-queries). You can then specify an [XPath](https://www.w3schools.com/xml/xpath_syntax.asp) to collect any specific values.
+
+    To collect a performance counter that's not available by default, use the format `\PerfObject(ParentInstance/ObjectInstance#InstanceIndex)\Counter`. If the counter name contains an ampersand (&), replace it with `&amp;`. For example, `\Memory\Free &amp; Zero Page List Bytes`.
+   
+    For examples of DCRs, see [Sample data collection rules (DCRs) in Azure Monitor](data-collection-rule-sample-agent.md).
+   
     <!-- convertborder later -->
     :::image type="content" source="media/data-collection-rule-azure-monitor-agent/data-collection-rule-data-source-custom-updated.png" lightbox="media/data-collection-rule-azure-monitor-agent/data-collection-rule-data-source-custom-updated.png" alt-text="Screenshot that shows the Azure portal form to select custom performance counters in a data collection rule." border="false":::
 

articles/azure-monitor/agents/media/use-azure-monitor-agent-troubleshooter/ama-win-standalone-prerequisites-cmd.png

@@ -21,9 +21,7 @@ The Azure Monitor Agent (AMA) Troubleshooter is designed to help identify issues
 ### Troubleshooter existence check
 Check for the existence of the AMA Agent Troubleshooter directory on the machine to be diagnosed to confirm the installation of the agent troubleshooter:
 
-***C:/Packages/Plugins/Microsoft.Azure.Monitor.AzureMonitorWindowsAgent***
-
-# [PowerShell](#tab/WindowsPowerShell)
+# [AMA Extension - PowerShell](#tab/WindowsPowerShell)
 To verify the Agent Troubleshooter is present, copy the following command and run in PowerShell as administrator:
 ```powershell
 Test-Path -Path "C:/Packages/Plugins/Microsoft.Azure.Monitor.AzureMonitorWindowsAgent"
@@ -33,7 +31,7 @@ If the directory exists, the Test-Path cmdlet returns `True`.
 
 :::image type="content" source="./media/use-azure-monitor-agent-troubleshooter/ama-win-prerequisites-powershell.png" alt-text="Screenshot of the PowerShell window, which shows the result of Test-Path PowerShell cmdlet." lightbox="media/use-azure-monitor-agent-troubleshooter/ama-win-prerequisites-powershell.png":::
 
-# [Windows Command Prompt](#tab/WindowsCmd)
+# [AMA Extension - Command Prompt](#tab/WindowsCmd)
 To verify the Agent Troubleshooter is present, copy the following command and run in Command Prompt as administrator:
 ```command
 cd "C:/Packages/Plugins/Microsoft.Azure.Monitor.AzureMonitorWindowsAgent"
@@ -43,6 +41,31 @@ If the directory exists, the cd command changes directories successfully.
 
 :::image type="content" source="media/use-azure-monitor-agent-troubleshooter/ama-win-prerequisites-cmd.png" alt-text="Screenshot of the command prompt window, which shows the result of cd command." lightbox="media/use-azure-monitor-agent-troubleshooter/ama-win-prerequisites-cmd.png":::
 
+# [AMA Standalone - PowerShell](#tab/WindowsPowerShellStandalone)
+To verify the Agent Troubleshooter is present, copy the following command and run in PowerShell as administrator:
+```powershell
+$installPath = (Get-ItemProperty -Path "Registry::HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\AzureMonitorAgent").AMAInstallPath
+Test-Path -Path $installPath\Troubleshooter
+```
+
+If the directory exists, the Test-Path cmdlet returns `True`.
+
+:::image type="content" source="./media/use-azure-monitor-agent-troubleshooter/ama-win-standalone-prerequisites-powershell.png" alt-text="Screenshot of the PowerShell window, which shows the result of Test-Path PowerShell cmdlet." lightbox="media/use-azure-monitor-agent-troubleshooter/ama-win-standalone-prerequisites-powershell.png":::
+
+# [AMA Standalone - Command Prompt](#tab/WindowsCmdStandalone)
+To verify the Agent Troubleshooter is present, copy the following command and run in Command Prompt as administrator:
+
+> [!Note]
+> If you have customized the AMAInstallPath, you'll need to adjust the below path to your custom path.
+
+```command
+cd "C:\Program Files\Azure Monitor Agent\Troubleshooter"
+```
+
+If the directory exists, the cd command changes directories successfully.
+
+:::image type="content" source="media/use-azure-monitor-agent-troubleshooter/ama-win-standalone-prerequisites-cmd.png" alt-text="Screenshot of the command prompt window, which shows the result of cd command." lightbox="media/use-azure-monitor-agent-troubleshooter/ama-win-standalone-prerequisites-cmd.png":::
+
 ---
 
 If directory doesn't exist or the installation is failed, follow [Basic troubleshooting steps](../agents/azure-monitor-agent-troubleshoot-windows-vm.md#basic-troubleshooting-steps-installation-agent-not-running-configuration-issues).
@@ -52,7 +75,7 @@ Yes, the directory exists. Proceed to [Run the Troubleshooter](#run-the-troubles
 ## Run the Troubleshooter
 On the machine to be diagnosed, run the Agent Troubleshooter.
 
-# [PowerShell](#tab/WindowsPowerShell)
+# [AMA Extension - PowerShell](#tab/WindowsPowerShell)
 To start the Agent Troubleshooter, copy the following command and run in PowerShell as administrator:
 ```powershell
 $currentVersion = ((Get-ChildItem -Path "Registry::HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows Azure\HandlerState\" `
@@ -70,7 +93,7 @@ It runs a series of activities that could take up to 15 minutes to complete. Be
 
 :::image type="content" source="media/use-azure-monitor-agent-troubleshooter/ama-win-run-troubleshooter-powershell.png" alt-text="Screenshot of the PowerShell window, which shows the result of the AgentTroubleshooter." lightbox="media/use-azure-monitor-agent-troubleshooter/ama-win-run-troubleshooter-powershell.png":::
 
-# [Windows Command Prompt](#tab/WindowsCmd)
+# [AMA Extension - Command Prompt](#tab/WindowsCmd)
 To start the Agent Troubleshooter, copy the following command and run in Command Prompt as administrator:
 
 > [!Note]
@@ -85,12 +108,44 @@ It runs a series of activities that could take up to 15 minutes to complete. Be
 
 :::image type="content" source="media/use-azure-monitor-agent-troubleshooter/ama-win-run-troubleshooter-cmd.png" alt-text="Screenshot of the command prompt window, which shows the result of the AgentTroubleshooter." lightbox="media/use-azure-monitor-agent-troubleshooter/ama-win-run-troubleshooter-cmd.png":::
 
+# [AMA Standalone - PowerShell](#tab/WindowsPowerShellStandalone)
+To start the Agent Troubleshooter, copy the following command and run in PowerShell as administrator:
+```powershell
+$installPath = (Get-ItemProperty -Path "Registry::HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\AzureMonitorAgent").AMAInstallPath
+Set-Location -Path $installPath\Troubleshooter
+Start-Process -FilePath $installPath\Troubleshooter\AgentTroubleshooter.exe -ArgumentList "--ama"
+Invoke-Item $installPath\Troubleshooter
+```
+
+It runs a series of activities that could take up to 15 minutes to complete. Be patient until the process completes.
+
+:::image type="content" source="media/use-azure-monitor-agent-troubleshooter/ama-win-standalone-run-troubleshooter-powershell.png" alt-text="Screenshot of the PowerShell window, which shows the result of the AgentTroubleshooter." lightbox="media/use-azure-monitor-agent-troubleshooter/ama-win-standalone-run-troubleshooter-powershell.png":::
+
+# [AMA Standalone - Command Prompt](#tab/WindowsCmdStandalone)
+To start the Agent Troubleshooter, copy the following command and run in Command Prompt as administrator:
+
+> [!Note]
+> If you have customized the AMAInstallPath, you'll need to adjust the below path to your custom path.
+
+```command
+cd "C:\Program Files\Azure Monitor Agent\Troubleshooter"
+AgentTroubleshooter.exe --ama
+```
+
+It runs a series of activities that could take up to 15 minutes to complete. Be patient until this process completes.
+
+:::image type="content" source="media/use-azure-monitor-agent-troubleshooter/ama-win-standalone-run-troubleshooter-cmd.png" alt-text="Screenshot of the command prompt window, which shows the result of the AgentTroubleshooter." lightbox="media/use-azure-monitor-agent-troubleshooter/ama-win-standalone-run-troubleshooter-cmd.png":::
+
 ---
 
 Log file is created in the directory where the AgentTroubleshooter.exe is located.
 
+Example for extension-based install:
 :::image type="content" source="media/use-azure-monitor-agent-troubleshooter/ama-win-verify-log-exists.png" alt-text="Screenshot of the Windows explorer window, which shows the output of the AgentTroubleshooter." lightbox="media/use-azure-monitor-agent-troubleshooter/ama-win-verify-log-exists.png":::
 
+Example for standalone install:
+:::image type="content" source="media/use-azure-monitor-agent-troubleshooter/ama-win-standalone-verify-log-exists.png" alt-text="Screenshot of the Windows explorer window, which shows the output of the AgentTroubleshooter." lightbox="media/use-azure-monitor-agent-troubleshooter/ama-win-standalone-verify-log-exists.png":::
+
 ## Frequently Asked Questions
 
 ### Can I copy the Troubleshooter from a newer agent to an older agent and run it on the older agent to diagnose issues with the older agent?

articles/azure-monitor/agents/media/use-azure-monitor-agent-troubleshooter/ama-win-standalone-prerequisites-powershell.png

@@ -14,7 +14,7 @@ Data collection rules (DCRs) are sets of instructions supporting data collection
 
 DCRs are stored in Azure so that you can centrally manage them. Different components of a data collection workflow will access the DCR for particular information that it requires. In some cases, you can use the Azure portal to configure data collection, and Azure Monitor will create and manage the DCR for you. Other scenarios will require you to create your own DCR. You may also choose to customize an existing DCR to meet your required functionality.
 
-For example, the following diagram illustrates data collection for the [Azure Monitor agent](../agents/azure-monitor-agent-overview.md) running on a virtual machine. In this scenario, the DCR specifies events and performance data, which the agent uses to determine what data to collect from the machine and send to Azure Monitor. Once the data is delivered, the data pipeline runs the transformation specified in the DCR to filter and modify the data and then sends the data to the specified workspace and table. DCRs for other data collection scenarios may contain different information.
+For example, the following diagram illustrates data collection for the [Azure Monitor agent](../agents/azure-monitor-agent-overview.md) running on a virtual machine. In this scenario, the DCR specifies events and performance data to collect, which the agent uses to determine what data to collect from the machine and send to Azure Monitor. Once the data is delivered, the data pipeline runs the transformation specified in the DCR to filter and modify the data and then sends the data to the specified workspace and table. DCRs for other data collection scenarios may contain different information.
 
 :::image type="content" source="media/data-collection-rule-overview/overview-agent.png" lightbox="media/data-collection-rule-overview/overview-agent.png" alt-text="Diagram that shows basic operation for DCR using Azure Monitor Agent." border="false":::