The OneDrive and SharePoint Sync Health dashboard in the Microsoft 365 Apps admin center provides visibility into sync client states, sync errors, and update compliance across an organization. When devices report sync health errors or fail to appear entirely, the dashboard is signaling that endpoint telemetry is missing, local sync engines are encountering policy blocks, or client-side sync loops are exhausting error thresholds.
Fast Fix
If devices are missing from the dashboard, ensure the registry value
SyncAdminReportsis set to1underHKLM\SOFTWARE\Policies\Microsoft\OneDrivevia Intune or Group Policy. If devices show active error badges, inspect the Sync errors tab in the admin center to identify whether failures stem from path limits, credential drops, or Known Folder Move (KFM) conflicts.
Diagnostic Snapshot
| Dashboard Indicator | Likely Cause | Primary Remediation Layer |
|---|---|---|
| “No data available” / Blank Dashboard | Telemetry key not enabled on endpoints; tenant licensing missing. | Intune / Group Policy (SyncAdminReports) |
| High Volume of “Path Too Long” Errors | Deep subfolder structures exceeding Win32 path thresholds. | SharePoint structure reorganization |
| “Sync Paused” / “Account Blocked” | Endpoint token revocation or tenant quota exhaustion. | Entra ID / SharePoint storage limits |
| KFM Opt-In Failures | Folder redirection conflicts or unmapped user shell folders. | Windows Registry / Intune KFM Profile |
Understanding the Sync Health Reporting Pipeline
The Sync Health dashboard does not communicate directly with SharePoint Online document libraries in real time. Instead, it relies on a client-side telemetry service embedded within the modern OneDrive sync client (onedrive.exe).
[Local OneDrive Sync Client]
│
▼ (Telemetry via 'SyncAdminReports' flag)
[Microsoft 365 Apps Admin Center]
│
▼ (Aggregation delay: 24 to 72 hours)
[SharePoint / OneDrive Sync Health Dashboard]
This reporting pipeline breaks down under three specific conditions:
- Disabled Endpoint Telemetry: By default, endpoints do not upload diagnostic telemetry to the administrative dashboard until the administrative policy key is explicitly written to the local machine.
- Telemetry Ingestion Lag: Diagnostic snapshots are aggregated asynchronously. New configurations can take between 24 and 72 hours to reflect accurately in the admin console.
- Endpoint Network Isolation: If endpoints cannot establish outbound connections to Microsoft diagnostic endpoints (
.manage.microsoft.comand related sync endpoints), health packets drop silently before reaching the reporting engine.
If individual endpoints show local sync halts that match reported dashboard issues, reference How to Reset the OneDrive Sync Client (The Complete Command List) to restore client baselines during testing.
Progressive Administrative Action Steps
1. Verify and Deploy the Administrative Telemetry Policy
Before troubleshooting specific errors displayed on the dashboard, confirm that endpoints are configured to send sync diagnostic reports.
Via Microsoft Intune:
- Sign in to the Microsoft Intune admin center.
- Navigate to Devices > Configuration > Create.
- Select Windows 10 and later > Settings catalog.
- Search for OneDrive, then select the category OneDrive.
- Enable Enable sync admin reports and toggle the setting to Enabled.
- Assign the profile to the target device group.
Via Registry (for Hybrid or Domain-Joined Devices):
If managing devices via Active Directory Group Policy or local scripts, confirm the following DWORD key exists on target endpoints:
Key: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\OneDrive
ValueName: SyncAdminReports
ValueType: DWORD
ValueData: 1
Note: Devices must be running OneDrive Sync client version 22.116 or higher to support sync health reporting.
2. Triage High-Frequency Errors in the Dashboard
Once telemetry arrives, navigate to the Microsoft 365 Apps admin center > Health > OneDrive sync. Select the Sync errors tab to filter issues by volume.
- “File path exceeds maximum length”: Users are nesting SharePoint shortcuts inside deep local folder structures. Win32 legacy limitations cause the sync engine to pause updates on affected paths.
- Resolution: Instruct users to shorten directory names or reduce nesting. Refer to How to Fix “File Path Too Long” in deep SharePoint Silos.
- “File name contains invalid characters”: Endpoints report synchronization halts due to forbidden symbols like colons, quotes, or trailing periods.
- Resolution: Audit files matching character rejection patterns using Resolving SharePoint “Invalid File Name” Character Errors (2025).
- “Known Folder Move (KFM) cannot be enabled”: Occurs when legacy Group Policies (such as Windows Folder Redirection to local file servers) conflict with OneDrive cloud redirection of Desktop, Documents, or Pictures.
3. Remediate Client-Side Credential Drops
If the dashboard reports widespread “User intervention required” or “Sign-in required” errors, local authentication tokens have dropped without alerting the user.
- In the dashboard, inspect the Device status list and note whether the errors are concentrated in a specific department or subnet.
- If concentrated, check whether an Entra Conditional Access policy or token lifetime policy was recently modified.
- Ensure affected workstations have access to Microsoft identity endpoints without SSL inspection or proxy interception.
If users show active token authentication loops on their devices, guide them through How to Clear Office Credential Cache on Windows 11 (The Modern Way).
4. Resolve Tenant and Library-Level Blocks
When a SharePoint library is marked with an error state across dozens of unique endpoints in the Sync Health dashboard, the root issue is rarely the sync client.
- Mandatory Columns: If a site owner made a custom metadata column mandatory without specifying a default value, client sync engines will flag sync health errors across every user syncing that library. For step-by-step metadata remediation, see How to Fix “Required Properties” preventing Office Auto-Save.
- Checkout Settings: Libraries configured to require checkout cannot synchronize downstream changes from multiple users, generating persistent client sync warnings. Check How to Fix SharePoint “Checkout Required” Sync Blockers.
Hidden Problem: Classic Sync Colliding with Shortcuts
If the dashboard displays intermittent sync halts on devices running clean builds, review whether users are executing both classic SharePoint Sync and modern OneDrive Shortcuts on the same libraries.
This behavior causes local database collisions that report as general engine errors in the Sync Health console. See Troubleshooting SharePoint “Sync” vs “Add Shortcut to OneDrive” to identify and resolve this mismatch at the tenant level.