When you use the OneDrive admin restore feature for a large team, you might find that restored files contain the wrong version. This happens because the restore operation targets the most recent version of a file at the time the restore is triggered, not the version that existed at the point of the incident. The admin restore feature is designed to revert all files in a user’s OneDrive to a previous state, but for large teams with frequent edits, the restore process can overwrite newer changes. This article explains why the wrong version appears and provides a checklist for admins to restore files accurately.
Key Takeaways: Restoring Files Without Version Conflicts for Large Teams
- Microsoft 365 admin center > OneDrive > Restore OneDrive: Reverts all files to a state up to 30 days in the past, but only if the user has not edited files after the restore point.
- OneDrive version history per file: Allows granular restoration of a single file to a specific version, avoiding overwriting other files.
- PowerShell cmdlet Restore-SPOSite: Provides scripted control over restore scope and timing for multiple users simultaneously.
Why OneDrive Admin File Restore Restores the Wrong Version for Large Teams
The OneDrive admin restore feature works by reverting the entire OneDrive of a user to a point in time that you specify. When you select a restore date and time, the system overwrites the current state of every file with the version that existed at that exact moment. For large teams, users often continue to edit files while the admin is preparing the restore. If a file was edited after the restore point, the restore overwrites those edits with the older version. This is not a bug — it is how the feature is designed. The admin restore does not merge changes or preserve newer versions of files that were not affected by the incident. The result is that users see the wrong version because their latest work is replaced.
Version Conflicts in Shared Libraries
When multiple team members collaborate on files in a shared OneDrive library, the restore point applies to all files uniformly. If one user edited a file minutes before the restore and another user’s file was corrupted, both files revert to the restore point. The admin cannot exclude specific files or users from the restore. This leads to lost changes that were unrelated to the original problem.
Time Zone and Delay Issues
The restore time is based on Coordinated Universal Time (UTC). If your team works in different time zones, a restore set for 2:00 PM UTC might revert files that were actively edited at 10:00 AM local time. Additionally, the restore process can take several hours for large teams, and files edited during that window can still be overwritten if the restore has not completed.
Admin Checklist for Accurate File Restore in Large Teams
Use this checklist to restore files without overwriting the wrong versions. Perform these steps in order.
- Identify the affected files and their correct versions
Before running any restore, ask the user which files contain the wrong data. Use OneDrive version history on each file to locate the version that should be restored. Write down the file names, the correct version timestamps, and the current version timestamps. - Notify the team to stop editing
Send a message to all team members who have access to the user’s OneDrive. Ask them to close all files in that library and not make any changes until the restore completes. This prevents new edits from being overwritten or conflicting with the restore. - Choose the correct restore method: per-file version history vs admin restore
If only a few files are affected, use per-file version history. Right-click the file in OneDrive, select Version history, and restore the correct version. This does not affect other files. If many files are affected, proceed with the admin restore. - Set the restore point to before the incident, not after
In the Microsoft 365 admin center, go to OneDrive > Restore OneDrive. Select a date and time that is before the corruption or deletion occurred. Do not set the restore point to a time after users made important edits. - Run the restore during off-peak hours
Schedule the restore for a time when the fewest team members are online, such as late evening or weekend. This reduces the chance that someone edits a file during the restore window. - Verify restored files immediately after completion
After the restore finishes, ask the affected user to check the files. Open the version history for each file to confirm that the restored version matches the expected one. If a file shows the wrong version, restore it individually using version history. - Restore accidentally overwritten files using version history
If the admin restore overwrote a file that had correct edits, navigate to that file, open Version history, and restore the version from after the restore point. This recovers the lost work without affecting other files.
If Files Still Show the Wrong Version After Admin Restore
OneDrive file restore completed but some files are missing
The admin restore only affects files that existed at the restore point. Files created after the restore point are not deleted, but they are not reverted either. If a file is missing, check the recycle bin in OneDrive. Files deleted before the restore point are not restored. Use version history on the parent folder to locate deleted items.
Version history shows the same version for all files
This happens when the restore point was set to a time when the files were already in the wrong state. For example, if the corruption happened on Monday and you restore to Tuesday, the files revert to the corrupted version. Always restore to a point before the incident. If the incident date is unknown, use the earliest available version from version history.
Team members report lost edits after restore
Edits made after the restore point are permanently overwritten by the admin restore. The only way to recover them is if the user had saved a separate copy or if the file’s version history still contains the newer version. If the restore overwrote the version history, the newer version is gone. To prevent this, always notify the team to stop editing before you run the restore.
Admin Restore vs Per-File Version History: Key Differences
| Item | Admin Restore | Per-File Version History |
|---|---|---|
| Scope | All files in the user’s OneDrive | Single file only |
| Time range | Up to 30 days in the past | All saved versions (up to 500) |
| Effect on other files | Overwrites all files to the restore point | No effect on other files |
| Recovery of lost edits | Edits after restore point are lost | Edits after restore point are preserved |
| Best for | Mass corruption, ransomware, or accidental deletion of many files | Restoring one or a few files to a specific version |
Use admin restore only when the incident affected a large number of files and you can confirm that no team members edited files after the restore point. For smaller incidents, use per-file version history to avoid overwriting unrelated changes.