fixes

Author: EdB-MSFT

articles/azure-monitor/agents/agents-overview.md

@@ -57,7 +57,7 @@ Azure Monitor Agent uses [data collection rules](../essentials/data-collection-r
 
     | Resource type | Installation method | More information |
     |:---|:---|:---|
-    | Virtual machines and VM scale sets | [Virtual machine extension](./azure-monitor-agent-manage.md#virtual-machine-extension-details) | Installs the agent by using Azure extension framework. |
+    | Azure Virtual Machines and Azure Virtual Machine Scale Sets | [Virtual machine extension](./azure-monitor-agent-manage.md#virtual-machine-extension-details) | Installs the agent by using Azure extension framework. |
     | On-premises Arc-enabled servers | [Virtual machine extension](./azure-monitor-agent-manage.md#virtual-machine-extension-details) (after installing the [Azure Arc agent](../../azure-arc/servers/deployment-options.md)) | Installs the agent by using Azure extension framework, provided for on-premises by first installing [Azure Arc agent](../../azure-arc/servers/deployment-options.md). |
     | Windows 10, 11 Client Operating Systems | [Client installer](./azure-monitor-agent-windows-client.md) | Installs the agent by using a Windows MSI installer. The installer works on laptops, but the agent *isn't optimized yet* for battery or network consumption. |
 
@@ -239,7 +239,7 @@ View [supported operating systems for Azure Arc Connected Machine agent](../../a
 > Machines and appliances that run heavily customized or stripped-down versions of the above distributions and hosted solutions that disallow customization by the user are not supported. Azure Monitor and legacy agents rely on various packages and other baseline functionality that is often removed from such systems, and their installation may require some environmental modifications considered to be disallowed by the appliance vendor. For instance, [GitHub Enterprise Server](https://docs.github.com/en/enterprise-server/admin/overview/about-github-enterprise-server) is not supported due to heavy customization as well as [documented, license-level disallowance](https://docs.github.com/en/enterprise-server/admin/overview/system-overview#operating-system-software-and-patches) of operating system modification.
 
 > [!NOTE]
-> CBL-Mariner 2.0's disk size is by default around 1GB to provide storage savings, compared to other Azure VMs that are around 30GB. However, the Azure Monitor Agent requires at least 4GB disk size in order to install and run successfully. Please check out [CBL-Mariner's documentation](https://eng.ms/docs/products/mariner-linux/gettingstarted/azurevm/azurevm#disk-size) for more information and instructions on how to increase disk size before installing the agent.
+> CBL-Mariner 2.0's disk size is by default around 1GB to provide storage savings, compared to other Azure Virtual Machines that are around 30GB. However, the Azure Monitor Agent requires at least 4GB disk size in order to install and run successfully. Please check out [CBL-Mariner's documentation](https://eng.ms/docs/products/mariner-linux/gettingstarted/azurevm/azurevm#disk-size) for more information and instructions on how to increase disk size before installing the agent.
 
 ### Linux Hardening Standards
 

articles/azure-monitor/agents/azure-monitor-agent-migration-dcr-generator.md renamed to articles/azure-monitor/agents/azure-monitor-agent-migration-data-collection-rule-generator.md

@@ -11,7 +11,7 @@ ms.date: 06/16/2024
 
 ---
 
-# Convert workspace configuration to DCR configurations.
+# Convert workspace configuration to DCR configurations
 
 Whereas Log Analytics Agent inherits its configuration from Log Analytics workspaces, the Azure Monitor Agent relies on data collection rules (DCRs) for configuration
 

articles/azure-monitor/agents/azure-monitor-agent-migration-helper-workbook.md

@@ -29,7 +29,7 @@ This page provides a high-level view of the resources in your subscriptions, whi
 On the subscriptions overview tab, the workbook automatically detects the following resources:
 - Subscriptions 
 - Workspaces
-- Azure VMs
+- Azure Virtual Machiness
 - Virtual Machine Scale Sets
 - Arc-enabled servers
 - Hybrid machines without Arc where the legacy agent is deployed
@@ -60,9 +60,9 @@ The following image shows the migration status table with the following statuses
 
   :::image type="content" source="./media/azure-monitor-agent-migration-helper-workbook/migration-status.png" lightbox="./media/azure-monitor-agent-migration-helper-workbook/migration-status.png" alt-text="A screenshot showing the migration status table.":::
 
-### Azure Virtual Machines, VM Scale Sets, and Arc-enabled servers tabs
+### Azure Virtual Machines, Azure Virtual Machine Scale Sets, and Arc-enabled servers tabs
 
-The Azure Virtual Machines and Scale Sets tabs provides a detailed view of the Azure VMs, VM scale sets and Arc-enabled serves in your subscriptions. These machines are listed regardless of the workspace to which they send telemetry. 
+The Azure Virtual Machines and Scale Sets tabs provides a detailed view of the Azure Virtual Machines, Virtual Machine Scale Sets and Arc-enabled serves in your subscriptions. These machines are listed regardless of the workspace to which they send telemetry. 
 The table provides a view of the migration status is per machine showing which agents are deployed, the last time a heartbeat was sent to one of your workspaces, and the migration status. 
 
  :::image type="content" source="./media/azure-monitor-agent-migration-helper-workbook/azure-virtual-machines-tab.png" lightbox="./media/azure-monitor-agent-migration-helper-workbook/azure-virtual-machines-tab.png" alt-text="A screenshot showing the Azure Virtual Machines migration status tab.":::

articles/azure-monitor/agents/azure-monitor-agent-migration.md

@@ -32,16 +32,16 @@ To monitor non-Azure and on-premises servers, you must install the Azure Arc age
 - Verify that Azure Monitor Agent can address all of your needs. Azure Monitor Agent is General Availability (GA) for data collection and is used for data collection by various Azure Monitor features and other Azure services.
 -  Verify that you have the necessary permissions to install the Azure Monitor Agent. You must have the necessary permissions to install the agent on the machines you want to monitor. For more information, see [Permissions required to install the Azure Monitor Agent](/azure/azure-monitor/agents/azure-monitor-agent-manage#permissions-required-to-install-the-azure-monitor-agent).
 
-## High level guidance.
+## High level guidance
 
 Use the following guidance to plan and execute your migration:
 
-1. Understand your agents and how many you have to migrate.
-1. Understand how you're using your workspaces.
-1. Understand which solutions, insights, and data collections that are configured.
-1. Configure your data collections and validate the collections.
-1. Understand additional dependencies and services.
-1. Remove the legacy agents.
+- Understand your agents and how many you have to migrate.
+- Understand how you're using your workspaces.
+- Understand which solutions, insights, and data collections that are configured.
+- Configure your data collections and validate the collections.
+- Understand additional dependencies and services.
+- Remove the legacy agents.
 
 The **Azure Monitor Agent Migration Helper** workbook is a workbook-based Azure Monitor solution that can help you at each of the steps outlined above. This guide references the workbook and other tools at each stage of the migration process. For more information, see [Azure Monitor Agent Migration Helper workbook](./azure-monitor-agent-migration-helper-workbook.md).
 
@@ -67,13 +67,13 @@ When looking at your workspaces, note which solutions are configured. This infor
 
 The Azure Monitor Agent Migration Helper Workbook can help you understand which workspaces you have, and the solutions implemented in each workspace, and when you last used the solution. Each solution has a migration recommendation. For more information, see [Azure Monitor Agent migration helper workbook- Workspaces](./azure-monitor-agent-migration-helper-workbook.md#workspaces)
 
-You can also the Azure Monitor Workspace Auditing workbook to help you understand your workspaces.  To use the Azure Monitor Workspace Auditing workbook, copy the workbook from the [GitHub repository](https://github.com/microsoft/AzureMonitorCommunity/blob/master/Azure%20Services/Log%20Analytics%20workspaces/Workbooks/Workspace%20Audit.json) and import it into your Log Analytics workspace. 
+You can also use the Azure Monitor Workspace Auditing workbook to help you understand your workspaces.  To use the Azure Monitor Workspace Auditing workbook, copy the workbook from the [GitHub repository](https://github.com/microsoft/AzureMonitorCommunity/blob/master/Azure%20Services/Log%20Analytics%20workspaces/Workbooks/Workspace%20Audit.json) and import it into your Log Analytics workspace. 
 
 This workbook collects all of your Log Analytics workspaces and shows you the following for each workspace:
-1. All data sources that are sending data to the workspace.
-1. The agents that are sending heartbeats to the workspace. 
-1. The resources that are sending data to the workspace.
-1. Any Application Insights resources that are sending data to the workspace.
+- All data sources that are sending data to the workspace.
+- The agents that are sending heartbeats to the workspace. 
+- The resources that are sending data to the workspace.
+- Any Application Insights resources that are sending data to the workspace.
 
 For more information, see [Azure Monitor Workspace Auditing workbook](./azure-monitor-agent-migration-helper-workbook.md#workspace-auditing-workbook).
 
@@ -82,14 +82,14 @@ For more information, see [Azure Monitor Workspace Auditing workbook](./azure-mo
 
 When configuring your data collections, consider the following steps:
 
-1. Identify a pilot group of servers that you can use for this process. Use the pilot servers to validate the data before you deploy at scale.
+- Identify a pilot group of servers that you can use for this process. Use the pilot servers to validate the data before you deploy at scale.
 
-1. Use the DCR Config Generator to transform the data collections that are configured in the workspace and deploy them as data collection rules back into your environment. For more information on the DCR Config Generator, see [DCR Config Generator](./azure-monitor-agent-migration-dcr-generator.md).
-1. Migrate VM Insights or Azure Monitor for Virtual Machines to the Azure Monitor Agent. Validate the migrated data collections for the pilot group of servers compared with what was collected before migration. To avoid double ingestion, you can disable data collection from legacy agents during the testing phase without uninstalling the agents yet, by removing the workspace configurations for legacy agents. For more information, see [Log Analytics agent data sources in Azure Monitor](/azure/azure-monitor/agents/agent-data-sources#configure-data-sources)
+- Use the DCR Config Generator to transform the data collections that are configured in the workspace and deploy them as data collection rules back into your environment. For more information on the DCR Config Generator, see [DCR Config Generator](./azure-monitor-agent-migration-data-collection-rule-generator.md).
+- Migrate VM Insights or Azure Monitor for Virtual Machines to the Azure Monitor Agent. Validate the migrated data collections for the pilot group of servers compared with what was collected before migration. To avoid double ingestion, you can disable data collection from legacy agents during the testing phase without uninstalling the agents yet, by removing the workspace configurations for legacy agents. For more information, see [Log Analytics agent data sources in Azure Monitor](/azure/azure-monitor/agents/agent-data-sources#configure-data-sources)
 
-1. Validate the new data to ensure there are no gaps. Compare the data ingested by legacy agent data to Azure Monitor Agent. Use KQL to compare equivalent data from each agent based on agent type.
+- Validate the new data to ensure there are no gaps. Compare the data ingested by legacy agent data to Azure Monitor Agent. Use KQL to compare equivalent data from each agent based on agent type.
 
-1. Plan deployment at scale using Azure policy. Use built-in policies to deploy extensions and DCR associations at scale. Using policy also ensures automatic deployment of extensions and DCR associations for new machines. For more information on deploying at scale, see [Manage Azure Monitor Agent - Use Azure policies](/azure/azure-monitor/agents/azure-monitor-agent-manage#use-azure-policy).
+- Plan deployment at scale using Azure policy. Use built-in policies to deploy extensions and DCR associations at scale. Using policy also ensures automatic deployment of extensions and DCR associations for new machines. For more information on deploying at scale, see [Manage Azure Monitor Agent - Use Azure policies](/azure/azure-monitor/agents/azure-monitor-agent-manage#use-azure-policy).
 
 
 
@@ -128,5 +128,5 @@ A SCOM Admin Management Pack exists and can help you remove the workspace config
 ## Next steps
 
 - [Azure Monitor Agent migration helper workbook](./azure-monitor-agent-migration-helper-workbook.md)
-- [DCR Config Generator](./azure-monitor-agent-migration-dcr-generator.md)
+- [DCR Config Generator](./azure-monitor-agent-migration-data-collection-rule-generator.md)
 - [MMA Discovery and Removal tool](/azure/azure-monitor/agents/azure-monitor-agent-mma-removal-tool?tabs=single-tenant%2Cdiscovery)

articles/azure-monitor/agents/media/azure-monitor-agent-migration-helper-workbook/automation-update-management.png

@@ -741,7 +741,7 @@ items:
         - name: AMA migration helper workbook  
           href: agents/azure-monitor-agent-migration-helper-workbook.md
         - name: DCR Config Generator
-          href: agents/azure-monitor-agent-migration-dcr-generator.md 
+          href: agents/azure-monitor-agent-migration-data-collection-rule-generator.md 
         - name: MMA removal tool
           href: agents/azure-monitor-agent-mma-removal-tool.md
         - name: Migration custom text log tables