Skip to content

Commit 1c3381b

Browse files
committed
Revert "Update immediatePurgeDataOn30Days"
This reverts commit 4734fed.
1 parent ef20afd commit 1c3381b

File tree

1 file changed

+7
-5
lines changed

1 file changed

+7
-5
lines changed

articles/azure-monitor/logs/data-retention-archive.md

Lines changed: 7 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Data retention and archive in Azure Monitor Logs
33
description: Configure archive settings for a table in a Log Analytics workspace in Azure Monitor.
44
ms.reviewer: adi.biran
55
ms.topic: conceptual
6-
ms.date: 3/31/2024
6+
ms.date: 6/28/2023
77
# Customer intent: As an Azure account administrator, I want to set data retention and archive policies to save retention costs.
88
---
99

@@ -240,12 +240,14 @@ Get-AzOperationalInsightsTable -ResourceGroupName ContosoRG -WorkspaceName Conto
240240

241241
## Purge retained data
242242

243-
If you need to retain data for 30 days for privacy compliance, [configure workspace retention](#configure-the-default-workspace-retention) to 30 days, then update workspace property `immediatePurgeDataOn30Days` to `true` using [REST](https://learn.microsoft.com/rest/api/loganalytics/workspaces/update). This operation isn't supported in CLI, PowerShell, and portal currently.
243+
If you set the data retention to 30 days, you can purge older data immediately by using the `immediatePurgeDataOn30Days` parameter in Azure Resource Manager. The purge functionality is useful when you need to remove personal data immediately. The immediate purge functionality isn't available through the Azure portal.
244244

245-
> [!IMPORTANT]
246-
> - You can purge privacy data from workspace by using [Purge feature](personal-data-mgmt.md#exporting-and-deleting-personal-data). The purge functionality isn't supported on data in archive.
247-
> - The Log Analytics [Purge feature](/rest/api/loganalytics/workspacepurge/purge) doesn't affect retention costs. To lower retention costs, reduce retention period for the workspace, or for certain tables.
245+
Workspaces with a 30-day retention might keep data for 31 days if you don't set the `immediatePurgeDataOn30Days` parameter.
246+
247+
You can also purge data from a workspace by using the [purge feature](personal-data-mgmt.md#exporting-and-deleting-personal-data), which removes personal data. You can't purge data from archived logs.
248248

249+
> [!IMPORTANT]
250+
> The Log Analytics [Purge feature](/rest/api/loganalytics/workspacepurge/purge) doesn't affect your retention costs. To lower retention costs, decrease the retention period for the workspace or for specific tables.
249251
250252
## Tables with unique retention periods
251253

0 commit comments

Comments
 (0)