When a former employee’s restored OneDrive lacks their final changes, investigate the handover evidence before choosing another restore date. The last working day, license-removal date and time of an unwanted file change are different events. None should be substituted for another without evidence.
Collect a precise handover record
Ask the responsible manager and administrator for the original OneDrive URL, the affected file paths, the expected changes, and the recovery actions already attempted. Record time zones and distinguish a user’s recollection of saving from a confirmed cloud version. Avoid relying on a single account-wide “last synced” time to explain every file.
For example, an employee may have completed a proposal on Friday while a colleague revised a related budget on Monday. A rollback to Thursday would not recover Friday’s writing and could also remove Monday’s valid work. Identify the specific missing proposal revision before touching the budget.
Resolve access problems separately
If the site cannot be opened, have an authorized administrator establish its actual state. License removal is not the event that starts the standard deleted-user cleanup process. Archived, retained and deleted OneDrives require different handling; consult Microsoft’s lifecycle documentation.
Do not enable the former employee’s sign-in or alter retention controls simply to investigate a file. Keep the offboarding security boundary intact. If a deleted site must be recovered, use the administrator recovery procedure, then assess document content. Site recovery does not select a particular paragraph revision.
Compare the cloud record with available copies
- For an accessible but outdated document, inspect available versions and locate the actual missing content.
- For a missing item, check its original storage location and deleted items, including administrator recovery options when needed.
- Preserve authorized local-only copies before reconnecting or resetting the former employee’s device.
- Compare recovered candidates in a separate working area. Do not overwrite the shared file until the business owner confirms which changes belong in it.
If the device is unavailable, document that gap and check approved backups or other authorized copies. Do not conclude that every missing change is permanently lost simply because one recovery route failed.
Avoid speculative second rollbacks
Choosing 23:59 on the day before license removal, or going back another seven days, is not a method for finding final edits. Use file-level recovery where possible. Any broader rollback needs a defined unwanted activity and independent preservation of current work outside its scope.
Keep an inventory of recovered files, source versions, destination locations and unresolved differences. Do not delete the former employee’s originals merely because a download succeeded. Transfer, access changes and eventual disposal should follow the organization’s approved offboarding and records process. Recovery is complete when the receiving owner has checked the contents and can open the agreed copies, not when a progress indicator reaches the end.