Enabling Copilot in SharePoint requires an admin to turn it on tenant-wide or per-site using PowerShell, after which users can chat with document libraries, draft pages, and build site-specific AI agents directly inside SharePoint. In our SharePoint and Microsoft 365 consulting work at Code Creators, the technical setup itself is usually the easy part, most of the delay we see in client rollouts comes from cleaning up permissions before flipping the switch, not from the configuration itself.
This guide covers exactly how to enable and use Copilot in SharePoint, plus the custom agent options and rollout practices we recommend to clients.
Admin Setup: How to Enable Copilot in SharePoint Online
Administrators need to lay the technical foundation before users can interact with AI on their sites. The deployment doesn’t require complex local installations, but it does require precise tenant-level configuration.
Setup at a glance:
| Steps | Action | Command / Detail |
| 1 | Confirm prerequisites | M365 E3/E5/Business Standard/Business Premium, Copilot licenses assigned, modern SharePoint Online, SPO Management Shell 16.0.26615.12013+ |
| 2 | Update your PowerShell module | Update-Module -Name Microsoft.Online.SharePoint.PowerShell |
| 3 | Connect to the admin center | Connect-SPOService –Url https://yourtenant-admin.sharepoint.com |
| 4 | Set the Copilot scope | Set-SPOTenant –KnowledgeAgentScope AllSites (or IncludeSelectedSites / ExcludeSelectedSites / NoSites) |
| 5 | Verify the configuration | Get-SPOTenant | Select-Object KnowledgeAgentScope |
Confirm the Prerequisites
To successfully execute the setup, your tenant needs to meet these baseline requirements:
- An active subscription to Microsoft 365 (E3, E5, Business Standard, or Business Premium).
- Assigned Microsoft 365 Copilot licenses for all target users.
- An active modern SharePoint Online environment.
- SharePoint Online Management Shell version 16.0.26615.12013 or later.
Configure Tenant Availability via PowerShell
Copilot in SharePoint is currently in preview, and availability is controlled through the SharePoint Online Management Shell using the KnowledgeAgentScope parameter, the parameter retains this name during preview for compatibility, even though the feature is branded “Copilot in SharePoint.” This is confirmed, current syntax as of Microsoft’s own documentation.
First, open your PowerShell terminal as an administrator and make sure you’re running the latest module:
Update-Module -Name Microsoft.Online.SharePoint.PowerShell
Next, connect to your organization’s admin center:
Connect-SPOService -Url https://yourtenant-admin.sharepoint.com
Now define your Copilot scope using KnowledgeAgentScope. This parameter accepts four values:
- AllSites: Copilot in SharePoint is available on every site in the tenant.
- IncludeSelectedSites: Available only on the sites you list.
- ExcludeSelectedSites: Available everywhere except the sites you list.
- NoSites: Disabled tenant-wide, this is the parameter’s default value.
# Enable across all sites
Set-SPOTenant -KnowledgeAgentScope AllSites
# Or restrict to specific sites
Set-SPOTenant -KnowledgeAgentScope IncludeSelectedSites
Set-SPOTenant -KnowledgeAgentSelectedSitesList @(“https://yourtenant.sharepoint.com/sites/ProjectAlpha”)
# Verify your configuration
Get-SPOTenant | Select-Object KnowledgeAgentScope
A quick note on defaults: Microsoft rolls Copilot in SharePoint out as on by default for licensed users once the preview reaches your tenant, but the underlying parameter’s documented default is NoSites. Run the verification command above rather than assuming either state, don’t guess your tenant’s actual configuration.
If you see the error Set-SPOTenant: A parameter cannot be found that matches parameter name ‘KnowledgeAgentScope’, you likely have a conflicting or outdated SharePoint PowerShell module installed. Uninstall any older SharePoint admin modules via Add or Remove Programs, confirm nothing remains with (Get-Module -Name *SharePoint* -ListAvailable). Path, then reinstall the latest module and try again.
Following these commands ensures you maintain total governance over where AI is deployed across your corporate files.
User Guide: How to Use Copilot in SharePoint Online
Once the admin setup is complete, users can access AI tools directly inside modern SharePoint pages, document libraries, and lists. Knowing how to use Copilot in SharePoint lets your team skip tedious manual formatting and extract insights instantly.
Authoring Pages and Writing Content
When creating or editing a modern SharePoint page, you’ll see the Copilot icon within the rich text editor. You can use the AI assistant to:
- Draft new pages. Provide a simple prompt like “Create a landing page for our new wellness initiative,” and Copilot builds a structured template with text sections and web parts.
- Refine text. Highlight any text block to rewrite it, change the tone (e.g., from casual to professional), condense long paragraphs, or expand bullet points.
Analyzing Documents in Libraries
You no longer have to open and read dozens of long PDFs or Word documents to find specific details. When you navigate to a document library, select one or more files and launch the Copilot pane to summarize the selected files instantly, compare two contract versions to highlight key changes, or generate an FAQ document based on the file’s contents.
In practice, the workflow looks like this: open your document library, select the file (or files) you want to analyze, click the Copilot icon that appears, and Copilot generates a summary, comparison, or FAQ based on your prompt, without you needing to open each file individually.
Customizing Your AI: Working with SharePoint Agents
A major benefit of modern intranet AI is the ability to use and build specialized SharePoint agents. Every modern SharePoint site automatically includes a “ready-made agent” pre-scoped to the files and pages hosted on that specific site. This means users can ask site-specific questions immediately without any manual configuration.
For more advanced workflows, site editors can build custom agents through Microsoft 365 Copilot Agent Builder. You can create an agent tailored to a specific project by clicking the agent icon, choosing your knowledge sources, and writing custom instructions. Per Microsoft’s current documentation, a declarative agent built this way supports up to 100 SharePoint files, folders, or sites as knowledge sources, along with up to 50 OneDrive files, four public website URLs, and five Teams chat URLs if you want to broaden its scope beyond SharePoint.
You can then share this custom agent with your team or deploy it directly into Microsoft Teams to streamline collaborative workflows. If your team is struggling to structure these custom assistant pathways, our specialized Microsoft Teams Consulting Services can help you integrate and optimize your AI tools.
Why is my Copilot button missing on certain SharePoint pages?
The Copilot button may be missing because the feature is only supported on modern SharePoint pages and standard document libraries. You won’t see the Copilot floating button or chat pane on the classic SharePoint Home page, inside Viva Connections, or when viewing SharePoint sites directly inside Microsoft Teams tabs. Also verify that your administrator hasn’t excluded that specific site URL using the KnowledgeAgentScope PowerShell parameter.
Technical Comparison: Out-of-the-Box vs. Custom Agents
To help your development team choose the right path for AI integration, review how built-in SharePoint capabilities compare to custom-built solutions:
| Feature / Capability | Ready-Made SharePoint Agent | Custom Agent (Agent Builder) | Copilot Studio Agent |
| Creation Effort | Zero (automatic) | Low (few clicks) | Medium to high |
| Data Scope | Entire active site | Up to 100 SharePoint files, folders, or sites | SharePoint, OneDrive, and external APIs |
| Custom Prompts | No | Yes (tailored instructions) | Yes (advanced conversation logic) |
| Sharing Capabilities | Cannot be shared individually | Shared via direct links or Teams | Published globally across enterprise apps |
For Copilot Studio agents specifically, SharePoint knowledge sources carry their own documented limits worth knowing before you architect a deployment:
- Lists: up to 15 lists total, with individual lists capped at 35,000 rows and a cumulative limit of 120,000 rows across all 15, for example, three lists of 35,000 rows each, or twelve lists of 10,000 rows each. Separately, SharePoint list queries only return data from the first 2,048 rows regardless of how the list itself is sized.
- Files: if your tenant lacks a Microsoft 365 Copilot license in the same tenant as the agent, generative answers are limited to files under 7 MB each. With a Copilot license and tenant graph grounding with semantic search turned on, that cap rises to 200 MB.
- Folder structure: each SharePoint knowledge source can include up to 1,000 files across 50 folders and 10 levels of subfolders.
Microsoft doesn’t publish one fixed cap on the number of SharePoint site URLs you can add as separate knowledge sources, instead, the practical ceiling is governed by these per-source file, folder, and row limits, so it’s worth testing with your actual content volume rather than assuming a specific number of sites is safe.
Best Practices for a Safe and Successful Rollout
To ensure a smooth rollout of your newly enabled AI assistant, your implementation team should follow these steps:
- Clean up permissions first. Because Copilot respects existing user permissions, run a full sharing audit. Use Microsoft Purview to identify and remove wide-open “Share with everyone” links so users don’t accidentally surface sensitive corporate data. This is consistently the step that takes longest in the rollouts we’ve run. Expect it to take real calendar time, not an afternoon.
- Use a SharePoint.md file. You can place a single markdown file named SharePoint.md in the root of your site’s assets. This file acts as a permanent “what to know” guide, telling the site’s AI agent about naming conventions, brand rules, and library structures so it behaves consistently in every chat.
- Train users on prompting. Teach your staff to write detailed prompts that specify the context, source file, and output format. Instead of asking “Summarize this,” train them to prompt: “Write a three-bullet executive summary of this contract focusing on liability clauses.”
- Watch for common PowerShell rollout errors. Beyond the module-conflict error covered above, admins occasionally see the KnowledgeAgentSelectedSitesList parameter silently have no effect, this happens if you call it without first setting KnowledgeAgentScope to IncludeSelectedSites or ExcludeSelectedSites. Set the scope first, then the site list, in that order.
- Pilot before you scale. Because the feature is still in preview, start with a small group of sites rather than flipping AllSites tenant-wide on day one. Confirm behavior, gather feedback, and expand deliberately.
Restructuring complex document hubs to prepare for this deployment can be a daunting task. If your team is running through this checklist and finding more red flags than green ones, that’s completely normal, most tenants we assess require deep remediation rather than a simple checkbox review. If you need expert guidance to prepare your infrastructure, our specialized SharePoint Consulting Services can help you clean up permissions and secure your environment before your pilot launch.
Connect with an Expert
Ready to clean up your file permissions, configure tenant-level settings, and safely rollout AI across your intranet? Schedule a consultation with our SharePoint Consulting Services team at Code Creators today to build an optimized SharePoint environment designed for your enterprise!


