Microsoft SharePoint Document Library Sync: What You Need to Know

SharePoint Document Library Sync uses OneDrive for Business as its engine to mirror a document library to your local machine — files show up in File Explorer or Finder like any other folder, staying two-way synced with the cloud, permissions and versioning intact.

In this post: How it works · Real limits worth knowing · Best practices · Syncing a library · Auto-syncing a library for everyone via Intune · When sync silently pauses itself · Admin monitoring · When would you actually use this? · Related reading

How it works

OneDrive constantly reconciles the local copy with the cloud version in both directions, so working offline (a field visit, a flight) doesn’t block you — changes sync silently once you’re back online. Microsoft’s sync documentation covers the full technical detail.

Real limits worth knowing

Sync failures usually trace back to one of a handful of hard limits, and knowing them upfront saves a support ticket later. The full file path (folder structure plus filename, after decoding) can’t exceed 400 characters — and on Windows specifically, the local OneDrive root folder path plus the relative file path together can’t exceed 520 characters, since the sync client also has to fit within Windows’ own path handling. Certain characters (" * : < > ? / \ |) will silently block a file or folder from syncing if they appear in the name. And while Microsoft’s long-standing guidance was to keep synced libraries under roughly 300,000 files for good performance, a rollout that started in April 2026 is raising that ceiling to as many as 1,000,000 items — worth checking whether it’s reached your tenant yet if a large library has been sitting right at the old limit.

Best practices

Don’t sync massive libraries wholesale. Break into subfolders/smaller libraries, or use filtered views, especially for large archives — syncing thousands of files kills local performance.
Enable Known Folder Move (KFM) — redirects Desktop/Documents/Pictures to OneDrive, giving continuity and an extra layer of backup.
Use Files On-Demand instead of full local copies — shows placeholders and downloads only what’s actually opened, so sync doesn’t quietly fill up someone’s disk.
Train users on the sync icon states — blue cloud (online-only), green check (synced), red cross (error) — and how to resolve conflicts. A short internal guide cuts helpdesk tickets meaningfully.
Monitor via the OneDrive admin center, and manage sync settings at scale with Group Policy or Intune rather than per-device.

Train users on what blue cloud, green check, and red cross actually mean — most sync-related helpdesk tickets are just someone not recognizing an error icon.

Syncing a library

Open the SharePoint Online document library.
Click Sync.
Allow the browser to open OneDrive if prompted.
It appears in File Explorer under your org’s name.

Encourage people to be selective about what they sync — pinning every library “just in case” is how local storage bloats.

Auto-syncing a library for everyone via Intune

The steps above are the manual, one-user-at-a-time path — fine for someone syncing a library themselves, but not for rolling the same library out to an entire team without asking each person to click Sync individually. Intune can push that automatically the next time OneDrive starts, no user action required:

In the target library, open the Sync menu and select Copy library ID — this gives a URL-encoded ID that needs decoding down to the plain ListID GUID Intune expects.
In the Intune admin center: Devices > Configuration > Create > New Policy, Platform Windows 10 and later, Profile type Settings catalog.
Search the settings picker for “Configure team site libraries to sync automatically” and add the library’s name and decoded ID.
Assign the policy to the relevant device/user group.

This is a “next sign-in” setting, not instant — expect up to about 8 hours after a targeted user’s next OneDrive sign-in before the library actually starts syncing on their machine. Worth pairing with the “don’t sync massive libraries wholesale” advice above — auto-provisioning a library nobody asked for, that also happens to be enormous, just moves the storage-bloat problem from a user decision to an admin one.

When sync silently pauses itself

Worth ruling out before treating a “why hasn’t this synced in hours” ticket as a real error: OneDrive pauses syncing automatically, by design, under two common conditions — the device is on a metered network (a connection Windows has flagged as data-capped, common on mobile hotspots and some home ISPs) or the device has entered Battery Saver mode. Neither shows an error state exactly — the sync icon just goes idle, and content genuinely stops moving in either direction until the condition clears or a user intervenes.

Both are per-device, user-facing toggles by default (Settings > Sync and backup in the OneDrive client), which means an affected user can turn them off individually — but that doesn’t scale past a handful of laptops. If a specific device fleet needs to keep syncing regardless of network type or power state (a field team on cellular hotspots, say), the equivalent controls are available as OneDrive sync policies deployed via Intune or Group Policy, the same delivery mechanism already covered above for auto-syncing a library — worth pairing both rollouts together rather than leaving metered-network and battery-saver behavior to each user’s own settings.

Admin monitoring

Check sync restrictions for a specific user:

Get-SPOSyncClientRestriction -Identity "user@domain.com"

Useful for confirming someone isn’t inadvertently syncing a restricted library. Pair with audit logs for anything needing more detailed tracking.

When would you actually use this?

Someone needs to work on SharePoint files with unreliable or no connectivity — sync means they keep working locally, not blocked until they’re back online.
Users keep asking why their sync icon shows an error and nobody can explain it — that’s a training gap, not a technical one, and the fix is a one-page internal guide.
You’re onboarding a device fleet and want consistent sync behavior across all of them — that’s Group Policy/Intune, not asking each user to configure it themselves.

SharePoint Sync Limitations: What You Need to Know — the limits worth knowing before rolling sync out the way this post describes.
Switching Between Classic and Modern Views in SharePoint — sync behavior can differ depending on which view mode a library is in.

That’s it for this one. Questions? Leave a comment and I’ll get back to you.