Efficiently managing content across Microsoft 365 often requires updating outdated text, branding, or terms across multiple SharePoint document libraries simultaneously. While Microsoft 365 does not offer a native “find and replace” button that spans multiple libraries, you can automate this task efficiently using PowerShell and the PnP PowerShell module.
This guide provides a step-by-step walkthrough to safely batch replace text across your document libraries. Prerequisites Before You Begin
To run the automation script successfully, you need to prepare your environment with the following components:
Administrator Permissions: You must have SharePoint Online Administrator or Site Collection Administrator access.
PnP PowerShell Module: This open-source library streamlines SharePoint management. Install it by running Install-Module PnP.PowerShell -Scope CurrentUser in your PowerShell console.
Local Word Application: The script utilizes the local Word Object Model to open, edit, and save documents. Step 1: Define Your Target Libraries and Search Terms
Before running the full script, map out your variables. Create a list of the specific SharePoint Document Library names you want to target, the exact text string you need to remove, and the new text string replacing it. Step 2: PowerShell Script for Batch Replacement
Open your PowerShell ISE or VS Code editor and customize the script below. This script connects to your SharePoint site, loops through the specified libraries, downloads the Word documents (.docx), applies the text replacement locally via Microsoft Word, and uploads the updated versions back to SharePoint. powershell
# — Configuration Variables — \(SiteURL = "https://sharepoint.com" \)TargetLibraries = @(“Documents”, “MarketingMaterial”, “Policies”) \(FindText = "Old Company Name" \)ReplaceText = “New Company Name” \(TempFolder = "C:\TempSharePointDocs\" # Create local temp folder if it doesn't exist if (-not (Test-Path \)TempFolder)) { New-Item -ItemType Directory -Path \(TempFolder | Out-Null } # --- Connect to SharePoint Online --- Connect-PnPOnline -Url \)SiteURL -Interactive # Initialize Word Object Model hidden in the background \(WordApp = New-Object -ComObject Word.Application \)WordApp.Visible = \(false \)WordApp.DisplayAlerts = “wdAlertsNone” foreach (\(LibraryName in \)TargetLibraries) { Write-Host “Processing Library: \(LibraryName" -ForegroundColor Cyan # Retrieve all Word documents from the library \)Files = Get-PnPListItem -List \(LibraryName -Fields "FileRef", "File_x0020_Type" | Where-Object { \)_[“File_x0020_Type”] -eq “docx” } foreach (\(File in \)Files) { \(FileRef = \)File[“FileRef”] \(FileName = Split-Path \)FileRef -Leaf \(LocalPath = Join-Path \)TempFolder \(FileName Write-Host "Downloading: \)FileName” -ForegroundColor Yellow Get-PnPFile -Url \(FileRef -Path \)TempFolder -AsFile -Force # Open the document locally in Word \(Doc = \)WordApp.Documents.Open(\(LocalPath) \)FindObject = \(WordApp.Selection.Find # Configure Find and Replace parameters \)FindObject.Text = \(FindText \)FindObject.Replacement.Text = \(ReplaceText \)FindObject.Forward = \(true \)FindObject.Wrap = 1 # wdFindContinue # Execute Replace All (Args: FindText, MatchCase, MatchWholeWord, MatchWildcards, MatchSoundsLike, MatchAllWordForms, Forward, Wrap, Format, ReplaceWith, Replace) \(FindObject.Execute(\)FindText, \(false, \)false, \(false, \)false, \(false, \)true, 1, \(false, \)ReplaceText, 2) | Out-Null # Save and close the document \(Doc.Save() \)Doc.Close() # Upload the updated file back to SharePoint Write-Host “Uploading updated file: \(FileName" -ForegroundColor Green Add-PnPFile -Path \)LocalPath -Folder \(LibraryName -Values @{"Title" = \)File[“Title”]} -Force | Out-Null # Clean up local file Remove-Item \(LocalPath -Force } } # --- Cleanup --- \)WordApp.Quit() # Release COM objects from system memory [System.Runtime.InteropServices.Marshal]::ReleaseComObject(\(WordApp) | Out-Null Remove-Item \)TempFolder -Recurse -Force Disconnect-PnPOnline Write-Host “Batch text replacement complete across all libraries!” -ForegroundColor Green Use code with caution. Step 3: Mitigation and Risk Management
Automated batch updates carry risks if executed blindly. Implement these safety measures before running the script on production data:
Test on a Mock Library: Always create a test library containing 2–3 sample documents first. Run the script against this test set to ensure formatting, spacing, and hyperlinks remain intact.
Account for Version Control: If your document libraries have versioning turned on, this script will create a new minor or major version for every single file. Ensure your storage capacity can handle the extra version history.
Manage Checked-Out Files: Files checked out by users will cause the script to skip or error out. Coordinate with your team to ensure all documents are checked in prior to execution. Alternative Third-Party Tools
If you prefer a visual user interface over command-line scripts, several enterprise third-party tools specialize in bulk metadata and content operations for SharePoint. Platforms like ShareGate, SysKit, or specialized Microsoft 365 find-and-replace add-ins allow administrators to execute these changes globally via a dashboard without writing code.
To help me tailor this script or find alternative solutions, let me know:
Leave a Reply