Removed log analytics agent references

johnmarco · johnmarco · commit b67e1f3e0f53 · 2024-09-03T14:48:50.000-04:00
diff --git a/articles/azure-arc/servers/learn/quick-enable-hybrid-vm.md b/articles/azure-arc/servers/learn/quick-enable-hybrid-vm.md
@@ -96,7 +96,5 @@ After you install the agent and configure it to connect to Azure Arc-enabled ser
 
 Now that you've enabled your Linux or Windows hybrid machine and successfully connected to the service, you are ready to enable Azure Policy to understand compliance in Azure.
 
-To learn how to identify Azure Arc-enabled servers enabled machine that doesn't have the Log Analytics agent installed, continue to the tutorial:
-
 > [!div class="nextstepaction"]
 > [Create a policy assignment to identify non-compliant resources](tutorial-assign-policy-portal.md)
diff --git a/articles/azure-arc/servers/manage-automatic-vm-extension-upgrade.md b/articles/azure-arc/servers/manage-automatic-vm-extension-upgrade.md
@@ -2,7 +2,7 @@
 title: Automatic extension upgrade for Azure Arc-enabled servers
 description: Learn how to enable automatic extension upgrades for your Azure Arc-enabled servers.
 ms.topic: conceptual
-ms.date: 11/03/2023
+ms.date: 09/03/2024
 ---
 
 # Automatic extension upgrade for Azure Arc-enabled servers
@@ -55,7 +55,6 @@ Extension versions fixing critical security vulnerabilities are rolled out much
 Automatic extension upgrade supports the following extensions:
 
 - Azure Monitor agent - Linux and Windows
-- Log Analytics agent (OMS agent) - Linux only
 - Dependency agent – Linux and Windows
 - Azure Security agent - Linux and Windows
 - Key Vault Extension - Linux only
diff --git a/articles/azure-arc/servers/manage-vm-extensions-ansible.md b/articles/azure-arc/servers/manage-vm-extensions-ansible.md
@@ -1,7 +1,7 @@
 ---
 title: Enable VM extension using Red Hat Ansible
 description: This article describes how to deploy virtual machine extensions to Azure Arc-enabled servers running in hybrid cloud environments using Red Hat Ansible Automation.
-ms.date: 05/15/2023
+ms.date: 09/03/2024
 ms.topic: how-to
 ms.custom: devx-track-ansible
 ---
@@ -67,7 +67,6 @@ The project you created from the Azure Infrastructure Configuration Demo collect
 |---------|---------|
 |Microsoft Defender for Cloud integrated vulnerability scanner  |microsoft_defender  |
 |Custom Script extension  |custom_script  |
-|Log Analytics Agent  |log_analytics_agent  |
 |Azure Monitor for VMs (insights)  |azure_monitor_for-vms  |
 |Azure Key Vault Certificate Sync  |azure_key_vault  |
 |Azure Monitor Agent  |azure_monitor_agent  |
diff --git a/articles/azure-arc/servers/overview.md b/articles/azure-arc/servers/overview.md
@@ -11,7 +11,7 @@ Azure Arc-enabled servers lets you manage Windows and Linux physical servers and
 
 When a hybrid machine is connected to Azure, it becomes a connected machine and is treated as a resource in Azure. Each connected machine has a Resource ID enabling the machine to be included in a resource group.
 
-To connect hybrid machines to Azure, you install the [Azure Connected Machine agent](agent-overview.md) on each machine. This agent doesn't replace the Azure [Log Analytics agent](../../azure-monitor/agents/log-analytics-agent.md) / [Azure Monitor Agent](../../azure-monitor/agents/azure-monitor-agent-overview.md). The Log Analytics agent or Azure Monitor Agent for Windows and Linux is required in order to:
+To connect hybrid machines to Azure, you install the [Azure Connected Machine agent](agent-overview.md) on each machine. This agent doesn't replace the Azure [Azure Monitor Agent](../../azure-monitor/agents/azure-monitor-agent-overview.md). The Azure Monitor Agent for Windows and Linux is required in order to:
 
 * Proactively monitor the OS and workloads running on the machine
 * Manage it using Automation runbooks or solutions like Update Management
