Share via

Purview disposition not triggered for SPO documents even after 15 days post-approval

Yen Chan 0 Reputation points
2024-12-23T17:31:47.2366667+00:00

The Context:

Our organization is currently testing disposition of content that was applied a retention label via a Graph API endpoint (driveItem: setRententionLabel). This is the configuration for the retention label file plan:

User's image

The reasoning behind labeling our documents as "Record" is because we would like to have proof of disposition once the document is destroyed by Purview:

User's image

Additionally, this file plan has been applied to several auto-apply label policies as well. The policies are set in the same SPO site as our Graph API testing scenario here. However, I don't believe that matters anyways since in the endpoint documentation, it clearly states that "(r)etention labels don't need to be published in a retention label policy to be applied using this method":

User's image

The Problem:

We were able to successfully apply the retention label, and the items predictably proceed to disposition review after retention period is complete (2 days). Our reviewers then approved the disposition. However, Purview has not yet delete the items, even after the maximum 15 days post-approval window:

User's image

Any insight as to why Purview seems quite inconsistent and unreliable in its disposition process is greatly appreciated, thank you.

SharePoint
SharePoint
A group of Microsoft Products and technologies used for sharing and managing content, knowledge, and applications.
11,004 questions
Microsoft Purview
Microsoft Purview
A Microsoft data governance service that helps manage and govern on-premises, multicloud, and software-as-a-service data. Previously known as Azure Purview.
1,304 questions

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. phemanth 12,655 Reputation points Microsoft Vendor
    2024-12-23T20:42:30.05+00:00

    @Yen Chan

    Thanks for the question and using MS Q&A platform.

    Please check the below steps and confirm us so that we can rule out below checks to move further

    1. Permissions: Ensure that the users involved in the disposition process have the necessary permissions. They should have the Disposition Management role Without this role, the disposition process might not complete as expected
    2. Audit Logs: Check the audit logs to see if there are any errors or warnings related to the disposition process. This can provide insights into what might be going wrong
    3. Configuration Issues: Verify that the retention label and the disposition review settings are correctly configured. Sometimes, minor misconfigurations can lead to significant issues
    4. System Delays: There might be delays in the system due to high load or other internal processes. Although 15 days is quite long, it's worth considering if there are any ongoing issues or maintenance activities
    5. Manual Intervention: In some cases, manual intervention might be required to trigger the disposition process. This can be done through the Purview portal

    I hope the above steps will resolve the issue, please do let us know if issue persists. Thank you

    1 person found this answer helpful.
    0 comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.