Review file-sync errors and stale reporting Get the source data and prepare the review Documentation-checked proposed route; source collection and human approval required WHAT WAS CHECKED Official documentation checked; all routes are proposed and have not been run in a product account. No client data, account access, installs or account writes used. Native column names are distinguished from editorial kit contracts. Missing source evidence blocks completeness claims. BEFORE YOU START - An already-enabled OneDrive sync health dashboard in Microsoft 365 Apps admin center; suitable existing reader role, such as Global Reader. - Existing eligible reporting devices, supported sync app and an IT-approved expected-device roster, freshness policy and cutoff. This recipe does not enable telemetry or change device settings. - Firm-approved Excel; optional Copilot entitlement and tenant approval for the exact minimized data. Native Excel analysis can be done manually if Copilot is absent. - Keep raw exports and identifying source pointers in a separate restricted location. The AI workbook contains only approved alias-based tables and visible policy/scope text, never raw client records on another tab. DATA ACQUISITION LIMITS - The official guide documents Devices/Issues views, not a CSV Download control; this route manually captures displayed fields. - Status reporting is delayed (typically about 36 hours, or about 1 hour after startup). Records expire after 30 days; signed-out or ineligible/insufficiently-on devices may be absent. Absence is not proof of healthy sync. DECLARED INPUT CONTRACT expected-devices.csv: device_id, account_alias, eligibility_status, expected_reporting, owner_alias sync-health.csv: device_id, error_code, last_sync_utc, last_report_utc, app_version, source_row scope.txt STEP 1: Read the actual sync-health observations Tool: Microsoft 365 Apps admin center Open: Health > OneDrive Sync > Devices; Issues for error detail Access needed: See prerequisites; actual subscription, tenant configuration and permissions are untested. Use the existing dashboard, select the intended view/filter and record capture time. On Devices read Device name, User, Errors, App version, Last synced timestamp (UTC) and Last status reported timestamp (UTC). Select a user or issue for the actual error detail. Manually capture only the authorized device scope; no native CSV export is claimed. Expected output: Observed device rows and error detail with screenshot/row references and scope. Use it next: Match observations to the IT roster using verified device identity, not just a possibly reused display name. Check: If dashboard setup/access is absent, stop this acquisition step. Do not generate a tenant key or change reporting policy. Documentation limit: Official sources support named product features. Workflow-specific prompts, alias fields, mappings and reviewer rules are editorial adaptations, not native export promises. Source documentation: https://learn.microsoft.com/en-us/sharepoint/sync-health?tabs=windows STEP 2: Map the observed records to the starter input Tool: Excel and authorized staff Open: Separate analysis workbook > Home > Format as Table Access needed: See prerequisites; actual subscription, tenant configuration and permissions are untested. Create expected-devices.csv from the actual IT asset roster: device_id,account_alias,eligibility_status,expected_reporting,owner_alias. Create sync-health.csv from observations: device_id,error_code,last_sync_utc,last_report_utc,app_version,source_row. If the screen shows a message but no code, retain the literal message in a restricted/safe note and mark error_code unknown. Do not invent stable IDs from device names; use an IT-verified crosswalk. Put scope.txt, approved freshness threshold and known dashboard lag in Scope. Create named tables for ExpectedDevices and SyncHealth. Put the policy and review scope in visible worksheets or paste them into the next prompt. Expected output: ExpectedDevices and SyncHealth tables; no unobserved device is silently excluded. Use it next: Check the mapping against each original source before using AI. Check: Aliases and missing policy fields are staff-created; do not relabel a native export as the kit schema. Unknown stays blank/unknown, not false or zero. Documentation limit: Official sources support named product features. Workflow-specific prompts, alias fields, mappings and reviewer rules are editorial adaptations, not native export promises. Source documentation: https://support.microsoft.com/en-us/excel/tutorial-import-data-into-excel-and-create-a-data-model STEP 3: Review the bounded evidence with Copilot Tool: Excel Copilot, optional Open: Approved analysis workbook > Copilot icon at lower right > Chat only Access needed: See prerequisites; actual subscription, tenant configuration and permissions are untested. Use Chat only and submit the prompt. Without Copilot: join the verified device IDs and compare dates/statuses using the approved lag/freshness rules. PASTE THIS PROMPT Compare ExpectedDevices and SyncHealth using verified device_id and Scope. Report observed errors, stale reports under the approved threshold, last-sync observations, expected-but-missing devices, ineligible devices and ambiguous identity matches separately. Cite source rows and UTC timestamps. Account for the supplied reporting lag; do not declare a missing or green device healthy, infer backup coverage, or recommend disabling controls. No settings changes or user messages. Expected output: IT investigation queue with coverage and freshness limits. Use it next: Copy the draft exception list to the reviewer; retain row references. Check: Check every flagged row and the scope. A fluent answer is not evidence of completeness; no automatic workbook or source-system edits. Documentation limit: Official sources support named product features. Workflow-specific prompts, alias fields, mappings and reviewer rules are editorial adaptations, not native export promises. Source documentation: https://support.microsoft.com/en-us/excel/copilot/get-started-with-copilot-in-excel https://support.microsoft.com/en-us/excel/copilot/frequently-asked-questions-about-copilot-in-excel STEP 4: Approve the review result Tool: Responsible staff reviewer Open: Reviewed local worksheet Access needed: See prerequisites; actual subscription, tenant configuration and permissions are untested. IT checks missing/ambiguous devices and actual client state, then chooses remediation through its normal approved process. Expected output: Reviewed sync investigation list. Use it next: Any external message, source change, payment or deletion requires its own authorized process. Check: This is a sync telemetry review, not proof that all files are backed up or recoverable. Documentation limit: Editorial human-review gate; linked Excel documentation supports the worksheet used, not legal or accounting conclusions. Source documentation: https://support.microsoft.com/en-us/excel/tutorial-import-data-into-excel-and-create-a-data-model ACCOUNT AND SOURCE CHECKS STILL NEEDED - Actual account access, plan and source-data completeness have not been tested. USING THE FILES IN THIS KIT Use the exact files or source text named in the steps above. Native exports keep their own headers. The kit tables are editorial review worksheets; they are not a claim that a product exports those fields. Some routes use reviewed text directly or require additional original files. Never rename an unreviewed raw export to make it appear mapped. Keep expected-result files separate from inputs. The source account, actual data, prompts and end-to-end workflow were not tested. Any final communication, filing, permission change, payment or publication needs its own authorized human action. This guide performs none.