fixes

Author: bwren

articles/azure-monitor/agents/data-collection-snmp-data.md

@@ -21,7 +21,7 @@ Azure Monitor agent can't collect SNMP data directly, but you can send this data
 - Syslog. The data is stored in the `Syslog` table with your other syslog data collected by Azure Monitor agent.
 - Text file. The data is stored in a custom table that you create. Using a transformation, you can parse the data and store it in a structured format.
 
-:::image type="content" source="media/data-collection-log-text/snmp-data-collection.png" lightbox="media/data-collection-log-text/snmp-data-collection.png" alt-text="Diagram showing collection of SNMP data by sending it to Syslog or a text file which is then collected by Azure Monitor agent.":::
+:::image type="content" source="media/data-collection-snmp-data/snmp-data-collection.png" lightbox="media/data-collection-snmp-data/snmp-data-collection.png" alt-text="Diagram showing collection of SNMP data by sending it to Syslog or a text file which is then collected by Azure Monitor agent.":::
 
 ## Prerequisites
 

articles/azure-monitor/includes/waf-vm-operation.md

@@ -22,7 +22,7 @@ ms.date: 03/23/2024
 |:---|:---|
 | Migrate from legacy agents to Azure Monitor agent. | The Azure Monitor agent is simpler to manage than the legacy Log Analytics agent and allows more flexibility in your [Log Analytics workspace design](). Both the Windows and Linux agents allow multihoming, which means they can connect to multiple workspaces. Data collection rules allow you to manage your data collection settings at scale and define unique, scoped configurations for subsets of machines. See [Migrate to Azure Monitor Agent from Log Analytics agent](../agents/azure-monitor-agent-migration.md) for considerations and migration methods. | 
 | Use Azure Arc to monitor your VMs outside of Azure. | [Azure Arc for servers](../../azure-arc/servers/overview.md) allows you to manage physical servers and virtual machines hosted outside of Azure, on your corporate network, or other cloud provider. With the [Azure Connected machine agent](../../azure-arc/servers/agent-overview.md) in place, you can deploy the Azure Monitor agent to these VMs using the same method that you do for your Azure VMs and then monitor your entire collection of VMs using the same Azure Monitor tools. |
