A colleague opens a quotation and sees yesterday's figures, while the person who edited it sees the latest version on their laptop. Both believe they are using the shared file. The immediate business risk is sending the wrong document, not simply an untidy sync icon.
When OneDrive reports pending changes or conflicting copies, first protect the work that exists only on a device. Then establish which account, library and file the team should use. This guide is for business OneDrive and SharePoint workflows, with Microsoft references checked on 11 October 2026.
Preserve the disputed work before trying a reset
Ask affected colleagues to stop editing the disputed file temporarily. Have each person save a clearly named copy of their current work to an approved, access-controlled location outside the affected sync folder. Record who made it and when. Confirm that the copy actually opens; a cloud-only placeholder is not an independent copy of the document.
Do not delete a duplicate because its filename looks wrong, and do not assume the most recent timestamp identifies the complete version. One person may have changed prices while another added delivery terms. The document owner should compare the content and decide how to combine those changes.
Microsoft's sync-pending guidance specifically cautions against deleting temporary files unless they are no longer needed: they can contain unsaved work. Blanket cache cleanup is a poor first response when the latest work has not been secured.
Separate a device problem from a shared-location problem
Open the intended OneDrive or SharePoint location in a browser using the correct work account. Compare its file with the local copy. Record the library URL, folder, filename and relevant error message. Do not paste confidential content into a public support forum.
- Browser copy opens, one device is behind: investigate that device's sync state and selected account.
- Several colleagues cannot open the same location: ask the administrator to check access and service health before changing individual computers.
- Only one file fails: investigate its name, path, application state and error details.
- Many unrelated files fail: examine sign-in, available storage and connection problems.
These are triage clues, not diagnoses. A browser test uses a different access path from the sync client. Success in the browser does not prove that desktop authentication or local storage is healthy.
Use the error to choose the next check
Open OneDrive's activity panel and read its current message. Microsoft's sync troubleshooting guide distinguishes paused sync, sign-in problems, storage limits and processing states. A missing icon can also mean that the application is not running. Do not treat every symptom as a slow internet connection.
For a file-specific error, compare the affected item against Microsoft's current naming, path and sync restrictions. Avoid changing a shared folder structure without checking links, application dependencies and colleagues' workflows.
If staff are repeatedly working from different copies, ITZ's Microsoft 365 setup and support service can review the account, library and device arrangement. Request a OneDrive Sync Review with the affected user count, file types and a sanitised error description.
Reconcile one important file before resuming normal work
Consider a hypothetical trading company whose sales and accounts teams have different quotation copies. Nominate one owner to compare both preserved versions, approve the final prices and terms, and place the agreed document in the correct shared location. Notify the team which link is authoritative.
- Verify the agreed file in the browser.
- Allow the affected device to finish syncing, then open the same file from its intended local folder.
- Make an approved, non-sensitive test change and confirm it appears through the other access path.
- Have an authorised colleague check the shared file from their own account.
- Retain the preserved copies until the owner confirms that no useful changes were lost.
If the problem persists, an administrator can choose an appropriate Microsoft-supported repair, including relinking or resetting where warranted. Capture the original configuration and protect local-only changes first. A repaired connection does not automatically reconcile conflicting business content.
Define what a successful repair means
Close the incident when representative files transfer correctly, colleagues use the intended location and the owner has approved the reconciled content. Record what failed and what changed. If the underlying problem is unclear folder ownership or inappropriate sharing, review the SharePoint handover checklist as a separate follow-up.
Successful synchronisation is not evidence that every recovery scenario is covered. Use a separate backup and restore test for recovery requirements. File history and available recovery options depend on the actual service configuration and circumstances.
Request a scoped OneDrive sync review
Tell ITZ which users and devices are affected, whether the browser copy is current, and whether the issue concerns one file or many. We can discuss a scope covering diagnosis, safe reconciliation, device checks and a clearer shared-file workflow. Do not send passwords or confidential documents through the enquiry form.
