Merge pull request #227712 from v-jbasden/jbasden-update-content-for-la-toc-update

Updating content based on new Log Analytics workspace ToC

Author: Court72

articles/azure-monitor/agents/agent-data-sources.md

@@ -36,7 +36,7 @@ The following table lists the agent data sources that are currently available wi
 
 ## Configure data sources
 
-To configure data sources for Log Analytics agents, go to the **Log Analytics workspaces** menu in the Azure portal and select a workspace. Select **Agents configuration**. Select the tab for the data source you want to configure. Use the links in the preceding table to access documentation for each data source and information on their configuration.
+To configure data sources for Log Analytics agents, go to the **Log Analytics workspaces** menu in the Azure portal and select a workspace. Select **Legacy agents management**. Select the tab for the data source you want to configure. Use the links in the preceding table to access documentation for each data source and information on their configuration.
 
 Any configuration is delivered to all agents connected to that workspace. You can't exclude any connected agents from this configuration.
 

articles/azure-monitor/agents/agent-linux-troubleshoot.md

@@ -78,7 +78,7 @@ A clean reinstall of the agent fixes most issues. This task might be the first s
  Extra configurations | `/etc/opt/microsoft/omsagent/<workspace id>/conf/omsagent.d/*.conf`
 
  > [!NOTE]
