When you use OneDrive for Business file restore for a large team site, you may find that the restored file is an older version than expected or a version that another user edited. This happens because the file restore feature in OneDrive for Business works on a per-user restore point, not a per-file version history. For team sites with multiple editors, the restore point you select may revert the file to a state that does not match the exact version you intended. This guide explains why the restore process picks the wrong version for large teams and provides the correct method to restore the exact file version you need.
Key Takeaways: Restoring the Correct Version in OneDrive for Business
- OneDrive admin center > Restore OneDrive: Use per-user restore points only when the file was last edited by that user — otherwise, version history is more precise.
- File version history (right-click > Version history): Shows every save from every team member; select the exact timestamp to restore the correct version.
- Site collection restore in SharePoint admin center: For large teams, restore the entire document library to a specific date and time to avoid partial or wrong version results.
Why OneDrive File Restore Picks the Wrong Version for Large Teams
The OneDrive for Business file restore feature does not restore a single file to a specific version. Instead, it restores the entire OneDrive or SharePoint document library to a restore point that represents the state of all files at a given date and time. For a team site where multiple users edit the same file, the restore point captures the last saved version before that point — but that version may have been saved by a different user than the one you expect. This is not a bug. It is the designed behavior of the restore point system, which works on a library-wide snapshot rather than per-file version history.
Additionally, OneDrive for Business creates restore points automatically every 12 hours and keeps them for up to 30 days. For large teams with frequent edits, a restore point may include edits from multiple users that were saved within the same 12-hour window. When you select a restore point, you get the entire library as it existed at that moment, not a single file version. If the file you need was edited by User A at 10:00 AM and then by User B at 11:30 AM, and the restore point is from 10:30 AM, the restored file will show User A’s version — even if you wanted User B’s version from later that day.
Steps to Restore the Correct File Version for a Large Team
To restore the exact version of a file that was edited by a specific team member, do not use the file restore feature directly. Instead, use file version history or a targeted library restore. Follow these steps in order.
- Identify the exact version you need
Ask the team member who made the desired edit to provide the date and time of their save. If they do not remember, check the file’s version history first: right-click the file in OneDrive or SharePoint, select Version history, and note the timestamps and editor names. - Restore a single file using version history
In the version history panel, locate the version with the correct timestamp and editor. Click the three dots next to that version and select Restore. This action restores only that file to that version, without affecting any other files in the library. This is the most precise method for large teams. - If version history does not show the version you need
Open the OneDrive admin center at admin.microsoft.com > SharePoint > Active sites. Select the site that contains the file. In the site settings, click Restore this library under Document Library. Choose a date and time range that matches the missing version. This restores the entire library, so coordinate with the team to avoid overwriting newer edits. - Use the file restore feature only as a last resort
If you must use the file restore feature for a large team, first create a separate document library or a backup copy of the current library. Then run the restore. After the restore, compare the restored file version with the version history to confirm the correct version was applied. If not, revert to the backup copy and restore the single file using version history. - Prevent future wrong-version restores
For files that multiple team members edit frequently, enable versioning limits in the library settings. Go to Library settings > Versioning settings and set a lower number of versions to keep, such as 50 or 100. This reduces the number of restore points and makes version history easier to navigate.
If the Restored Version Is Still Incorrect After Following the Steps
The file restore feature restored a version from a different user
This occurs when the restore point you selected includes edits from multiple users within the same time window. To fix this, do not repeat the restore. Instead, open the file’s version history, find the version from the correct user, and restore that single version. If the version history does not show the correct user’s version, the file may have been overwritten after the restore point. In that case, ask the user who made the desired edit to re-upload their version from their local copy.
The file restore feature restored an older version than expected
If the restored file is older than the version you wanted, the restore point you selected was too far back. Restore points are created every 12 hours, so the file may have been edited multiple times between the restore point and the version you need. Use version history to restore the exact version. If the version history does not show the version you need, the file may have been overwritten by a sync conflict. Check the Version history for a version labeled “Conflict” — that version may contain the correct content.
The file restore feature restored a version that is blank or corrupted
A blank or corrupted version usually indicates that the file was being edited at the exact moment the restore point was created. OneDrive may have captured an incomplete save. To recover, go to the file’s version history and restore the version immediately before the restore point. If that version is also corrupted, check the Recycle Bin for the site. The original file may still be there if it was deleted and not permanently removed.
File Restore vs Version History: Key Differences for Large Teams
| Item | File Restore (OneDrive admin center) | Version History (right-click) |
|---|---|---|
| Scope of restore | Entire library or OneDrive | Single file only |
| Granularity | Restore point every 12 hours | Every save by any user |
| Best for large teams | No — may restore wrong version | Yes — exact version per user |
| Time to complete | Minutes to hours | Seconds |
| Risk of overwriting other files | High | None |
For large teams, version history is the recommended method. Use file restore only when you need to recover the entire library after a ransomware attack or mass deletion.
You can now restore the correct file version for your team by using version history instead of the file restore feature. For files edited by multiple users, always check version history first. If you need to restore a large number of files at once, create a backup copy of the library before running file restore. As an advanced tip, set a retention label on the document library in the Microsoft 365 compliance center to preserve all versions for a specific period, which gives you more restore points to choose from.