Added TOC node per publishing team

Author: stevenmatthew

articles/storage-mover/TOC.yml

@@ -41,11 +41,11 @@ items:
   expanded: true
 - name: Resources
   items:
-  - name: Troubleshooting job run error codes
+  - name: Monitor copy and job run logs
+    href: log-monitoring.md
+  - name: Troubleshoot job run error codes
     href: status-code.md
   - name: Collect a support bundle
     href: troubleshooting.md
   - name: Release notes
     href: release-notes.md
-
-  

articles/storage-mover/log-monitoring.md

@@ -1,5 +1,5 @@
 ---
-title: Monitoring Copy Logs in Azure Storage Mover
+title: Monitor copy logs in Azure Storage Mover
 description: Learn how to monitor the status of Azure Storage Mover migration jobs.
 author: stevenmatthew
 ms.author: shaas
@@ -12,10 +12,10 @@ ms.date: 03/20/2023
 
 When you use a migration tool to move your critical data from on-premises sources to Azure destination targets, you want to be able to monitor operations for potential issues. The data relating to the operations performed during your migration can be stored as either logs entries or metrics. When configured, Azure Storage Mover can provide **Copy logs** and **Job run logs**. These logs are especially useful because they allow you to trace the migration result of job runs and of individual files.
 
-Both the copy and job run logs can be sent to an Azure Analytics Workspace. Analytics workspaces are storage units where log data generated by Azure services are stored. Log Analytics is also integrated into the Storage Mover portal experience. This integration allows you to create and run log queries from multiple logs and interactively analyze their results.
+Both the copy and job run logs can be sent to an Azure Analytics Workspace. Analytics workspaces are storage units where Azure services store the log data they generate. Log Analytics is integrated into the Storage Mover portal experience. This integration allows you to see the relevant logs for your copy jobs within the same surface you use to manage them. Perhaps more importantly, the integration also allows you to create and run log queries from multiple logs and interactively analyze their results.
 
 > [!IMPORTANT]
-> Before you can access your migration's log data, you need to ensure that you've created an Azure Analytics Workspace and configured your Storage Mover instance to use it. It's important to complete the steps described within this article before running your migration jobs to collect the resulting data. Any migration log data generated prior to configuration will not be accessible.
+> Before you can access your migration's log data, you need to ensure that you've created an Azure Analytics Workspace and configured your Storage Mover instance to use it. Any logs generated prior to this configuration will be lost. You may be able to retrieve limited log information directly from the agent.
 
 This article describes the steps involved in creating an analytics workspace and to configure a diagnostic setting within a storage mover resource.
 
@@ -25,7 +25,7 @@ This section briefly describes how to configure an Azure Monitor Log Analytics W
 
 ### Create a Log Analytics workspace
 
-Storage Mover collects copy and job logs, and stores the information in an Azure Log Analytics workspace. You can create multiple workspaces, but each workspace must have a unique workspace ID and resource ID for a given resource group. After you've created a workspace, you can configure Storage Mover to save its data there. If you don't have an existing workspace, you can quickly create one in the Azure portal.
+Storage Mover collects copy and job logs, and stores the information in an Azure Log Analytics workspace. After you've created a workspace, you can configure Storage Mover to save its data there. If you don't have an existing workspace, you can create one in the Azure portal.
 
 Enter **Log Analytics** in the search box and select **Log Analytics workspace**. In the content pane, select either **Create** or **Create log analytics workspace** to create a workspace. Provide values for the **Subscription**, **Resource Group**, **Name**, and **Region** fields, and select **Review + Create**.
 
@@ -57,7 +57,7 @@ All resource logs in Azure Monitor have the same fields, and are followed by ser
 
 Storage Mover generates two tables, StorageMoverCopyLogsFailed and StorageMoverJobRunLogs. The schema for **StorageMoverCopyLogsFailed** is found in the [Azure Storage Copy log data reference](/azure/azure-monitor/reference/tables/StorageMoverCopyLogsFailed), and the schema for **StorageMoverJobRunLogs** is found in the [Azure Storage Job run log data reference](/azure/azure-monitor/reference/tables/StorageMoverJobRunLogs).
 
-You log data is integrated into Storage Mover's Azure portal user interface (UI) experience. To access your log data, migrate to your top-level storage mover resource and select **Logs** from within the **Monitoring** group in the navigation pane. Close the initial **Welcome to Log Analytics** window displayed in the main content pane as shown in the following example.
+Your log data is integrated into Storage Mover's Azure portal user interface (UI) experience. To access your log data, migrate to your top-level storage mover resource and select **Logs** from within the **Monitoring** group in the navigation pane. Close the initial **Welcome to Log Analytics** window displayed in the main content pane as shown in the following example.
 
 :::image type="content" source="media/log-monitoring/logs-splash-sml.png" lightbox="media/log-monitoring/logs-splash-lrg.png" alt-text="This image illustrates the selections required to open the Logs pane and close the splash screen." :::
 
@@ -67,7 +67,7 @@ After the **Welcome** window is closed within the main content pane, the **New Q
 
 ```kusto
     StorageMoverCopyLogsFailed 
-    | where TimeGenerated > ago(60d)
+    | top 1000 by timeGenerated desc
 ```
 
 ### Sample Kusto queries