Copilot usually can’t find your SharePoint documents for one of five reasons: you don’t have access to them, the site or library is excluded from search, the file hasn’t been indexed yet, the detail you’re asking about isn’t stored as metadata, or Copilot is misreading a column like a date. The first three stop documents appearing at all, and the last two give you slow, partial or empty answers even when the files are sitting right there.
The metadata cause catches people out because the documents are searchable in the ordinary sense. I tested it on a contracts library of 30-odd files with no columns at all. Asked to find every contract with a force majeure clause and a renewal date between 1 September and 30 November 2026, Copilot in SharePoint had to open and read every contract to check the clause wording and the dates. It got there, but it took a while, and I wouldn’t rely on that approach in a library of 10,000 documents.
The symptoms vary: Copilot says it can’t find a document you know exists, returns a list with gaps in it, or spends ages reading and comes back with an answer you don’t quite trust. Work through the causes below in order, because the first ones are the quickest to rule out.
Do you have permission to open the document?
Copilot works inside your existing permissions. It only surfaces SharePoint content you can already open, so if a colleague can see a file and you can’t, Copilot won’t show it to you either.
Check and fix: ask the person who can see the file to send you the link. If you land on an access request screen, there’s your answer. Ask the site owner for access, and if the file should be shared more widely, fix the permissions on the library or site rather than sharing files one at a time.
Is the site or library excluded from search?
A site owner can turn search off for a whole site or a single library, and Copilot’s broad answers rely on that same index.
Check the site: go to the gear icon, Site settings, then under Search choose Search and offline availability. Allow this site to appear in Search results should be Yes.
Check the library: go to the gear icon, Library settings, then Advanced settings. Allow items from this document library to appear in search results? should be Yes.
Check Restricted Content Discovery: your SharePoint admin can hide a site from organisation-wide search and from Copilot’s general answers without changing anyone’s access. If a whole site seems invisible to Copilot, ask your admin whether it’s restricted.
Has the file been indexed yet?
New or changed files are picked up in the next scheduled crawl, so a document you uploaded a few minutes ago may not appear straight away. Draft items aren’t crawled either, so a file that’s never had a major version published can stay out of results.
Fix: if a library has been missing from results for a while, go to Library settings, Advanced settings and choose Reindex Document Library. There’s a matching Reindex Site button on the site’s Search and offline availability page.
Is the answer stored as metadata, or buried inside each document?
When the documents are clearly there but the answers are slow or partial, check this first. If your question depends on a renewal date, a contract type or whether a clause exists, and that detail only lives inside the document text, Copilot has to read every file to answer you.
In my contracts library I added a Yes/No column called Force majeure and a date column for the renewal date, both as autofill columns so SharePoint reads each contract and fills in the value from a prompt. The force majeure prompt tested correctly on two contracts, one Yes and one No, before I ran autofill across the library. The setup is in how SharePoint autofill columns work.
With the same question, plus an instruction to use those two columns, Copilot read the library metadata instead of opening each file and answered far quicker. Once the information sits in columns, Copilot filters on it the way a view does, which I go into in turning SharePoint into a Copilot knowledge base with metadata.
Fix: work out the three or four things people ask about this library and make each one a column. If you’re still relying on folders to describe documents, why columns make documents easier to find than folders covers the switch.
Is Copilot reading your date columns correctly?
The metadata version of my test came back with zero results the first time, and still zero after I moved four renewal dates into the range. Asked to recheck how it was parsing the dates, Copilot corrected itself and returned seven contracts, which matched what was in the library after my edits.
Fix: if a date-filtered answer comes back empty or short, ask Copilot to recheck how it’s reading the date column before you assume the documents aren’t there. Then make the fix stick. When I asked Copilot to update the site’s memory, it wrote the date rule into the site’s SHAREPOINT.md file in the Agent Assets library, and a new chat with the same prompt returned the matching contracts without a nudge. What SHAREPOINT.md is and what goes in it explains the file.
How do you stop documents going missing in Copilot again?
Most of these fixes are one-off clean-ups. Prevention happens in how the library is designed, and this is what I’d set up on any library Copilot will be asked about.
- Design columns around the questions, before the documents arrive. Ask the people who use the library what they search for. Renewal date, contract type and owner belong in columns, and a folder called “Contracts 2026 final” tells Copilot nothing it can filter on.
- Let autofill do the data entry. Getting people to fill in metadata by hand is a pain, and it’s why plenty of libraries have none. An autofill column with a tested prompt removes that excuse.
- Build shared columns once with content types. If several libraries hold contracts, set the columns up on a parent content type so every library gets the same ones and your prompts and views work across sites.
- Save the rules Copilot gets wrong. Every time you correct Copilot on how to read a column, put the correction in SHAREPOINT.md so the next person doesn’t have to.
- Check search settings when a site is created, especially one copied from an old template.
The metadata works outside Copilot too. At the end of my test Copilot created a view of contracts with force majeure set to Yes and a renewal date in the period, which the whole team can use without opening a chat. To check a library against all of this, use my free Copilot-ready library checklist.
Frequently asked questions
Does Restricted Content Discovery stop people opening the documents? No. It changes discovery only. People can still search inside the site, Copilot still surfaces files they own or recently worked on, and permissions, sharing links and site membership stay as they were. On sites with 500,000 items or more, the setting can take more than a week to apply across the search index.
Can Copilot in SharePoint filter on any column type? For views, Copilot can filter on Choice, Number, Text, Date and Time, Yes/No, Currency and managed metadata columns. Views it creates are public to everyone using the library, and file contents are only processed in English.
Do autofill columns fix documents that are already in the library? Not on their own. Saving an autofill prompt covers new uploads. For existing files, select them, choose Autofill columns, then Autofill, and track progress under View autofill activity.
Is there a quick way to check a site’s search visibility?
Yes. Add /_layouts/srchvis.aspx to the end of the site’s address and check that Allow this site to appear in Search results is selected. The same page controls whether pages on a site with unique permissions get indexed.
