You might see a warning that a OneDrive restore request conflicts with your organization’s retention policies. This happens because Microsoft 365 retention settings can lock files from being altered or deleted during a restore operation. The conflict occurs when a user attempts to restore a OneDrive to a point in time that includes files already subject to a retention hold. This article explains why the conflict appears and provides the exact steps to resolve it from both the user and admin perspective.
Key Takeaways: OneDrive Restore Conflict With Retention Settings
- Microsoft Purview compliance portal > Data lifecycle management > Retention policies: Retention policies can block file modifications during a restore, causing the conflict error.
- OneDrive admin center > Restore OneDrive: The restore function cannot proceed if the target time range includes files under a retention hold.
- Microsoft 365 admin center > Users > Active users > OneDrive settings: Admins can temporarily exempt a user from a retention policy to allow the restore to complete.
Why OneDrive Restore Conflicts With Retention Settings
Microsoft 365 retention policies can preserve files for a specified period, preventing deletion or modification. When a user initiates a OneDrive restore, the system attempts to revert files to a state from an earlier date. If any file in that restore scope is currently under a retention hold that prohibits changes, the restore operation fails with a conflict error. The retention policy locks the file’s metadata and content, so the restore cannot overwrite or replace it.
The conflict can also arise if the retention policy is set to preserve files for a duration that extends beyond the restore point. For example, if a retention policy holds a file for three years and the restore point is two years ago, the system cannot modify that file until the hold expires or an admin removes the hold. This design protects data from accidental or malicious deletion, but it also blocks legitimate restores.
How Retention Policies Interact With OneDrive Restore
Retention policies in Microsoft 365 are applied at the site level or directly to a user’s OneDrive. When a restore is triggered, OneDrive checks each file against active retention holds. If a conflict is found, the entire restore operation stops and displays an error message. The error typically reads: “Restore conflicts with retention settings. Contact your admin.” The admin must then review the retention policy and decide to either exclude the user from the policy or wait for the hold to expire.
Steps to Resolve the OneDrive Restore Conflict
Resolving this conflict requires action from a Microsoft 365 admin. The steps below cover identifying the retention policy, temporarily removing the user from the policy, and completing the restore. Users without admin rights must contact their IT department.
- Open the Microsoft Purview compliance portal
Sign in to compliance.microsoft.com with a Global Admin or Compliance Admin account. Navigate to Data lifecycle management > Retention policies. - Identify the retention policy that applies to the user
In the list of retention policies, find the one that targets the user’s OneDrive. Click the policy name to open its details. Check the Locations section to confirm the user’s OneDrive URL is included. - Edit the retention policy to exclude the user
Click Edit policy. Under Locations, select Edit next to OneDrive accounts. Change the status from Included to Excluded for the specific user. Save the policy changes. This removal may take up to 24 hours to take effect. - Wait for the policy change to propagate
After excluding the user, wait for the retention hold to lift. You can check the status by using the Content search tool in the compliance portal to verify the files are no longer under hold. - Instruct the user to retry the OneDrive restore
The user should go to OneDrive on the web, click Settings (gear icon) > Restore your OneDrive, select the desired restore point, and confirm the operation. The restore should now complete without the conflict error. - Reapply the retention policy after the restore
Once the restore finishes, the admin should re-include the user in the original retention policy by editing it again. This ensures compliance requirements remain met.
If the Restore Still Fails After Excluding the User From the Policy
The retention policy change has not propagated yet
Policy changes can take up to 24 hours to apply across Microsoft 365. If the restore still fails immediately after editing the policy, wait for the propagation period. You can monitor the status in the compliance portal under Data lifecycle management > Retention policies > policy name > Status.
The user is part of a compliance or litigation hold
A compliance hold (also called a legal hold) can also block restores. Check if the user has a hold applied in the Microsoft Purview compliance portal under eDiscovery > eDiscovery (Standard) or eDiscovery (Premium). Remove the hold only if legally permissible.
The restore point includes files that are still under a separate retention label
Retention labels applied directly to files can also prevent modification. Use the Content search tool to find files with the label. The admin can remove the label from those files if the business requirement no longer exists.
OneDrive Restore vs Retention Policy: Key Differences
| Item | OneDrive Restore | Retention Policy |
|---|---|---|
| Purpose | Revert files to a previous state | Preserve files for compliance or legal reasons |
| Who can trigger | User or admin | Admin only |
| Effect on files | Modifies or replaces file versions | Blocks deletion or modification |
| Conflict scenario | Fails if any file is under retention hold | Prevents restore from completing |
| Resolution | Exclude user from retention policy | Remove hold or wait for expiry |
The main difference is that OneDrive restore is a user-driven recovery action, while retention policies are administrative safeguards. They conflict when a restore attempts to change files that the policy protects.
You can now resolve the OneDrive restore conflict by identifying the retention policy and excluding the affected user. After the restore completes, remember to reapply the policy to maintain compliance. For advanced control, consider using retention labels with shorter durations for files that may need frequent restores.