If a project loses recent edits after a OneDrive restore, start with the documents that are wrong, not another rollback. Establish whether each item is missing, contains an older version, or has newer work on a contributor’s device. Those problems need different recovery paths.
This guide covers work or school OneDrive. A project stored in a Teams channel or SharePoint library has a different storage owner and recovery scope. Verify the browser location before making changes.
Protect the project state you still need
Ask contributors to pause edits while you make a recovery list. For each important document, record its full path, the missing change, who made it, and when they last saw it. “The budget is old” is too vague; “the approved supplier cost in the September worksheet is missing” gives the reviewer something specific to test.
Preserve important current files and any local-only work in an approved location outside the OneDrive being restored. Open the copies to confirm they contain actual data. Another folder in the same drive does not provide an independent fallback. Do not reconnect a device containing the only newer copy until that copy is safe.
Recover the smallest affected set
- Open the correct project location in the browser and check whether the file still exists. Search for renamed or moved copies before assuming deletion.
- For an existing but outdated document, inspect Version history. Compare candidate content with the recovery list, then restore the verified version. Microsoft’s single-file recovery instructions describe the controls.
- For a missing document, check deleted items in the owning storage location. Ask the administrator to check the second-stage recycle bin when necessary.
- If neither path contains the edit, inspect authorized device copies and approved backups. An absent version is not proof that the edit was never uploaded: history may also have been removed.
Use a broad rollback only for a broad incident
Restore OneDrive affects the entire OneDrive, not just the open project folder. The built-in window is 30 days. Review the activities to undo; selecting the first unwanted activity also selects later activities. It is not a list of guaranteed 15-minute snapshots.
For example, if the team approved a budget at 14:00 and damaged it at 14:20, returning to a state before 14:00 cannot include that approval. Check the activity sequence and document content rather than subtracting an arbitrary half hour. If legitimate work continued after the damage, plan how to retain that work before confirming the rollback.
Check the result against project dependencies
Open the recovered documents from their intended shared location. Verify formulas, linked workbooks, embedded references and expected attachments where applicable. Have the contributor who reported the missing work check the exact change, not merely the file’s modified date.
Record unresolved files separately. Do not change storage quotas, trim version history or repeat a larger rollback to address an unexplained error. Send the administrator the file URL, operation time and exact error. Business version availability depends on configured version-history limits; it is not universally 500 versions kept for 30 days.