-| Use Azure Policy to deploy agents and assign data collection rules. | [Azure Policy](../../governance/policy/overview.md) allows you to have agents automatically deployed to sets of existing VMs and any new VMs that are created. This ensures that all VMs are monitored with minimal intervention by administrators. If you use VM insights, see [Enable VM insights by using Azure Policy](../vm/vminsights-enable-policy.md). If you want to manage Azure Monitor agent without VM insights, see [Enable Azure Monitor Agent by using Azure Policy](../agents/azure-monitor-agent-manage.md#use-azure-policy). See [Manually create a DCR](../essentials/data-collection-rule-create-edit.md?tabs=arm#create-a-dcr) for a template to create a data collection rule association. |
+| Use Azure Policy to deploy agents and assign data collection rules. | [Azure Policy](../../governance/policy/overview.md) allows you to have agents automatically deployed to sets of existing VMs and any new VMs that are created. This ensures that all VMs are monitored with minimal intervention by administrators. If you use VM insights, see [Enable VM insights by using Azure Policy](../vm/vminsights-enable-policy.md). If you want to manage Azure Monitor agent without VM insights, see [Enable Azure Monitor Agent by using Azure Policy](../agents/azure-monitor-agent-policy.md). See [Manually create a DCR](../essentials/data-collection-rule-create-edit.md?tabs=arm#create-a-dcr) for a template to create a data collection rule association. |
 | Establish a strategy for structure of data collection rules. | Data collection rules define data to collect from virtual machines with the Azure Monitor agent and where to send that data. Each DCR can include multiple collection scenarios and be associated with any number of VMs. [Establish a strategy for configuring DCRs](../essentials/data-collection-rule-best-practices.md) to collect only required data for different groups of VMs while minimizing the number of DCRs that you need to manage. |
 | Consider migrating SCOM client management packs to Azure Monitor. | If you have an existing SCOM environment for monitoring client workloads, you may be able to migrate enough of the management pack logic to Azure Monitor to allow you to retire your SCOM environment, or at least to retire certain management packs. See [Migrate from System Center Operations Manager (SCOM) to Azure Monitor](../vm/monitor-virtual-machine-management-packs.md#migrate-management-pack-logic-for-vm-workloads). |
 

articles/azure-monitor/vm/monitor-virtual-machine-agent.md

@@ -56,7 +56,7 @@ The Azure Monitor agent is implemented as a [virtual machine extension](../../vi
 
 | Method | Scenarios | Details |
 |:---|:---|:---|
-| Azure Policy | Production deployment at scale | If you have a significant number of virtual machines, you should deploy the agent using Azure Policy as described in [Manage Azure Monitor Agent](../agents/azure-monitor-agent-manage.md?tabs=azure-portal#use-azure-policy) or [Enable VM insights by using Azure Policy](vminsights-enable-policy.md). This will ensure that the agent is automatically added to existing virtual machines and any new ones that you deploy. |
+| Azure Policy | Production deployment at scale | If you have a significant number of virtual machines, you should deploy the agent using Azure Policy as described in [Manage Azure Monitor Agent](../agents/azure-monitor-agent-policy.md) or [Enable VM insights by using Azure Policy](vminsights-enable-policy.md). This will ensure that the agent is automatically added to existing virtual machines and any new ones that you deploy. |
 | Data collection rule in Azure portal | Testing and simple deployments | When you create a data collection rule in the Azure portal as described in [Collect data with Azure Monitor Agent](../agents/azure-monitor-agent-data-collection.md), you have the option of specifying virtual machines to receive it. The Azure Monitor agent will be automatically installed on any machines that don't already have it. |
 | VM insights in Azure portal | Testing and simple deployments with preconfigured monitoring | VM insights provides [simplified onboarding of agents in the Azure portal](vminsights-enable-portal.md). With a single click for a particular machine, it installs the Azure Monitor agent, connects to a workspace, and starts collecting performance data. You can optionally have it install the dependency agent and collect processes and dependency data to enable the map feature of VM insights. |
 | Windows client installer | Client machines | Use the [Windows client installer](../agents/azure-monitor-agent-windows-client.md) to install the agent on Windows clients such as Windows 11. For different options deploying the agent on a single machine or as part of a script, see [Manage Azure Monitor Agent](../agents/azure-monitor-agent-manage.md?tabs=azure-portal#installation-options). |

articles/azure-monitor/vm/monitor-virtual-machine-data-collection.md

@@ -130,7 +130,7 @@ There are multiple reasons why you would want to create a DCR to collect guest p
 - Collect performance counters from other workloads running on your client.
 - Send performance data to [Azure Monitor Metrics](../essentials/data-platform-metrics.md) where you can use them with metrics explorer and metrics alerts.
 
-For guidance on creating a DCR to collect performance counters, see [Collect events and performance counters from virtual machines with Azure Monitor Agent](../agents/azure-monitor-agent-data-collection.md). You can quickly create a DCR by using the most common counters. For more granular filtering by criteria such as event ID, you can create a custom filter by using [XPath queries](../agents/data-collection-performance.md#filter-events-using-xpath-queries).
+For guidance on creating a DCR to collect performance counters, see [Collect events and performance counters from virtual machines with Azure Monitor Agent](../agents/azure-monitor-agent-data-collection.md). You can quickly create a DCR by using the most common counters. For more granular filtering by criteria such as event ID, you can create a custom filter by using [XPath queries](../agents/data-collection-windows-events.md#filter-events-using-xpath-queries).
 
 > [!NOTE]
 > You might choose to combine performance and event collection in the same DCR.