Merge pull request #261243 from DaleKoetke/docs-editor/personal-data-mgmt-1702570790

Update personal-data-mgmt.md

Author: v-dirichards

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

@@ -80,6 +80,7 @@ We __strongly__ recommend you restructure your data collection policy to stop co
 
 > [!IMPORTANT]
 >  While most purge operations complete much quicker, **the formal SLA for the completion of purge operations is set at 30 days** due to their heavy impact on the data platform. This SLA meets GDPR requirements. It's an automated process, so there's no way to expedite the operation. 
+
 ### View and export
 
 Use the [Log Analytics query API](/rest/api/loganalytics/dataaccess/query) or the [Application Insights query API](/rest/api/application-insights/query) for view and export data requests. 
@@ -97,6 +98,9 @@ Purge is a highly privileged operation. Grant the _Data Purger_ role in Azure Re
 
 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.
 
+> [!IMPORTANT]
+> Use of the Log Analytics or Application Insights Purge API does not affect your retention costs. To lower retention costs, you must decrease your data retention period.
+
 #### Log data
 
 * The [Workspace Purge POST API](/rest/api/loganalytics/workspacepurge/purge) takes an object specifying parameters of data to delete and returns a reference GUID.