Copilot Studio SharePoint Knowledge Source Shows No Results: Fix

When you configure a SharePoint knowledge source in Copilot Studio, the expected behavior is that your custom copilot retrieves relevant documents and answers from the specified SharePoint sites. However, you may encounter a situation where the knowledge source returns zero results, even though documents exist in the SharePoint locations you added. This problem typically occurs due to permission misconfigurations, indexing delays, or incorrect data source setup within the Copilot Studio environment. This article explains the root causes behind empty SharePoint knowledge source results and provides step-by-step fixes to resolve the issue.

Why Copilot Studio SharePoint Knowledge Source Returns No Results

Copilot Studio uses the SharePoint search index to query documents from the sites you add as knowledge sources. When the knowledge source returns zero results, the most common root cause is that the Copilot Studio service principal lacks sufficient permissions to read the SharePoint content. Another frequent cause is that the SharePoint site or specific document library is not indexed by SharePoint search, which can happen if the site is a modern communication site without a default document library or if the site has been excluded from search by an administrator. Additionally, if the knowledge source was recently added, the indexing process may not have completed, leading to temporary empty results. Finally, incorrect configuration of the knowledge source itself, such as pointing to a site URL that does not exist or using an unsupported site type, can cause the issue.

Permission Requirements for SharePoint Knowledge Sources

For Copilot Studio to read SharePoint content, the service principal named Copilot Studio must have at least Read access to the SharePoint site and its document libraries. This permission is typically granted automatically when you add the knowledge source through the Copilot Studio interface, but manual intervention may be required in some tenant configurations. If your organization has strict permission policies, the service principal may be blocked.

SharePoint Search Index Dependency

Copilot Studio does not directly query SharePoint databases. Instead, it sends search queries to the SharePoint search index. If the SharePoint site is not indexed, or if the documents are stored in a location that is excluded from search, the knowledge source will return no results. Common scenarios include document libraries with unique permissions that are not indexed, or sites that have been configured to block search crawlers.

Steps to Fix SharePoint Knowledge Source Showing No Results

Follow these steps in order to diagnose and resolve the issue. After each step, test the knowledge source by asking your copilot a question related to the SharePoint content.

1. Verify the SharePoint Site URL
   Open Copilot Studio and navigate to the copilot that uses the SharePoint knowledge source. Go to Settings > Knowledge. Find the SharePoint knowledge source entry and note the site URL. Open that URL in a browser to confirm the site exists and contains documents. If the site is a modern team site, ensure it has a default Documents library with files. If the site is a communication site, verify that a document library exists and has content.
2. Check SharePoint Site Permissions for the Copilot Studio Service Principal
   In the Microsoft 365 admin center, go to SharePoint > Sites. Select the site used as the knowledge source. Click Permissions and then Advanced permissions settings. Under the Permission levels section, click Grant Permissions. Add the Copilot Studio service principal as a member with Read permission level. If you cannot find the service principal in the people picker, type its full name: Copilot Studio. Wait 5 minutes for the permission change to propagate, then test the knowledge source again.
3. Confirm SharePoint Search Indexing Status
   In the SharePoint site, go to Site settings > Search and offline availability. Ensure Allow this site to appear in search results is set to Yes. For the specific document library, go to Library settings > Advanced settings and confirm that Allow items from this document library to appear in search results is set to Yes. If these settings were changed, wait up to 15 minutes for the search index to update, then test the knowledge source.
4. Remove and Re-add the SharePoint Knowledge Source
   In Copilot Studio, go to Settings > Knowledge. Delete the existing SharePoint knowledge source. Click Add knowledge source and select SharePoint. Enter the exact site URL again. If your organization uses multiple SharePoint tenants, ensure you select the correct tenant. After adding, wait 10 minutes for the indexing process to complete, then test the copilot.
5. Verify Tenant-Wide SharePoint Search Settings
   In the Microsoft 365 admin center, go to SharePoint > Search. Click Manage search schema and ensure that no custom managed properties are blocking the default content. Also, check Search result sources to confirm that the default Local SharePoint Results source is active and includes the site. If your tenant uses a custom search result source, add the site to that source.
6. Check for Content Type Limitations
   Copilot Studio can index files in common formats like DOCX, PDF, PPTX, and TXT. If your SharePoint library contains only unsupported file types such as images, videos, or ZIP archives, the knowledge source will return no results. Verify that at least a few documents in supported formats exist in the library.

If Copilot Studio Still Shows No Results After the Main Fix

If the knowledge source still returns empty results after completing the steps above, investigate these additional scenarios.

Copilot Studio Returns No Results for a Specific Document Library

If you added a specific document library path instead of the entire site, verify that the library is not excluded from search. In SharePoint, go to Library settings > Advanced settings and confirm Allow items from this document library to appear in search results is set to Yes. Also, check if the library has unique permissions that block the Copilot Studio service principal. If needed, break permission inheritance and grant Read access to the service principal.

Knowledge Source Works in One Tenant but Not Another

This issue points to a tenant-level configuration difference. Compare the SharePoint search settings between the working and non-working tenants. Pay special attention to SharePoint admin center > Search > Result sources and Search schema. Also, verify that the Copilot Studio service principal is not blocked by a conditional access policy in the non-working tenant. Work with your tenant administrator to review Microsoft Entra ID service principal permissions.

Knowledge Source Returns Results in Preview but Not in Production

If your copilot is published and the knowledge source works in the Copilot Studio test panel but not in the production environment, the issue is likely related to authentication. In Copilot Studio, go to Settings > Security > Authentication. Ensure that the authentication method is set to Microsoft Entra ID or No authentication depending on your deployment. If you use Microsoft Entra ID, confirm that the app registration has the correct API permissions for SharePoint. If you use No authentication, the copilot uses the service principal permissions you configured earlier, so double-check those permissions.

Copilot Studio SharePoint Knowledge Source vs Manual SharePoint Integration

Item	Copilot Studio Knowledge Source	Manual SharePoint Integration via API
Setup effort	Low — configured through GUI	High — requires custom code and API calls
Permission management	Uses Copilot Studio service principal automatically	Requires manually creating and managing a service principal
Search dependency	Relies on SharePoint search index	Can use Graph API or direct SharePoint REST calls
Supported content	Documents in libraries on indexed sites	Any SharePoint content accessible via API
Scalability	Limited to 5 sites per copilot	No built-in limit

After completing the steps in this article, you should be able to see relevant documents from your SharePoint knowledge source in Copilot Studio responses. If the issue persists, consider using the SharePoint Graph connector in Copilot Studio as an alternative, which bypasses the search index dependency. As an advanced tip, use Copilot Studio analytics to review which queries returned zero results and cross-reference them with the SharePoint search logs to identify unindexed content.