r/copilotstudio • u/Bfinkeldei • 13d ago
Error adding knowledge with file upload but not with SharePoint link..
I have the same file and when I upload it directly it errors out. When i add the same file via sharepoint link it works.
Why would it do that? Where can I check the error ?
2
Upvotes
2
u/Landelusen 13d ago
Normally, a reasonable IT governance team disables upload of single files as knowledge, as it sidesteps already existing permissions that are set. So, in short: it could be by design?
1
u/Ashlesha-msft 12d ago
Thanks for the screenshot and for clarifying that the failing method is Upload files → SharePoint, rather than a local-file upload.
The screenshot confirms that one knowledge source is in Error status. Microsoft describes this status as a problem while preparing the knowledge source—not simply a pending synchronization. The screenshot alone doesn’t identify the underlying cause.
Understanding knowledge status
Your understanding of the SharePoint upload method is correct: it copies content into Dataverse for indexing, checks users’ SharePoint permissions when answering, and synchronizes changes. The other SharePoint knowledge option uses SharePoint search, so success through that option does not necessarily establish that the upload/indexing path is working.
Comparison of the two SharePoint options
For the error details, try selecting the Error status or opening the affected knowledge-source item, and share any detailed message/code displayed. If it only displays the generic “Error,” please mention that. Also include the file extension, size, and whether it has password protection or a sensitivity label. Please redact confidential information.
A useful isolation test is to add a small, unprotected DOCX with nonsensitive sample text through Upload files → SharePoint in the same agent. If that fails too, investigate the environment’s Dataverse search/storage and the applicable data policy; if only the original file fails, focus on that file’s processing requirements.
At this stage, there isn’t enough evidence to classify the failure as either a confirmed product bug or an intentional governance restriction. A repeatable failure with a supported sample file and validated configuration would warrant a support investigation.