Skip to content

Commit b400d30

Browse files
Merge pull request #255830 from yossi-y/main
Added behavior for deleted solution table.
2 parents 7a4c1a1 + e141aa1 commit b400d30

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

articles/azure-monitor/logs/create-custom-table.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ ms.reviewer: adi.biran
77
ms.service: azure-monitor
88
ms.custom: devx-track-azurepowershell
99
ms.topic: how-to
10-
ms.date: 11/09/2022
10+
ms.date: 10/23/2023
1111
# Customer intent: As a Log Analytics workspace administrator, I want to create a table with a custom schema to store logs from an Azure or non-Azure data source.
1212
---
1313

@@ -140,7 +140,8 @@ Use the [Tables - Update PATCH API](/rest/api/loganalytics/tables/update) to cre
140140
You can delete any table in your Log Analytics workspace that's not an [Azure table](../logs/manage-logs-tables.md#table-type-and-schema).
141141

142142
> [!NOTE]
143-
> Deleting a restored table doesn't delete the data in the source table.
143+
> - Deleting a restored table doesn't delete the data in the source table.
144+
> - Azure tables that are part of a solution can be removed from workspace when [deleting the solution](https://learn.microsoft.com/cli/azure/monitor/log-analytics/solution?view=azure-cli-latest#az-monitor-log-analytics-solution-delete). The data remains in workspace for the duration of the retention policy defined for the tables. If the [solution is re-created](https://learn.microsoft.com/cli/azure/monitor/log-analytics/solution?view=azure-cli-latest#az-monitor-log-analytics-solution-create) in the workspace, these tables become visible again.
144145

145146
# [Portal](#tab/azure-portal-2)
146147

0 commit comments

Comments
 (0)