Share via

Large Excel file as Knowledge source

Mayank Gupta, Vodafone 0 Reputation points
2026-03-23T17:00:56.5166667+00:00

I have created an copilot studio agent and ingested an Excel containing around 17k rows in knowledge source via SharePoint folder document library , however i notice agent is not able to retrieve read all rows specifically post 1500 rows agent do not retrieve ?

Please note excel is formatted as table . Is there a limit of how many rows can be read by an agent ?

Best Regards

[Moderators note: personal information removed]

Microsoft 365 and Office | Excel | For business | Windows
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Hendrix-C 13,005 Reputation points Microsoft External Staff Moderator
    2026-03-23T19:08:46.54+00:00

    Hi @Mayank Gupta, Vodafone,

    According to your concern, refer to Quotas and limits - Microsoft Copilot Studio | Microsoft Learn, Microsoft Copilot Studio limits focus on file sizes, counts and source types, not row limits. However, from practical experience and community sharing, Excel seems to be not a first-class unstructured source. Based on Copilot Studio: Using Structured Data in Excel as SharePoint Knowledge Source, the same tabular content indexes more reliably when embedded in Word or PDF. The author did a side-by-side tests, Copilot Studio often retrieves from the DOCX/PDF copy but not from the Excel copy even though both are in the same SharePoint folder.

    Therefore, the suggested practical approach for your situation will be:

    1/ Treat the data as structured and fetch rows via a Tool/Action.

    Instead of relying on indexing of the .xlsx, expose the table through an Excel Online connector or an agent flow that reads rows based on the user’s query (with filters, pagination). This bypasses the RAG index and queries the sheet directly at runtime.

    2/ Convert the Excel table to a document people can cite (DOCX/PDF) and use it as knowledge.

    If your use case is “answer policy/lookup questions from a table,” export the relevant table(s) to DOCX or PDF and store those in the same library. As I mentioned from the community sharing above, retrieval is much better from DOCX/PDF compared to xlsx. You can also keep the documents reasonably sized (split by category or letter range) and a simple layout (no merged cells, minimal images).

    Hope this information may help. If you have any questions or need further assistance, please feel free to reach out in the comments under this post. I will be happy to assist you further.

    Thank you for your understanding and cooperation. I'm looking forward to your response.


    If the answer is helpful, please click "Accept Answer" and kindly upvote it.

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.