Merge pull request #5824 from MicrosoftDocs/phecke-auditing-update

Delete audit data using BulkDelete

Author: phecke

powerapps-docs/developer/data-platform/retrieve-and-delete-the-history-of-audited-data-changes.md

@@ -45,7 +45,63 @@ Refer to the sample link at the end of this topic for sample code that demonstra
 
  If your Dataverse server uses an Enterprise edition of SQL Server that does support partitioning, the <xref:Microsoft.Crm.Sdk.Messages.DeleteAuditDataRequest> request will delete all audit data in those partitions where the end date is before the date specified in the <xref:Microsoft.Crm.Sdk.Messages.DeleteAuditDataRequest.EndDate> property. Any empty partitions are also deleted. However, neither the current (active) partition nor the `audit` records in that active partition can be deleted by using this request or any other request.
 
- New partitions are automatically created by the Dataverse platform on a quarterly basis each year. This functionality is non-configurable and cannot be changed. You can obtain the list of partitions using the <xref:Microsoft.Crm.Sdk.Messages.RetrieveAuditPartitionListRequest> request. If the end date of any partition is later than the current date, you cannot delete that partition or any `audit` records in it.  
+ New partitions are automatically created by the Dataverse platform on a quarterly basis each year. This functionality is non-configurable and cannot be changed. You can obtain the list of partitions using the <xref:Microsoft.Crm.Sdk.Messages.RetrieveAuditPartitionListRequest> request. If the end date of any partition is later than the current date, you cannot delete that partition or any `audit` records in it.
+
+## Delete audit data flexibly using BulkDelete
+
+You can delete audit records your organization no longer needs to retain to comply with internal and external auditing requirements using the [BulkDelete](xref:Microsoft.Dynamics.CRM.BulkDelete) action in the Web API or the [BulkDelete](xref:Microsoft.Crm.Sdk.Messages.BulkDeleteRequest) message in the Organization Service. Deleting audit data using bulk delete will run in the background and allows you to define recurrence patterns, start time, and other parameters that help you to manage your bulk deletion jobs.
+
+### Basic audit bulk delete example
+
+This basic example deletes audit records of type 64 (User Access via Web) from the audit log. You can find the full list of audit actions in the [audit entity reference](reference/entities/audit.md) and modify your bulk delete job according to your needs.
+
+**Request**
+
+```http
+POST [Organization URI]/api/data/v9.1/BulkDelete HTTP/1.1  
+Accept: application/json  
+OData-MaxVersion: 4.0  
+OData-Version: 4.0  
+
+{
+  "QuerySet":
+      [
+        {
+          "EntityName": "audit",
+          "Criteria": {
+              "FilterOperator": "And",
+              "Conditions": [
+                  {
+                    "AttributeName": "action",
+                    "Operator": "Equal",
+                    "Values": [ {"Type": "System.String", "Value": "64"} ]
+                  }
+              ],
+              "Filters": []
+          }
+        }
+      ],
+      "JobName": "Bulk Delete of audit records with action = 64",
+      "SendEmailNotification": false,
+      "ToRecipients": [],
+      "CCRecipients": [],
+      "RecurrencePattern": "",
+      "StartDateTime": "2022-02-02T10:00:00.000Z"
+}
+```
+
+**Response**
+
+```HTTP
+HTTP/1.1 200 OK
+Content-Type: application/json; odata.metadata=minimal
+OData-Version: 4.0
+
+{
+  "@odata.context": "[Organization URI]/api/data/v9.0/$metadata#Microsoft.Dynamics.CRM.BulkDeleteResponse",
+  "JobId": "[Job Id]"
+}
+```
 
 ### See also