@@ -40,7 +40,7 @@ When you connect your machine to Azure Arc-enabled servers, you can perform many
   * Perform post-deployment configuration and automation tasks using supported [Arc-enabled servers VM extensions](manage-vm-extensions.md) for your non-Azure Windows or Linux machine.
 * **Monitor**:
   * Monitor operating system performance and discover application components to monitor processes and dependencies with other resources using [VM insights](../../azure-monitor/vm/vminsights-overview.md).
-  * Collect other log data, such as performance data and events, from the operating system or workloads running on the machine with the [Log Analytics agent](../../azure-monitor/agents/log-analytics-agent.md). This data is stored in a [Log Analytics workspace](../../azure-monitor/logs/log-analytics-workspace-overview.md).
+  * Collect other log data, such as performance data and events, from the operating system or workloads running on the machine with the [Azure Monitor Agent](../../azure-monitor/agents/azure-monitor-agent-overview.md). This data is stored in a [Log Analytics workspace](../../azure-monitor/logs/log-analytics-workspace-overview.md).
 
 > [!NOTE]
 > At this time, enabling Azure Automation Update Management directly from an Azure Arc-enabled server is not supported. See [Enable Update Management from your Automation account](../../automation/update-management/enable-from-automation-account.md) to understand requirements and [how to enable Update Management for non-Azure VMs](../../automation/update-management/enable-from-automation-account.md#enable-non-azure-vms).
diff --git a/articles/azure-arc/servers/plan-evaluate-on-azure-virtual-machine.md b/articles/azure-arc/servers/plan-evaluate-on-azure-virtual-machine.md
@@ -29,7 +29,7 @@ While you cannot install Azure Arc-enabled servers on an Azure VM for production
 
 To start managing your Azure VM as an Azure Arc-enabled server, you need to make the following changes to the Azure VM before you can install and configure Azure Arc-enabled servers.
 
-1. Remove any VM extensions deployed to the Azure VM, such as the Log Analytics agent. While Azure Arc-enabled servers support many of the same extensions as Azure VMs, the Azure Connected Machine agent can't manage VM extensions already deployed to the VM.
+1. Remove any VM extensions deployed to the Azure VM, such as the Azure Monitor agent. While Azure Arc-enabled servers support many of the same extensions as Azure VMs, the Azure Connected Machine agent can't manage VM extensions already deployed to the VM.
 
 2. Disable the Azure Windows or Linux Guest Agent. The Azure VM guest agent serves a similar purpose to the Azure Connected Machine agent. To avoid conflicts between the two, the Azure VM Agent needs to be disabled. Once it is disabled, you cannot use VM extensions or some Azure services.
 
diff --git a/articles/azure-arc/servers/private-link-security.md b/articles/azure-arc/servers/private-link-security.md
@@ -30,7 +30,7 @@ For more information, see  [Key Benefits of Private Link](../../private-link/pri
 
 Azure Arc Private Link Scope connects private endpoints (and the virtual networks they're contained in) to an Azure resource, in this case Azure Arc-enabled servers. When you enable any one of the Azure Arc-enabled servers supported VM extensions, such as Azure Monitor, those resources connect other Azure resources. Such as:
 
-- Log Analytics workspace, required for Azure Automation Change Tracking and Inventory, Azure Monitor VM insights, and Azure Monitor log collection with Log Analytics agent.
+- Log Analytics workspace, required for Azure Automation Change Tracking and Inventory, Azure Monitor VM insights, and Azure Monitor log collection with Azure Monitor agent.
 - Azure Automation account, required for Update Management and Change Tracking and Inventory.
 - Azure Key Vault
 - Azure Blob storage, required for Custom Script Extension.
