ReplaceMagic and SharePoint Online — Native Bulk Link Repair

SharePoint Online is Microsoft’s cloud-based document management and collaboration platform, part of Microsoft 365. Organizations worldwide use it to store Word, Excel, PowerPoint, Visio, and Project files in structured document libraries. When those organizations migrate from file servers, on-premises SharePoint farms, or another Microsoft 365 tenant, every hyperlink, OLE object reference, and embedded path that pointed to an old location becomes broken. ReplaceMagic was built specifically to solve this problem — at scale, without requiring you to open a single document manually.

Native Connection — No Drive Mapping Required

ReplaceMagic connects to SharePoint Online directly through the Microsoft SharePoint REST API and CSOM (Client-Side Object Model). This means you do not need to map SharePoint as a network drive or configure WebDAV. The native API connection is faster, more reliable, and gives ReplaceMagic access to SharePoint metadata that a mapped drive simply cannot expose. Once connected, ReplaceMagic can enumerate document libraries, download files for processing, apply replacements, and upload the corrected files — all without leaving the ReplaceMagic interface.

Authentication Methods Supported

ReplaceMagic supports multiple authentication methods for SharePoint Online to accommodate different tenant security configurations:

• SharePoint Online (username/password) — Standard Microsoft 365 credentials. Suitable for tenants where legacy authentication is still permitted.
• MFA with App Password — For accounts protected by multi-factor authentication. Generate an app password in your Microsoft 365 account security settings and use it in place of your regular password.
• App-Only Authentication — Register an Azure AD application, grant it the required SharePoint permissions, and use the client ID and client secret. This method is ideal for automated, unattended, or scheduled workflows where no interactive login is possible.

What ReplaceMagic Preserves on SharePoint Online

One of the most critical concerns during bulk document processing is metadata integrity. ReplaceMagic is designed to preserve the following SharePoint Online properties after modifying a file:

• Last-modified date and modified-by author
• Content approval status (Approved, Rejected, Pending)
• Version history — changes are checked in as a new version rather than overwriting the version chain
• Check-in and check-out state — documents that were checked out before processing are returned to the same state

Preserving the last-modified date and author requires Site Administrator rights on the target site collection. Contributor rights alone are not sufficient for this operation.

SharePoint Online Throttling (HTTP 429)

SharePoint Online enforces rate limits on API requests. When too many requests arrive in a short window, the service returns an HTTP 429 (Too Many Requests) or HTTP 503 response. ReplaceMagic handles throttling automatically: it detects the 429 response, reads the Retry-After header, pauses the affected thread for the specified duration, and then retries the request. No manual intervention is required.

To minimize throttling pressure, the recommended parallel processing setting for SharePoint Online is 3 to 5 threads. Higher parallelism will trigger throttling more frequently and can actually reduce overall throughput. You can adjust the thread count in the ReplaceMagic Processing settings panel.

Supported Library and Page Types

Via its native integration, ReplaceMagic can process the following content types on SharePoint Online:

• Standard document libraries (Word, Excel, PowerPoint, Visio, PDF, and other file types)
• Wiki pages (Enterprise Wiki content stored as ASPX)
• Canvas pages (Modern SharePoint pages)

Special Character Limitation

Files whose names contain any of the following characters cannot have their shared link tokens or organizational link information retrieved by the SharePoint API: ~ # % & * { } \ : <> ? / + | ". These files are still downloaded, processed for broken links, and re-uploaded — but any shared-link-style URLs pointing to them cannot be repaired through the token mechanism.

Typical Migration Scenarios

• File server → SharePoint Online: UNC paths (\\Server\Share\File.xlsx) become HTTPS document library URLs.
• SharePoint On-Premises → SharePoint Online: Intranet URLs (http://intranet/sites/...) change to cloud URLs (https://company.sharepoint.com/sites/...).
• Tenant-to-tenant migration: Both the base URL and internal SharePoint item IDs change; ID-based links require conversion to absolute URL format.

Step-by-Step Processing Overview

Using ReplaceMagic with SharePoint Online follows a straightforward workflow: select SharePoint Online as the target → authenticate using your preferred method → select the site and document library → run a scan to identify all links → configure find-and-replace rules → preview changes in the results grid → execute replacements. The entire process is logged and reversible via SharePoint’s built-in version history.