Copilot Studio

'SharePoint sites pages as Knowledge are shown as files in Copilot Studio'

(3) Share

Report

Posted on by bitverse

Hello,

I have been developing Copilot Studio agent with SharePoint as Knowledge.

Documents library (Contains excel glossary and pdf files with table)
Site pages

Now I added this as knowledge in Copilot Studio agent but site pages shows as files so document folder. You can see in the screenshot below:

When I interact with agent, it only answers from document library and not site pages. Meaning, it does not answer anything from site pages.

Same agent, i have developed in M365 Agent builder. It was able to add SharePoint site pages and document library and classified as SharePoint in type.

I have tried adding dynamically and also URI directly but same result.

How do i fix this?

Thanks

Categories:

General topics

Bot administration

Copilot Studio skills development

I have the same question (0)

All responses (5)

Answers (0)

Sort by

Vish WR 2,244 on at

Like (1)

Report
Copy link

Link copied!

@bitverse

For testing, can you try adding the site URL instead of the individual library

Was this reply helpful? Yes No
Suggested answer

Valantis 4,803 on at

Like (1)

Report
Copy link

Link copied!

Hi @bitverse,

This is expected behavior based on how you added the knowledge source, and it explains why site pages aren't being used.
In Copilot Studio there are two different SharePoint options in the Add knowledge dialog and they work completely differently:

1. The SharePoint option under the file upload section this is what you used. It uploads files and folders into Dataverse, which is why everything shows as type "Files". It works for documents but site pages are not supported here.

2. The SharePoint option in the Featured section this is the full SharePoint connector integration. It shows as type "SharePoint" (like you see in M365 Agent Builder), supports site pages, and creates a live connection to SharePoint rather than uploading copies into Dataverse.

To get site pages working, remove the current knowledge source and re-add it using the Featured SharePoint option instead. In the Add knowledge dialog, look for SharePoint in the Featured/top section, paste your site URL there, and add it. This is the path that supports modern SharePoint pages and is the same connector M365 Agent Builder uses.

One limitation to be aware of: classic ASPX pages are not supported, only modern SharePoint pages. Also SharePoint sites with custom CSS or accordion navigation menus won't generate answers.

Ref: https://learn.microsoft.com/en-us/microsoft-copilot-studio/knowledge-add-sharepoint

Best regards,

Valantis

✅ If this helped solve your issue, please Accept as Solution so others can find it quickly.

❤️ If it didn’t fully solve it but was still useful, please click “Yes” on “Was this reply helpful?” or leave a Like :).

🏷️ For follow-ups @Valantis.

📝 https://valantisond365.com/

💼 LinkedIn

▶️ YouTube

Was this reply helpful? Yes No
Suggested answer

11manish 1,922 on at

Like (1)

Report
Copy link

Link copied!

It seems that the issue occurs because Copilot Studio does not fully support SharePoint Site Pages as a structured knowledge source.

While document libraries are properly indexed, site pages are treated as files and are not semantically processed, so the agent cannot retrieve answers from them.

This is why it works in M365 Agent Builder, which uses a different indexing approach.

To fix this, you should either convert site page content into documents (PDF/Word), sync the content into a document library using Power Automate, or use

Azure AI Search as an indexing layer for a more robust enterprise solution.

Was this reply helpful? Yes No
Suggested answer

Haque 2,323 on at

Like (1)

Report
Copy link

Link copied!
Hi @bitverse,

Let's do bit of "Rootcase Analysis":

Part-1: Site Pages appearing as files in the document library knowledge source—is expected behavior because SharePoint treats Site Pages as a type of file stored in a library. When you add a SharePoint site or document library as a knowledge source in Copilot Studio, it indexes all files it finds, including Site Pages, which show up alongside documents like Excel or PDFs.

Part-2: Why the Copilot Studio agent answers only from the document library content but not from Site Pages? It likely means that although Site Pages are included in the knowledge source, the indexing or retrieval for those pages is not effective or prioritized.

Part-3: Is M365 Agent builder is smarter? Your observation is consistent with differences between Copilot Studio and M365 Agent Builder, but here are two cents:

M365 Agent Builder tends to classify SharePoint content more granularly, recognizing both Site Pages and Document Libraries distinctly as SharePoint types, which helps the agent understand and retrieve content from both sources effectively.

Copilot Studio, on the other hand, often treats Site Pages as files within a document library, which can cause them to appear as generic files and sometimes limits the agent’s ability to retrieve answers from Site Pages content, especially if the indexing or extraction is less optimized for page content.

What you can do to improve Site Pages inclusion:

Verify that Site Pages are properly indexed and included in the knowledge source configuration: Sometimes you need to explicitly configure the knowledge source to crawl and extract text from Site Pages.

Consider extracting key content from Site Pages into a more structured format (e.g., export important text to documents or Dataverse tables) that the agent can query more reliably.

Test queries specifically targeting Site Pages content to see if any answers are returned, which can help diagnose if the issue is indexing or retrieval.

Review the knowledge source refresh schedule and logs to ensure Site Pages content is up to date and indexed.

If Site Pages content is critical, consider creating a dedicated knowledge source for Site Pages and tune its settings separately from the document library.

I am sure some clues I tried to give. If these clues help to resolve the issue brought you by here, please don't forget to check the box Does this answer your question? At the same time, I am pretty sure you have liked the response!

Was this reply helpful? Yes No
Haque 2,323 on at

Like (2)

Report
Copy link

Link copied!

Hi @bitverse,

Was following up - if your expected answers found or not. If you think you got clues - please mark the answer verfied. Thanks

Was this reply helpful? Yes No