Fix Broken Links in Office 365 Documents After Migration
Microsoft 365 (formerly Office 365) stores documents across SharePoint Online, Teams and OneDrive for Business — all backed by SharePoint. Any migration into or within Microsoft 365 changes file paths and URLs, breaking the embedded links in every affected Office document. This guide covers how ReplaceMagic repairs them across all Microsoft 365 applications.
All Microsoft 365 apps covered: SharePoint Online, Teams, OneDrive for Business — all use SharePoint as their document storage backend
All Office formats: Word, Excel, PowerPoint, Visio, Project, OneNote, PDF and text files — every link type in every format
Bulk repair: ReplaceMagic processes thousands of documents in parallel without opening any file, preserving SharePoint metadata
What Happens to Document Links During Microsoft 365 Migration
Office documents store links to other files as the exact path or URL where the linked file lived when the link was created. During any Microsoft 365 migration, these stored paths change — making every embedded reference invalid.
File Server to Microsoft 365
UNC paths (\\FileServer\Dept\File.xlsx) become SharePoint Online URLs (https://company.sharepoint.com/sites/Dept/File.xlsx). Every embedded link referencing the old UNC path breaks simultaneously at cutover.
SharePoint On-Premises to Microsoft 365
Internal URLs (http://intranet/sites/Finance/...) become cloud URLs (https://company.sharepoint.com/sites/Finance/...). Absolute links and some relative links break depending on how site paths changed.
Microsoft 365 Tenant-to-Tenant
Both the base URL and SharePoint’s internal item IDs change. Absolute links, relative links and ID-based links all break. ID-based links require conversion to absolute URL format (based on user provided search/replace combinations) to survive the tenant boundary — ReplaceMagic handles all three types. See the tenant-to-tenant guide.
Office 365 Applications and Affected Link Types
- Word: hyperlinks, OLE objects, field codes, header/footer paths, VBA
- Excel: hyperlinks, external link sources, OLE, Power Queries, Pivots, connections
- PowerPoint: hyperlinks, OLE objects, embedded file references, action links
- Visio: hyperlinks, OLE objects, shape data links
- Project: hyperlinks, resource links, OLE objects
- OneNote: page links, embedded file references [BETA]
- PDF: hyperlinks, launch action links
- Text/CSV/HTML: any embedded URL or path string
How ReplaceMagic Works With Microsoft 365
Native SharePoint Online Integration
ReplaceMagic connects directly to SharePoint Online via the Microsoft API — no drive mapping or WebDAV required. This means it can scan and repair documents stored in:
- SharePoint Online document libraries
- Microsoft Teams channel document libraries (SharePoint backend)
- OneDrive for Business (SharePoint backend)
- SharePoint Canvas and Wiki pages (ASPX content)
Authentication for Microsoft 365
ReplaceMagic supports all Microsoft 365 authentication methods:
- Standard credentials: Microsoft 365 email and password
- Multi-Factor Authentication: use an application password from your account security settings
- App-Only Authentication: certificate-based, for automated or service account scenarios
See the authentication guide for setup instructions.
Handling Microsoft 365 Throttling
SharePoint Online rate-limits API calls (HTTP 429 throttling). ReplaceMagic manages this automatically:
- Start with 3–5 parallel processing threads for Microsoft 365 targets
- Enable “Decrease workload during SharePoint Throttling” in Configuration for automatic rate management
- Run during off-peak hours (nights and weekends) for best throughput on large libraries
See the throttling guide.
Metadata Preservation in Microsoft 365
ReplaceMagic can preserve the original last-modified date and modified-by author after making changes to documents in SharePoint Online. This requires Site Administrator rights on the target SharePoint site. Without Site Admin, changes are saved normally but the modified timestamp updates to the current time.
Scale: Processing Enterprise Microsoft 365 Estates
- Multi-threaded: documents processed in parallel across CPU cores — no documents opened
- Recommended batch size: up to 250,000 documents per run
- Volume licensing available: run multiple licensed copies on separate machines simultaneously to reduce migration window time
- Database export: results exportable to SQLite, MySQL or SQL Server for very large result sets
Ready to fix your Microsoft 365 migration links? Download the free trial and test against your own documents before buying.
