You’re offline. This is a read only version of the page.
5
Hi everyone,
I’m currently using a Copilot Studio agent with a custom knowledge base. The knowledge is provided as a JSON file exported from our internal wiki. Each entry contains the fields title, url, and content.
In the agent’s instructions, I explicitly tell it to output the corresponding URL whenever it uses information from the knowledge base. This works in some cases, but I’m still running into several issues:
Sometimes the agent can’t find an answer at all, even though the relevant information definitely exists in the JSON.
Sometimes it hallucinates an answer and even invents a link, despite the instructions stating that it is not allowed to do this.
Sometimes it finds the correct information, but the returned link is wrong — instead of pointing to the specific referenced article, it links only to a parent or unrelated subpage.
Because of these issues, I’m wondering:
Should I use a different format instead of JSON for the custom knowledge base?
Is there a recommended or more reliable format for Copilot Studio to improve grounding and reduce hallucinations?
Share
Report
All responses (
Answers (
