Skip to content

Commit 1fe2cc9

Browse files
Merge pull request #224388 from yossi-y/main
Updated shortening retention data
2 parents 914616d + 1c5f0ca commit 1fe2cc9

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

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

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -30,6 +30,8 @@ You can access archived data by [running a search job](search-jobs.md) or [resto
3030
> [!NOTE]
3131
> The archive period can only be set at the table level, not at the workspace level.
3232
33+
When you shorten an existing retention policy, it takes 30 days for Azure Monitor to remove data, to prevent data loss in error configuration, and let you revert it. You can [purge data](#purge-retained-data) immediately when required.
34+
3335
## Configure the default workspace retention policy
3436

3537
You can set the workspace default retention policy in the Azure portal to 30, 31, 60, 90, 120, 180, 270, 365, 550, and 730 days. You can set a different policy for specific tables by [configuring the retention and archive policy at the table level](#set-retention-and-archive-policy-by-table). If you're on the *free* tier, you'll need to upgrade to the paid tier to change the data retention period.
@@ -215,8 +217,6 @@ Get-AzOperationalInsightsTable -ResourceGroupName ContosoRG -WorkspaceName Conto
215217

216218
## Purge retained data
217219

218-
When you shorten an existing retention policy, it takes several days for Azure Monitor to remove data that you no longer want to keep.
219-
220220
If you set the data retention policy 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.
221221

222222
Workspaces with a 30-day retention policy might keep data for 31 days if you don't set the `immediatePurgeDataOn30Days` parameter.

0 commit comments

Comments
 (0)