What problem does it solve? SharePoint accepts file and folder names that OneDrive sync, File Explorer, and the Teams Files tab later refuse to handle, causing sync failures that surface one user at a time with no visibility into how widespread the problem is. ## Core Features & Use Cases - Rule-Based Detection: Flags illegal characters, leading/trailing spaces, trailing periods, Windows reserved names, URLs over 400 characters, deep nesting, long-term check-outs, and junk artifacts across Blocker, Risk, and Info severities. - Safe Rename Proposals: Generates a proposed safe name for every blocked item without ever modifying the library, since the audit is strictly read-only. - Self-Contained HTML Report: Produces a severity-ranked report with sync readiness score, rule frequency chart, path-length analysis, and a prioritized remediation list saved to a Sync Reports folder. - Use Case: When users report "why won't this library sync" after a migration, run the audit on the affected library to get a full inventory of the 36 blocked items, their proposed renames, and the folders causing the most failures. ## Quick Start Ask Copilot in SharePoint to run a sync health check on the document library that is failing to sync.
