You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
title: Troubleshoot Deleting Migrated Custom Tables in Log Analytics
3
+
description: Step-by-step guide on how to resolve issues with deleting migrated custom tables in Log Analytics.
4
+
ms.date: 07/16/2025
5
+
ms.reviewer: v-liuamson; v-gsitser
6
+
ms.service: azure-monitor
7
+
ms.custom: Configure and Manage Log analytics tables
8
+
---
9
+
10
+
# Troubleshoot Deleting Migrated Custom Tables in Log Analytics
11
+
12
+
When attempting to delete a custom log table in Log Analytics, users may encounter issues due to the table being migrated. This guide provides a solution to effectively resolve this problem.
13
+
14
+
## Common Issues and Solutions
15
+
16
+
-**API Access Issues**: Ensure you have the necessary permissions to use the API.
17
+
-**Table Not Found**: Confirm the correct table name and workspace details.
18
+
19
+
### Solution: Use Azure Log Analytics API
20
+
21
+
To delete a migrated custom table, follow these steps using the Azure Log Analytics API:
22
+
23
+
1.**Access Azure Portal**: Navigate to the [Azure Portal](https://portal.azure.com) and login to your Azure account.
24
+
2.**Locate Log Analytics Workspace**: Access the **Log Analytics workspaces** section and select the workspace containing the table you wish to delete.
25
+
3.**Use API for Deletion**: Use the **Tables - Delete** API to remove the table. Refer to the [Azure Log Analytics API documentation](https://learn.microsoft.com/azure/azure-monitor/logs/api/tables-delete) for detailed instructions.
26
+
4.**Verify Deletion**: After executing the API call, confirm that the table has been successfully deleted by checking the workspace.
27
+
28
+
## Reference
29
+
30
+
-[Azure Log Analytics API Documentation](https://learn.microsoft.com/azure/azure-monitor/logs/api/tables-delete)
31
+
32
+
If the issue persists after following the solution steps, please open a support case for further assistance.
0 commit comments