Others

How to Fix the CopilotSearchable Parameter Error in SharePoint PowerShell

Maira Mehtab Sep 22, 2026 869 views

Question details

Users experience an error when running the Add-SPOOrgAssetsLibrary cmdlet in SharePoint PowerShell, where the -CopilotSearchable parameter is rejected or not recognized.

Product: SharePoint Online Management Shell
Device & OS: not provided
Scenario: Adding a SharePoint organizational assets library with Copilot searchability enabled via PowerShell.
Observed behavior: The command fails because the CopilotSearchable parameter is rejected, often due to an outdated shell version installed on another account or incorrect boolean syntax.

Before you start

Ensure you have administrator privileges on your computer to uninstall software and install the latest SharePoint Online Management Shell system-wide.

Solution 1Recommended

Update SharePoint Online Management Shell and Correct Syntax

Uninstall any outdated versions of the Management Shell across all user accounts, install the latest version, and use the correct PowerShell boolean syntax.

The issue is typically caused by an older version of the SharePoint Online Management Shell installed under another account on the same computer, or by following inaccurate syntax in the official documentation.

Uninstall older shell versions

Open 'Apps & features' or 'Programs and Features' in Windows settings. Search for 'SharePoint Online Management Shell' and click 'Uninstall'. Ensure you check other user accounts on the computer and remove any older versions found there as well.

Install the latest version

Navigate to the official Microsoft Download Center, download the newest SharePoint Online Management Shell executable, and install it as an administrator.

Apply correct boolean syntax in PowerShell

Launch PowerShell as an administrator. When typing your Add-SPOOrgAssetsLibrary command, replace the plain text 'true' with the PowerShell boolean variable '$true'. Your parameter string should look exactly like: -CopilotSearchable $true

Documentation Error: Official Microsoft documentation may incorrectly list the parameter as '-CopilotSearchable true'. PowerShell requires the '$' prefix for true and false values to be recognized correctly.

Free Microsoft Office alternative

Looking for a Lightweight Office Suite Alternative?

While managing SharePoint and Copilot requires Microsoft's administrative tools, your daily document creation doesn't require an expensive suite. WPS Office is a lightweight, fully compatible, and free alternative for all your Word, Excel, and PowerPoint needs.

1. Download the installer: Visit the official WPS Office website and download the free installer package for your operating system.
2. Install the application: Run the downloaded executable file and follow the on-screen instructions to complete the installation.
3. Open your files: Launch WPS Office and instantly open any existing Microsoft Word, Excel, or PowerPoint files without formatting loss.

Fully compatible with Microsoft Office file formats (.docx, .xlsx, .pptx) used in SharePoint.Lightweight design that uses minimal system resources compared to heavier office suites.All-in-one suite combining Writer, Presentation, and Spreadsheets in a single tabbed window.Seamless migration from Microsoft Office with a familiar user interface.

microsoft office alternative - wps office

Frequently Asked Questions

Why does the Add-SPOOrgAssetsLibrary cmdlet say the CopilotSearchable parameter is not recognized?

This typically occurs if you are running an outdated version of the SharePoint Online Management Shell. The -CopilotSearchable parameter is relatively new and requires the latest module version to function.

How do I correctly format a boolean parameter in SharePoint PowerShell?

In PowerShell, true and false values must be preceded by a dollar sign. You must use $true or $false instead of just typing the words plainly.

Can having multiple Windows user accounts affect my PowerShell modules?

Yes, if the SharePoint Online Management Shell was installed previously under a different user profile on the same machine, your current PowerShell session might still be calling the older, incompatible version of the module.

Office Quick Solutions