Copilot Cannot Find SharePoint Files After Connector Setup: Fix

You set up the SharePoint connector for Microsoft Copilot, but Copilot still cannot find or search your SharePoint files. This problem occurs because the connector setup alone does not grant Copilot permission to read the files. The root cause is missing or misconfigured Microsoft Graph data source settings and user permissions. This article explains the exact permissions and configuration steps required to make SharePoint files visible to Copilot.

Why Copilot Cannot Access SharePoint Files After Connector Setup

The SharePoint connector in Microsoft 365 does not automatically grant Copilot permission to index or retrieve files. The connector establishes a communication channel between Microsoft 365 and SharePoint, but Copilot requires explicit data source configuration in the Microsoft 365 admin center. Without this configuration, Copilot will not search SharePoint content even if the connector shows as connected.

Two additional layers control access: user permissions on the SharePoint site and the Copilot plugin setting. A user must have at least Read permission on the SharePoint site where the target files reside. Even with correct permissions, Copilot will not search SharePoint files unless the SharePoint plugin is enabled in the Copilot pane. These three conditions must all be met.

Microsoft Graph Data Source Setting

Copilot uses Microsoft Graph to ground its responses. The data source setting in the admin center tells Copilot which Microsoft 365 services it can read. If SharePoint is not listed as a data source, Copilot will not search SharePoint files regardless of the connector status. This setting is separate from the SharePoint connector and must be enabled explicitly.

SharePoint Site Permissions

Each SharePoint site has its own permission set. A user who is not a member of the site or does not have explicit Read access will be invisible to Copilot. This includes external users and guests. Copilot respects the same access control lists that SharePoint uses for direct file access.

Copilot Plugin Toggle

Copilot uses plugins to extend its search capabilities. The SharePoint plugin must be turned on for each user. This toggle is not enabled by default after connector setup. Users must enable it manually in the Copilot pane settings.

Steps to Make SharePoint Files Visible to Copilot

Complete these steps in order. Each step addresses one of the three root causes described above.

1. Enable SharePoint as a data source in the Microsoft 365 admin center
   Go to the Microsoft 365 admin center. Select Settings then Copilot. Under Data sources, ensure SharePoint is checked. If it is not checked, check it and select Save. This setting tells Copilot to include SharePoint content in its search index.
2. Verify user permissions on the SharePoint site
   Open the SharePoint site where the files are stored. Select Settings then Site permissions. Confirm the user is listed in the Site members group or has been granted explicit Read permission. If the user is missing, add them and assign the Read permission level. Changes take effect immediately.
3. Enable the SharePoint plugin in Copilot
   Open Copilot in Microsoft Teams or on the web. Select the Copilot pane icon. Select Settings then Plugins. Locate SharePoint in the list and toggle it to On. This enables Copilot to query SharePoint files during conversations.
4. Test file discovery with a specific query
   In the Copilot chat, type a query that includes a known file name or phrase from the SharePoint site. For example, type Find the sales report for Q3 2024 in SharePoint. Copilot should return the file if all permissions and settings are correct. If not, repeat steps 1 through 3 and verify the file is stored in a document library indexed by SharePoint.

If Copilot Still Cannot Find SharePoint Files

Some issues require additional troubleshooting beyond the three main causes. The following scenarios are common after connector setup.

Copilot returns no results for SharePoint queries

This usually indicates that the SharePoint site is not indexed by Microsoft Search. Go to the SharePoint admin center. Select Search then Manage search schema. Ensure the site URL is listed under Content sources. If the site is missing, add it and run a full crawl. Full crawls can take up to 24 hours to complete.

Copilot returns files from OneDrive but not SharePoint

This happens when the SharePoint data source is enabled but the user has not granted Copilot permission to read SharePoint content. In the Copilot pane, select Settings then Data permissions. Confirm that SharePoint is toggled on. This is a per-user permission that is separate from the admin data source setting.

Copilot returns outdated or incomplete file versions

Copilot indexes files based on the last modified date. If a file was recently updated, Copilot may return an older version. Force a re-index by opening the file in SharePoint, editing it, and saving it again. Alternatively, use the SharePoint admin center to request a re-index of the document library.

Copilot Pro vs Copilot for Microsoft 365: SharePoint File Access

Item	Copilot Pro	Copilot for Microsoft 365
SharePoint connector	Not available	Included with subscription
Data source configuration	Not required	Required in admin center
User permission requirement	None	Read access on SharePoint site
Plugin toggle	Not available	Must be enabled per user
File types supported	Public web content only	.docx, .xlsx, .pptx, .pdf, .txt

Copilot Pro does not include SharePoint integration. Only Copilot for Microsoft 365 can connect to SharePoint files. The table above summarizes the key differences in setup and access requirements.

After completing the three configuration steps, Copilot will successfully find and return SharePoint files. Start by testing with a single file on a site where you have Read access. If you manage multiple SharePoint sites, repeat the data source verification and plugin toggle for each site that needs to be searchable. For quick re-indexing, use the SharePoint admin center request tool instead of editing files manually.