OneDrive for Business file server migration breaks recent links for remote users: Fix Guide
🔍 WiseChecker

OneDrive for Business file server migration breaks recent links for remote users: Fix Guide

After migrating shared files from an on-premises file server to OneDrive for Business, remote users often find that their existing shortcuts, recent document links in Office apps, and bookmarked URLs stop working. This happens because the original file paths change from UNC paths like \\server\share\file.docx to OneDrive web URLs or sync paths. The problem affects users who rely on the Recent Files list in Word, Excel, and PowerPoint, as well as pinned links in Microsoft Teams and Outlook. This guide explains why these links break and provides step-by-step methods to restore access without re-sharing every file manually.

Key Takeaways: Restoring Broken Recent Links After File Server Migration

  • Office Recent Files list (File > Open > Recent): Stores the original UNC path; clearing the Office cache forces a refresh to the new OneDrive location.
  • OneDrive sync app > Settings > Account > Unlink this PC: Resets the sync relationship and allows re-syncing the migrated folder with the correct local path.
  • Microsoft 365 admin center > SharePoint > Active sites > Migration site: Allows bulk URL replacement using the SharePoint Migration Tool (SPMT) or PowerShell to update all file references.

ADVERTISEMENT

Why File Server Migration Breaks Recent Links

When you move files from a Windows file server to OneDrive for Business, the underlying storage location changes from a network share to a cloud-based library in SharePoint or OneDrive. Office applications store the last-used file path in the Recent Files registry and in the Office Document Cache. These paths are absolute — for example, \\fileserver\shared\project\budget.xlsx. After migration, the file exists at a OneDrive URL like https://contoso-my.sharepoint.com/personal/user/Documents/project/budget.xlsx or a local sync path like C:\Users\User\OneDrive - Contoso\project\budget.xlsx. The old UNC path no longer resolves, so Office displays a broken link or a generic error message.

Remote users are affected more severely because they never had direct LAN access to the file server. They accessed files through VPN or Remote Desktop, and the migration changes the access method entirely. Even if the files are re-synced locally via OneDrive, the Office Recent list still references the old path. The migration process itself does not update these cached references, so manual intervention is required.

The Role of Office Document Cache

Office maintains a local cache of recently opened files in the %LOCALAPPDATA%\Microsoft\Office\ folder. This cache includes the full path, file name, and a thumbnail preview. When the path changes, Office cannot locate the file and removes it from the list or shows a broken icon. Clearing this cache forces Office to rebuild the list from the new location the next time the user opens the file.

Impact on Microsoft Teams and Outlook Links

Links shared in Teams chats, channels, or Outlook emails that point to the old file server path also break. These links use UNC or HTTP paths that no longer exist. Users see a 404 error or a “File not found” message. The OneDrive sync app does not automatically redirect these links.

Steps to Fix Broken Recent Links for Remote Users

Use the following methods in order. Start with the quickest fix that requires no admin privileges.

  1. Clear the Office Document Cache on Each User’s Machine
    Close all Office applications. Open any Office app like Word. Go to File > Options > Save. Scroll to the Cache Settings section. Click Delete cached files. Restart the Office app. The Recent list will now show only files that the user opens manually from the new OneDrive location.
  2. Unlink and Re-link OneDrive Sync
    Right-click the OneDrive cloud icon in the system tray. Select Settings > Account. Click Unlink this PC. Confirm the action. After unlinking, sign in again with the same work account. Choose the folders that contain the migrated files. This forces OneDrive to rebuild the local sync path and update file metadata in Office.
  3. Reopen Files from the New OneDrive Location
    Open File Explorer and navigate to the OneDrive folder. Locate each file that appears broken in the Recent list. Double-click to open it in the corresponding Office app. This action adds the new path to the Recent list. Repeat for all critical files. The old broken entries will eventually be replaced as the cache refreshes.
  4. Use the SharePoint Migration Tool to Update Links (Admin Required)
    If you migrated files using the SharePoint Migration Tool, you can run a post-migration scan to update internal file references. In the SPMT dashboard, select the migration job. Click Review and update file references. The tool scans for old UNC paths in Office files and replaces them with the new OneDrive URLs. This works for files that contain hyperlinks or embedded references.
  5. Update Shared Links in Microsoft Teams and Outlook
    For links shared in Teams channels, navigate to the channel and edit the message. Replace the old UNC path with the new OneDrive share link. To get the new link, go to the file in OneDrive or SharePoint, click the three dots, and select Share > Copy link. For Outlook emails, ask users to forward a corrected link or resend the file as an attachment.

ADVERTISEMENT

If Recent Links Still Do Not Work After the Main Fix

Some issues persist even after clearing the cache and relinking OneDrive. The following sections address the most common remaining problems.

Office Recent List Shows a Red X on the File Icon

A red X indicates that the file path is invalid but Office has not removed the entry. Open the file from the new location manually. If the red X remains, delete the file from the Recent list by right-clicking the entry and selecting Remove from list. Then reopen the file from OneDrive to add a fresh entry.

OneDrive Sync Shows a Gray Cloud Icon Instead of a Green Check

A gray cloud means the file is online-only and not synced locally. Remote users on slow connections may see this often. Right-click the file in File Explorer and select Always keep on this device. This downloads the file locally and updates the Office Recent list path to the local sync folder.

Users Report “File Not Found” When Clicking Links in Teams

The link still points to the old file server. Edit the message in Teams as described in step 5. If the link was sent in a chat that cannot be edited, ask the sender to resend the correct link. As a long-term fix, configure your migration to use a URL redirect rule in your firewall or DNS, but this is rarely practical for UNC paths.

Item UNC Path (Before Migration) OneDrive URL (After Migration)
File location example \\fileserver\shared\project\budget.xlsx https://contoso-my.sharepoint.com/personal/user/Documents/project/budget.xlsx
Access method LAN, VPN, or Remote Desktop OneDrive sync app or web browser
Office Recent list entry Stored as UNC path Stored as local sync path or web URL
Link sharing in Teams UNC or mapped drive letter SharePoint share link
Fix required None Clear cache, relink sync, or update links

After completing the steps above, remote users can access migrated files through OneDrive without broken links. Test the Recent Files list in Word, Excel, and PowerPoint by opening a file from the new location and verifying it appears correctly. For ongoing migrations, use the SharePoint Migration Tool’s link update feature to automate the process. As an advanced tip, run the PowerShell cmdlet Set-SPOMigrationPackage with the -UpdateLinks parameter to bulk-replace UNC paths in migrated files before users access them.

ADVERTISEMENT