- > Editing configuration files for performance counters and Syslog is overwritten if the collection is configured from the [agent's configuration](../agents/agent-data-sources.md#configure-data-sources) in the Azure portal for your workspace. To disable configuration for all agents, disable collection from **Agents configuration**. For a single agent, run the following script:
+ > Editing configuration files for performance counters and Syslog is overwritten if the collection is configured from the [agent's configuration](../agents/agent-data-sources.md#configure-data-sources) in the Azure portal for your workspace. To disable configuration for all agents, disable collection from **Legacy agents management**. For a single agent, run the following script:
 >
 > `sudo /opt/microsoft/omsconfig/Scripts/OMS_MetaConfigHelper.py --disable && sudo rm /etc/opt/omi/conf/omsconfig/configuration/Current.mof* /etc/opt/omi/conf/omsconfig/configuration/Pending.mof*`
 

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

@@ -103,7 +103,7 @@ For the network requirements for the Linux agent, see [Log Analytics agent overv
 
 ### Workspace ID and key
 
-Regardless of the installation method used, you need the workspace ID and key for the Log Analytics workspace that the agent will connect to. Select the workspace from the **Log Analytics workspaces** menu in the Azure portal. Under the **Settings** section, select **Agents management**.
+Regardless of the installation method used, you need the workspace ID and key for the Log Analytics workspace that the agent will connect to. Select the workspace from the **Log Analytics workspaces** menu in the Azure portal. Under the **Settings** section, select **Agents**.
 
 [![Screenshot that shows workspace details.](media/log-analytics-agent/workspace-details.png)](media/log-analytics-agent/workspace-details.png#lightbox)
 

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

@@ -36,7 +36,7 @@ To download the latest version of the Windows agent from your Log Analytics work
 
 1. In your list of Log Analytics workspaces, select the workspace.
 
-1. In your Log Analytics workspace, select the **Agents Management** tile and then select **Windows Servers**.
+1. In your Log Analytics workspace, select the **Agents** tile and then select **Windows Servers**.
 
 1. On the **Windows Servers** screen, select the appropriate **Download Windows Agent** version to download depending on the processor architecture of the Windows operating system.
 

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

@@ -69,7 +69,7 @@ Configure .NET Framework 4.6 or later to support secure cryptography because by
 
 ### Workspace ID and key
 
-Regardless of the installation method used, you'll require the workspace ID and key for the Log Analytics workspace that the agent will connect to. Select the workspace from the **Log Analytics workspaces** menu in the Azure portal. Then in the **Settings** section, select **Agents management**.
+Regardless of the installation method used, you'll require the workspace ID and key for the Log Analytics workspace that the agent will connect to. Select the workspace from the **Log Analytics workspaces** menu in the Azure portal. Then in the **Settings** section, select **Agents**.
 
 [![Screenshot that shows workspace details.](media/log-analytics-agent/workspace-details.png)](media/log-analytics-agent/workspace-details.png#lightbox)
 

articles/azure-monitor/agents/data-sources-custom-logs.md

@@ -51,8 +51,8 @@ Use the following procedure to define a custom log file. Scroll to the end of th
 
 The Custom Log wizard runs in the Azure portal and allows you to define a new custom log to collect.
 
-1. In the Azure portal, select **Log Analytics workspaces** > your workspace > **Settings**.
-1. Select **Custom logs**.
+1. In the Azure portal, select **Log Analytics workspaces** > your workspace.
+1. Under the **Classic** section, select **Legacy custom logs**.
 1. By default, all configuration changes are automatically pushed to all agents. For Linux agents, a configuration file is sent to the Fluentd data collector.
 1. Select **Add** to open the Custom Log wizard.
 
@@ -114,7 +114,7 @@ The entire log entry will be stored in a single property called **RawData**. You
 
 Use the following process in the Azure portal to remove a custom log that you previously defined.
 
-1. From the **Data** menu in the **Advanced Settings** for your workspace, select **Custom Logs** to list all your custom logs.
+1. On the left, under the **Classic** section for your workspace, select **Legacy custom Logs** to list all your custom logs.
 1. Select **Remove** next to the custom log to remove the log.
 
 ## Data collection

articles/azure-monitor/agents/data-sources-performance-counters.md

@@ -16,7 +16,7 @@ Performance counters in Windows and Linux provide insight into the performance o
 ![Screenshot that shows performance counters.](media/data-sources-performance-counters/overview.png)
 
 ## Configure performance counters
-Configure performance counters from the [Agents configuration menu](../agents/agent-data-sources.md#configure-data-sources) for the Log Analytics workspace.
+Configure performance counters from the [Legacy agents management menu](../agents/agent-data-sources.md#configure-data-sources) for the Log Analytics workspace.
 
 When you first configure Windows or Linux performance counters for a new workspace, you're given the option to quickly create several common counters. They're listed with a checkbox next to each. Ensure that any counters you want to initially create are selected and then select **Add the selected performance counters**.
 

articles/azure-monitor/agents/data-sources-windows-events.md

@@ -17,13 +17,13 @@ Windows event logs are one of the most common [data sources](../agents/agent-dat
 
 ## Configure Windows event logs
 
-Configure Windows event logs from the [Agents configuration menu](../agents/agent-data-sources.md#configure-data-sources) for the Log Analytics workspace.
+Configure Windows event logs from the [Legacy agents management menu](../agents/agent-data-sources.md#configure-data-sources) for the Log Analytics workspace.
 
 Azure Monitor only collects events from Windows event logs that are specified in the settings. You can add an event log by entering the name of the log and selecting **+**. For each log, only the events with the selected severities are collected. Check the severities for the particular log that you want to collect. You can't provide any other criteria to filter events.
 
 As you enter the name of an event log, Azure Monitor provides suggestions of common event log names. If the log you want to add doesn't appear in the list, you can still add it by entering the full name of the log. You can find the full name of the log by using event viewer. In event viewer, open the **Properties** page for the log and copy the string from the **Full Name** field.
 
-[![Screenshot that shows the Windows event logs tab on the Agents configuration screen.](media/data-sources-windows-events/configure.png)](media/data-sources-windows-events/configure.png#lightbox)
+[![Screenshot that shows the Windows event logs tab on the Legacy agents management screen.](media/data-sources-windows-events/configure.png)](media/data-sources-windows-events/configure.png#lightbox)
 
 > [!IMPORTANT]
 > You can't configure collection of security events from the workspace by using the Log Analytics agent. You must use [Microsoft Defender for Cloud](../../security-center/security-center-enable-data-collection.md) or [Microsoft Sentinel](../../sentinel/connect-windows-security-events.md) to collect security events. The [Azure Monitor agent](azure-monitor-agent-overview.md) can also be used to collect security events.

articles/azure-monitor/agents/diagnostics-extension-logs.md

@@ -46,7 +46,7 @@ For information on how to install and configure the diagnostics extension, see [
 To enable collection of diagnostics extension data from an Azure Storage account:
 
 1. In the Azure portal, go to **Log Analytics Workspaces** and select your workspace.
-1. Select **Storage accounts logs** in the **Workspace Data Sources** section of the menu.
+1. Select **Legacy storage account logs** in the **Classic** section of the menu.
 1. Select **Add**.
 1. Select the **Storage account** that contains the data to collect.
 1. Select the **Data Type** you want to collect.

articles/azure-monitor/agents/log-analytics-agent.md

@@ -58,7 +58,7 @@ This section explains how to install the Log Analytics agent on different types
 - Log Analytics VM extension for [Windows](../../virtual-machines/extensions/oms-windows.md) or [Linux](../../virtual-machines/extensions/oms-linux.md) can be installed with the Azure portal, Azure CLI, Azure PowerShell, or an Azure Resource Manager template.
 - [Microsoft Defender for Cloud can provision the Log Analytics agent](../../security-center/security-center-enable-data-collection.md) on all supported Azure VMs and any new ones that are created if you enable it to monitor for security vulnerabilities and threats.
 - Install for individual Azure virtual machines [manually from the Azure portal](../vm/monitor-virtual-machine.md?toc=%2fazure%2fazure-monitor%2ftoc.json).
-- Connect the machine to a workspace from the **Virtual machines** option in the **Log Analytics workspaces** menu in the Azure portal.
+- Connect the machine to a workspace from the **Virtual machines (deprecated)** option in the **Log Analytics workspaces** menu in the Azure portal.
 
 ### Windows virtual machine on-premises or in another cloud