formatting update

Author: amsliu

support/azure/azure-monitor/log-analytics/configure-and-manage-log-analytics-tables/troubleshoot-custom-log-table-creation.md

@@ -11,37 +11,32 @@ ms.custom: Configure and Manage Log analytics tables
 
 When attempting to create a custom log table using a JSON file in Azure, users may encounter an error stating "Cannot read properties of undefined (reading length)". This issue typically arises during the final step of table creation, despite the JSON being valid. Understanding the root cause and following the correct steps can help resolve this problem.
 
-## Step-by-Step Instructions to Resolve the Issue
-
-### 1. Verify JSON Validity
-
-- Ensure that the JSON file being used is correctly formatted and valid. Use a JSON validator tool to confirm this.
-
-### 2. Create a New Data Collection Rule (DCR)
-
-- Navigate to the Azure portal and access the **Log Analytics Workspace**.
-- Create a new DCR specifically for the custom log table. Avoid using an existing DCR that collects other types of data, as this can lead to configuration conflicts.
-
-### 3. Use PowerShell Script for Table Creation
+## Common Issues and Solutions
 
-- Follow the steps outlined in the [Azure documentation](https://learn.microsoft.com/azure/azure-monitor/vm/data-collection-log-json#create-custom-table) to create the custom table using a PowerShell script.
-- This method allows you to specify the file pattern and verify the DCR configuration after creation.
+- **Error: Cannot read properties of undefined (reading length)**
+  - This error often indicates a problem with the JSON structure or the DCR configuration. Double-check both for accuracy.
 
-### 4. Check Contributor Role
+- **No Data Ingestion**
+  - Verify that the data source is correctly set up to collect log files. The data source type should be **Custom (Log files)**, and the stream declaration should follow the format `Custom-<TableName>`.
 
-- Ensure that you have at least the Contributor role in the relevant Azure Workspace to perform these actions.
+### Step-by-Step Instructions to Resolve the Issue
 
-### 5. Refresh the Portal
+1. **Verify JSON Validity**
+   - Ensure that the JSON file being used is correctly formatted and valid. Use a JSON validator tool to confirm this.
 
-- If issues persist, try refreshing the Azure portal to ensure all settings are updated.
+2. **Create a New Data Collection Rule (DCR)**
+   - Navigate to the Azure portal and access the **Log Analytics Workspace**.
+   - Create a new DCR specifically for the custom log table. Avoid using an existing DCR that collects other types of data, as this can lead to configuration conflicts.
 
-## Common Issues and Solutions
+3. **Use PowerShell Script for Table Creation**
+   - Follow the steps outlined in the [Azure documentation](https://learn.microsoft.com/azure/azure-monitor/vm/data-collection-log-json#create-custom-table) to create the custom table using a PowerShell script.
+   - This method allows you to specify the file pattern and verify the DCR configuration after creation.
 
-- **Error: Cannot read properties of undefined (reading length)**
-  - This error often indicates a problem with the JSON structure or the DCR configuration. Double-check both for accuracy.
+4. **Check Contributor Role**
+   - Ensure that you have at least the Contributor role in the relevant Azure Workspace to perform these actions.
 
-- **No Data Ingestion**
-  - Verify that the data source is correctly set up to collect log files. The data source type should be **Custom (Log files)**, and the stream declaration should follow the format `Custom-<TableName>`.
+5. **Refresh the Portal**
+   - If issues persist, try refreshing the Azure portal to ensure all settings are updated.
 
 ## Reference