Forum Discussion

Nancy1415's avatar
Nancy1415
Copper Contributor
Jun 19, 2025

Purview Destruction of Records Not Working

Hi everyone, 

I work for a Microsoft Partner Organization, we are experiencing issues with our Purview Implementations as the records are not being destroyed from SharePoint as expected event though the audit log registered all successful approvals for destructions including details on the stages, the comments and the label.  We have waited 15 days as per the Purview's documentation and the content is still in the source library.  Is anyone else experiencing a similar issue?  The instability of the platform is forcing us to stop offering Purview as a solution to our customers and we are leaning more toward developing our own records  management solution. 

We have created a ticket, but Microsoft has not responded, there is no priority to resolve this issue and unfortunately our customers can't wait. 

If anyone has a solution, please share it with the community. If there are any  Purview experts from Microsoft that can offer any ideas, I would appreciate it. 

Note: Auditing is on for the organization and the email enabled security group and the Disposition Reviewers are in the correct roles: Disposition Reviewer, Records Management, Compliance Admin, List  View Explorer and Content Explorer.  Also, my configuration is set correctly, I have proof  as the audit log indicates content has been approved for destruction weeks ago. 

Thank you! 

purview

2 Replies

Sort By
  • Ankit365's avatar
    Ankit365
    Brass Contributor
    Jun 19, 2025

    After approval, Purview triggers a background “disposition job” to clean up items. These jobs can stall silently, especially in SharePoint environments, leaving items undeleted despite showing as “Approved” in the audit log. If a site or retention policy conflicts (e.g., Preservation Hold Library, other retention labels or holds), Purview won't delete the item, even if the disposition was approved, until those blockers are cleared.

    Ask Microsoft to review the backend compliance job queue (especially the “Pending Disposition” queue). If a backlog exists, manually restarting or escalating can help.
    Additionally, query the compliance details via the Graph API or SharePoint PnP to view the label status, record lock status, and internal expiration dates.

Resources