Skip to content

Commit be37e6a

Browse files
authored
Merge pull request #99188 from jack-cloud-platform/azure-monitor-data-purging-corrections
Azure Monitor: Data purging corrections: Permission and data access
2 parents 3a63806 + cdeb84a commit be37e6a

File tree

1 file changed

+2
-5
lines changed

1 file changed

+2
-5
lines changed

articles/azure-monitor/logs/personal-data-mgmt.md

Lines changed: 2 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -93,12 +93,9 @@ You need to implement the logic for converting the data to an appropriate format
9393
9494
Azure Monitor's Purge API lets you delete personal data. Use the purge operation sparingly to avoid potential risks, performance impact, and the potential to skew all-up aggregations, measurements, and other aspects of your Log Analytics data. See the [Strategy for personal data handling](#strategy-for-personal-data-handling) section for alternative approaches to handling personal data.
9595
96-
Purge is a highly privileged operation. Applications and Azure users, including the resource owner, can't execute a purge operation without explicitly being granted the _Data Purger_ role in Azure Resource Manager. Grant this role cautiously due to the potential for data loss.
96+
Purge is a highly privileged operation. Grant the _Data Purger_ role in Azure Resource Manager cautiously due to the potential for data loss.
9797
98-
To manage system resources, we limit purge requests to 50 requests an hour. Batch the execution of purge requests by sending a single command whose predicate includes all user identities that require purging. Use the [in operator](/azure/kusto/query/inoperator) to specify multiple identities. Run the query before executing the purge request to verify the expected results.
99-
100-
> [!NOTE]
101-
> After initiating a purge request, you cannot access the related data while the [purge operation status](/rest/api/loganalytics/workspacepurge/getpurgestatus) is *pending*.
98+
To manage system resources, we limit purge requests to 50 requests an hour. Batch the execution of purge requests by sending a single command whose predicate includes all user identities that require purging. Use the [in operator](/azure/kusto/query/inoperator) to specify multiple identities. Run the query before executing the purge request to verify the expected results.
10299
103100
#### Log data
104101

0 commit comments

Comments
 (0)