Microsoft 365 files missing or not syncing? Find the source before changing the copies.

Ask the actual file/site owner whether the folder moved, was deleted, was renamed or is no longer shared with the intended identity. Check the organisation and any guest identity on the invitation. An expired/revoked link, changed group membership or deleted source can make a shared folder disappear without a local sync fault.

Microsoft’s shortcut guidance distinguishes a shortcut from the shared source. Remove shortcut and Delete are not interchangeable. Do not delete/recreate the folder, move its contents or grant yourself wider rights to force it back. A copied file can also be an independent fork that no longer updates the original.

For older files tied to a departed or unlicensed user, ask the authorised administrator to check the actual account, retention, archive and recovery state promptly. Current unlicensed-OneDrive rules depend on account/licensing/billing/retention status and have changed. Do not assume every account remains available indefinitely or every file is deleted after one fixed number of days.

Agree where the work belongs before creating another folder or sync connection. Individual work OneDrive and team-owned SharePoint libraries serve different ownership needs. Use the organisation’s established site/library when appropriate, with clear owners and a plan for staff changes, rather than keep the only shared business records under an arbitrary person’s account.

For an approved new library, the site owner can follow Microsoft’s library guidance. Agree purpose, membership, sensible folders/metadata and how people will find records. Check actual versioning settings and any required retention with the responsible owner; these are not automatic proof of backup or regulatory compliance.

On an authorised supported device, use the approved OneDrive client and correct work account. For shared-library access, choose the organisation’s supported shortcut/sync method and scope only needed content. Do not build competing duplicate connections, sync confidential libraries onto a public computer or remove management to obtain a local copy.

Confirm authority, destination, available capacity and the source copy that will be retained. For a small authorised upload, use the actual destination library’s supported Upload control or approved sync workflow. Start with harmless representative files, check for overwrite/conflict prompts and record what arrived.

SharePoint move/copy guidance explains that copying and moving do not preserve everything identically; for example, Copy to does not carry all historical versions. Check the actual method’s treatment of history, metadata, permissions, links and specialist content such as notebooks or live application data before a larger transfer.

Open representative destination content, confirm intended access and check error/exception reports. A matching item count or completed upload is useful evidence, not proof every file, version or link is complete. Larger or cross-organisation migrations need their own supported plan, ownership and recovery checks. Do not delete the source, empty bins or overwrite current work to make counts match.

Have the owner inspect the exact file/folder/library and its existing access, including site/group membership and sharing links. Confirm who needs view, edit or another supported role. Microsoft’s SharePoint sharing guidance explains that editing a folder can include changing, moving and deleting its accessible content.

For a justified new share, follow policy and select the actual intended recipients and least access needed. A Specific people link limits that link’s intended recipients, but it does not remove access people already have through another permission. Review the real audience, organisation/guest identity and whether the destination permits external sharing. Cancel harmless practice before sending real invitations.

Do not select Anyone/public access, turn off policy or email private attachments as a shortcut around Access denied. If collaboration changes are not appearing, confirm both people are editing the same original rather than separate downloaded copies, and inspect saving/sync status. Preserve competing edits before the owner resolves a conflict; do not replace one person’s work merely to remove a warning.

Open the relevant OneDrive status and read the actual item/error. Confirm the correct work account, supported client, connection, pause/sign-in state, available local/cloud capacity and whether the source opens online. OneDrive icons distinguish online-only placeholders, downloaded availability, shared items and faults; a visible name does not always mean the file can open offline.

Use the appropriate current sync guidance for the actual client and message. Read current file/path/type/library limits rather than rename whole collections or switch to an Insider build. A blocked type or policy restriction needs owner review, not a false extension or protection bypass.

Preserve local-only edits and cloud versions before any assessed reset/relink. Do not clear caches, delete sync folders, relocate live Outlook data, recreate profiles or move whole libraries in/out as a routine first step. If the intended original, authority or replacement behaviour is uncertain, stop and use the responsible IT/site owner with the exact error.

Use the responsible file/site/IT owner for missing shared sources, former-staff access, uncertain recovery, repeated sync faults or a bulk migration. Privately provide the intended account/organisation, owner/site/library, file name, last access time and relevant error. Do not send the whole confidential folder, sharing tokens, credentials or payment details to explain one missing item.

Our Microsoft 365 support can discuss the symptom and a scoped assessment. Agree authority, preservation, destination/access and verification before work. Source-owner or administrator permissions may be necessary; no support visit can guarantee every deleted, archived or unretained file can be recovered.

If an ordinary deletion is established, use the lost-file recovery guide for appropriate retained copies and preservation. If data is corrupt, use the corrupted-file guide. Reconnecting sync is not a substitute for an actual recovery or incident plan.