OneDrive Admin Checklist: shared library sync stays pending for managed Windows PCs

When you deploy OneDrive to managed Windows PCs in your organization, users often report that a shared library shows a status of Pending and never synchronizes files. This symptom occurs because the OneDrive sync engine cannot resolve the SharePoint site URL or lacks the required permissions, group policy settings, or network access. This article explains the five most common root causes and provides a step-by-step checklist that IT administrators can use to resolve the pending state on shared libraries.

Why a Shared Library Shows Pending Instead of Syncing

OneDrive for Business uses the same sync engine as the consumer version, but it authenticates against Microsoft Entra ID formerly Azure AD and communicates with SharePoint Online. When a user clicks Sync on a shared library document library, the sync engine sends a request to SharePoint Online, downloads the file metadata, and begins file transfer. If any step in this chain breaks, the library stays in a Pending state.

The most common technical reason is that the sync engine cannot authenticate the user’s token for the specific SharePoint site. This happens when the user’s cached credentials are for a personal Microsoft account instead of a work or school account. Another frequent cause is a group policy that blocks syncing of libraries larger than a defined size. The sync engine checks the library size before it starts downloading, and if the size exceeds the policy limit, it marks the library as Pending indefinitely.

Network restrictions also play a role. If the Windows PC is behind a proxy that does not allow WebSocket connections or blocks the SharePoint Online endpoints, the sync engine cannot establish a persistent connection and falls back to a polling mode that often results in a pending status. Finally, the OneDrive sync app version matters. Older versions of the sync app do not support shared libraries that are part of a Microsoft 365 Group or a communication site.

Step-by-Step Admin Checklist to Resolve Pending Shared Library Sync

Use the following checklist in the order shown. After each step, ask the user to restart OneDrive or sign out and sign back in to trigger a new sync attempt.

1. Verify the user is signed in with the correct work or school account
   Open OneDrive settings by right-clicking the OneDrive cloud icon in the notification area and selecting Settings. Go to the Account tab. The account listed under You are signed in as must match the user’s Microsoft Entra ID UPN. If it shows a personal account like user@outlook.com, click Unlink this PC, then sign in again with the work account.
2. Check the tenant sync policy for domain restrictions
   Go to the Microsoft 365 admin center, then Settings > Org Settings > OneDrive. Under Sync, confirm that Allow syncing only for specific domains is either not enabled or includes the domain of the SharePoint site where the library resides. If the domain is blocked, the sync engine leaves the library pending.
3. Review group policies that control sync behavior
   On the managed Windows PC, open the Local Group Policy Editor or check the domain-based GPO. Navigate to Computer Configuration > Administrative Templates > OneDrive. Verify the policy Set the maximum size of a OneDrive that can download automatically. If this policy is enabled and the shared library exceeds the size limit in megabytes, the library will not sync. Either increase the limit to a value larger than the library or disable the policy.
4. Ensure the shared library URL is reachable from the client
   Open a web browser on the affected PC and navigate to the SharePoint site URL. If the site loads, confirm the user has at least Read permissions on the library. If the site does not load, check the network proxy configuration. Add the SharePoint Online and OneDrive endpoints to the proxy bypass list. Microsoft publishes the full endpoint list at docs.microsoft.com/microsoft-365/enterprise/urls-and-ip-address-ranges.
5. Update OneDrive to the latest production version
   On the managed PC, right-click the OneDrive cloud icon, select Settings, go to the About tab, and note the version number. Compare it with the latest version listed in the Microsoft 365 admin center under Health > Service health. If the version is older than the current production build, download and install the latest OneDrive sync app from the Microsoft 365 admin center or deploy it via Microsoft Intune.
6. Clear the OneDrive sync cache for the specific library
   Close OneDrive completely. Open File Explorer and navigate to %LocalAppData%\Microsoft\OneDrive\settings\Business1. Delete the folder that contains the SharePoint site ID for the affected library. Restart OneDrive. The sync engine will re-enumerate the library and should move it out of the pending state.
7. Reset OneDrive if all previous steps fail
   Press Windows key + R, type %localappdata%\Microsoft\OneDrive\onedrive.exe /reset, and press Enter. Wait 30 seconds. Open OneDrive again by searching for OneDrive in the Start menu. Sign in with the work account. This resets all sync relationships without deleting local files.

When the Shared Library Still Shows Pending After the Checklist

OneDrive Pending on a Shared Library That Uses Metadata or Content Types

Some shared libraries have custom metadata columns, content types, or information management policies that require the sync engine to download additional schema information. If the schema download fails, the library stays pending. To fix this, ask the site owner to simplify the library by removing unnecessary columns or content types. Alternatively, create a new library with default settings and test the sync again.

OneDrive Pending on a Library with File Names That Exceed the Path Length Limit

The Windows file system has a maximum path length of 260 characters. If any file or folder in the shared library has a full path longer than 260 characters, OneDrive cannot create the local file and marks the library as pending. Use the SharePoint Online Management Shell to run Get-PnPFolder and identify files with long paths. Ask users to rename or move those files to a shorter path.

OneDrive Pending on a Library That Is Part of a Microsoft 365 Group

Shared libraries that belong to a Microsoft 365 Group require the user to be a member of the group. If the user was added to the group after the library was synced, the sync engine might not recognize the membership. Ask the user to unfollow the library in OneDrive settings, then sync it again from the SharePoint site. The membership check will run again and resolve the pending state.

Sync Behavior Comparison: Shared Library vs Personal OneDrive

Item	Shared Library Sync	Personal OneDrive Sync
Authentication source	SharePoint Online site token	User’s Microsoft Entra ID token
Group policy size limit	Applies to library total size	Applies to user’s entire OneDrive
Network endpoint requirements	SharePoint Online URLs plus WebSocket	OneDrive consumer URLs plus WebSocket
Permission dependency	Site-level or library-level permissions	User’s own license and storage quota
Cache reset method	Delete site-specific folder in Business1	Reset OneDrive via command line

Use this table to decide which troubleshooting path to follow. If the user’s personal OneDrive syncs correctly but a shared library stays pending, the issue is almost always a permission or site-specific policy problem rather than a client configuration issue.

After completing the checklist, you can now resolve pending shared library sync on any managed Windows PC. Next, review the OneDrive sync reports in the Microsoft 365 admin center to identify other users with pending libraries. As an advanced tip, enable audit logging for SharePoint Online so you can see when a sync request fails and the exact HTTP error code returned to the client.