How to Troubleshoot Copilot Returning Old SharePoint Results

You ask Copilot a question about a document in your SharePoint library, but it returns data from a version that is weeks or months old. This is a common complaint among Microsoft 365 users who rely on Copilot to surface current information. The root cause is usually a delay in indexing or a search scope that is not set to refresh. This article explains why Copilot shows stale SharePoint results and provides step-by-step fixes to force a fresh index and adjust your search settings.

Why Copilot Returns Old SharePoint Results

Copilot retrieves information from SharePoint by querying the Microsoft Search index. When you modify a document, SharePoint triggers a re-index of that item. However, the index update is not instant. The default crawl schedule for a SharePoint site is typically set to run every few hours. If you edit a file and immediately ask Copilot about it, Copilot will return the last indexed version, which is the old one. Additionally, the search schema’s freshness boost setting determines how much weight the search engine gives to recently modified items. If this boost is too low, older documents can appear more relevant even when newer versions exist. Another contributing factor is that Copilot may be configured to pull from a broad scope, such as the entire tenant, and may rank results based on relevance rather than recency. Finally, custom search scopes or content source configurations in the SharePoint admin center can exclude recent changes from the index entirely.

Steps to Force a Full SharePoint Re-index

The most direct way to fix stale results is to request a full re-index of the affected document library. This action tells SharePoint to re-crawl every item in the library and update the search index immediately.

1. Go to the document library settings
   Open the SharePoint site in your browser. Navigate to the document library that contains the outdated documents. Click the gear icon in the top-right corner and select Library settings.
2. Open advanced settings
   Under the General settings section, click Advanced settings.
3. Trigger a re-index
   Scroll down to the Re-index Document Library section. Click the Re-index Library button. A confirmation dialog appears. Click OK to start the process. The re-index may take from a few minutes to an hour depending on the size of the library.
4. Wait for the crawl to complete
   After triggering the re-index, wait at least 15 minutes before testing Copilot again. You can check the crawl status by going to the SharePoint admin center and selecting Search > Crawl Log. Look for the site collection URL and verify that the last crawl time is recent.
5. Test Copilot with the updated document
   Open Copilot in Microsoft Teams, Word, or the Copilot web app. Ask a question that references the document you updated. For example, ask “What is the status of the Q3 report in the Sales library?” If the result still shows old data, repeat the re-index step and ensure no other issues exist.

Adjust the Freshness Boost in the Search Schema

If re-indexing does not solve the problem, the search schema may be ranking older documents higher due to low freshness weight. You can increase the freshness boost to make recently modified items appear first.

1. Open the SharePoint admin center
   Sign in to the Microsoft 365 admin center as a SharePoint administrator. Under Admin centers, click SharePoint.
2. Navigate to search settings
   In the left navigation, click Search. Then select Manage Search Schema.
3. Edit the LastModifiedTime managed property
   In the managed properties list, locate LastModifiedTime. Click it to open the settings. Under Freshness boost, increase the value from the default 1.0 to a higher number, such as 2.0 or 3.0. A higher value gives more weight to documents modified recently. Click OK to save.
4. Trigger a full crawl for the site collection
   Return to the Search section and select Manage Search Schema is not required. Instead, go to Search > Crawl Log and request a full crawl of the affected site collection. This ensures the schema change is applied to all items.
5. Test Copilot again
   After the crawl completes, ask Copilot the same question. The results should now prefer the most recent version of the document.

Verify and Update Copilot Data Sources

Copilot might be configured to query a SharePoint site that no longer contains the current document, or it may be set to a broader scope that includes outdated content. You can check and adjust the data sources directly in the Copilot settings.

1. Open Copilot settings
   In any Microsoft 365 app that has Copilot, such as Microsoft Teams or Word, click the Copilot icon in the toolbar. In the Copilot pane that opens, click the three-dot menu (More options) and select Settings.
2. Review data sources
   In the Settings menu, look for a section labeled Data sources or Connected sources. This section lists the SharePoint sites and document libraries that Copilot can access. If the site containing your updated document is not listed, click Add source and enter the site URL.
3. Remove stale sources
   If a site or library is listed that no longer contains the current data, click the remove or disconnect button next to it. This prevents Copilot from pulling results from that source.
4. Save and test
   Click Save or Apply to confirm the changes. Then ask Copilot the same question again to see if the results are now up to date.

If Copilot Still Has Issues After the Main Fix

Copilot returns results from a different SharePoint site

This happens when Copilot is configured to search across the entire tenant and finds a similar document on another site. To limit the scope, use the Data sources setting in Copilot to restrict it to a specific site or library. Alternatively, include the site name in your query, such as “Show the latest version of the budget file from the Finance site.”

Copilot shows a document that was deleted

Deleted documents can remain in the search index for up to 24 hours. To remove them immediately, go to the SharePoint admin center and select Search > Remove Search Results. Enter the URL of the deleted document and click Remove Now. After the removal, the document will no longer appear in Copilot responses.

Copilot returns no results at all for a SharePoint library

This is often caused by the library being excluded from search. In the library’s Advanced settings, ensure that Allow items from this document library to appear in search results? is set to Yes. If it is set to No, change it to Yes and trigger a re-index.

Copilot Old Results vs Fresh Index: Key Differences

Item	Old Results (Stale Index)	Fresh Results (Re-indexed)
Data source	Last crawled version, possibly days old	Latest version from the current crawl cycle
Search schema freshness boost	Low or default value	Increased to prioritize recent modifications
Crawl schedule	Incremental crawl every few hours	Full crawl triggered manually or scheduled
Copilot data source scope	Broad tenant-wide scope	Restricted to specific site or library
Result accuracy	May show outdated or deleted content	Shows only current, indexed content

Conclusion

You now know how to force a full SharePoint re-index, adjust the freshness boost in the search schema, and update Copilot data sources to ensure it returns current results. Start by triggering a re-index on the affected document library. If the problem persists, increase the freshness boost for the LastModifiedTime managed property. As an advanced tip, you can create a scheduled PowerShell script that runs a full crawl every night for critical libraries to keep results consistently fresh without manual intervention.