Compliance Problems

Fix SharePoint Retention Policy Not Creating Preservation Hold Files

Khadija KhanKhadija Khan Oct 26, 2026 869 views

Question details

Users report that a SharePoint retention policy stops generating files in the Preservation Hold Library after the policy has been disabled and then re-enabled.

Fix SharePoint Retention Policy Not Creating Preservation Hold Files
Product
SharePoint
Device & OS
not provided
Scenario
Administrators are trying to enforce data retention on SharePoint sites, but modified or deleted documents are no longer being preserved securely after toggling the policy.
Observed behavior
The Preservation Hold Library fails to create preserved copies of files. The compliance mechanisms appear inactive despite the policy being re-enabled.
Before you start

Ensure you have Microsoft 365 Compliance Administrator or Global Administrator privileges before attempting to modify or check retention policy scopes.

Solution 1Recommended

Verify Policy Status, Scope, and Apply a Test File

Check that the retention policy is correctly scoped to the affected sites and force a manual test to monitor the background processing.

When a retention policy is disabled and re-enabled, it must be re-processed by Microsoft 365 backend services. This can cause temporary disconnects in the scope of the policy applied to specific SharePoint sites.

1
Access the Compliance Portal

Log in to the Microsoft Purview compliance portal using your administrator credentials.

2
Check Policy Status

Navigate to 'Data lifecycle management' > 'Microsoft 365' > 'Retention policies'. Locate your specific policy and ensure its status is marked as 'Active' with no lingering errors.

3
Verify Site Scope

Edit the policy to confirm that the affected SharePoint sites are explicitly included in the 'Locations applied' configuration.

4
Modify a Test File

Go to one of the affected SharePoint sites, create a new document, and modify it. Delete the document to trigger the retention hold, then check the Preservation Hold Library after 24 hours to see if the file appears.

Verify Policy Status, Scope, and Apply a Test File
Processing Delays: Retention policies and holds can take up to 7 days to fully synchronize and process across all Microsoft 365 environments after being enabled or modified.
Free Microsoft Office alternative

Boost Your Productivity with WPS Office

While troubleshooting complex Microsoft 365 SharePoint admin policies, ensure your team has a reliable, lightweight, and hassle-free document editor for their daily tasks. WPS Office provides an all-in-one suite that is seamlessly compatible with your existing Office files.

  1. 1. Download the Installer: Visit the official WPS Office website and click the free download button for your operating system.
  2. 2. Install WPS Office: Run the downloaded installer and follow the simple on-screen instructions to set up the software in minutes.
  3. 3. Open Your Office Documents: Launch WPS Office and directly open your existing .docx, .xlsx, or .pptx files to start editing with full formatting support.
Fully compatible with Microsoft Word, Excel, and PowerPoint file formats.Lightweight software with fast startup times and minimal system requirements.Free to use with a familiar user interface, requiring zero learning curve.Built-in PDF editing capabilities directly inside the suite.
microsoft office alternative - wps office

Frequently Asked Questions

How long does it take for a SharePoint retention policy to take effect?

When you create, modify, or re-enable a retention policy in Microsoft 365, it can take anywhere from 24 hours to 7 days for the policy to fully apply across all selected SharePoint locations.

Who can view the Preservation Hold Library in SharePoint?

The Preservation Hold Library is intentionally hidden from regular users. Only users assigned the Site Collection Administrator role for that specific SharePoint site can view and access the contents of this library.

Why did disabling the retention policy break the hold library process?

Disabling a policy interrupts active Microsoft 365 background timer jobs. Re-enabling it requires the backend system to re-evaluate all items against the newly activated policy, which can cause temporary synchronization delays or glitches before files are successfully preserved again.

Can I manually force a retention policy to sync immediately?

No, Microsoft 365 relies on automated background timer jobs to process retention policies and eDiscovery holds. There is no manual button to force an immediate sync; administrators must wait for the background tasks to complete naturally.