Why cannot the ADO wiki knowledge be searched as expected?

(1) Share

Report

Posted on by BZ-22010926-0 Microsoft Employee

I setup a bot to search and answer questions, which uses ADO wiki as knowledge.
But it cannot find the doc even through I give the exact wiki doc title.

Here is my bot: Overview - CCUI DRI Chatbot | Microsoft Copilot Studio
My doc is How to switch to No MSA or No AAD mode - Overview, which exists in ADO wiki.

Can someone help investigate why this happens?

Categories:

General topics

I have the same question (0)

All responses (2)

Answers (0)

Sort by

Suggested answer

rezarizvii 352 on at

Like (0)

Report
Copy link

Link copied!
Hi, hope you are doing well.

As far as I know, here are some reasons why the agent is unable to find your doc:

Retrieval from ADO Wiki is semantic, not keyword/title based

ADO Wiki indexing can be:

partial (not all pages indexed yet)

delayed (recent pages not picked up)

Titles alone are often not enough context for the retriever

If the content is short or lacks strong keywords, it may not rank high enough

I'd suggest you try some of these options:

Add more context in the page

Include phrases like:

“disable MSA authentication”

“no AAD mode setup”

“local auth configuration”

Don’t rely on title alone.

Ask better prompts

Instead of: How to switch to No MSA or No AAD mode

Try: How do I disable MSA or AAD authentication for local development?

Re-sync the knowledge source

Remove and re-add the ADO Wiki source

Or update it to trigger re-indexing

Let me know if any of these fix your issue.

Reza M. Rizvi
LinkedIn | Email
If this solved your issue, please mark it as ✅ Accepted Answer. If it helped, feel free to give it a 🩷 Like!

Was this reply helpful? Yes No
Suggested answer

Karan_Shewale_MSFT Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

This is a common limitation when using Azure DevOps (ADO) Wiki as a knowledge source in Microsoft Copilot Studio. Even if the document exists and you provide the exact title, Copilot may still fail to retrieve it because it does not perform exact keyword search like traditional search engines. Instead, it relies on indexed content + semantic retrieval, which introduces a few constraints. First, the ADO Wiki must be properly indexed through the connector—if indexing (crawl) is incomplete or delayed, the content won’t be available for retrieval. Second, permissions play a critical role: the connector only retrieves content that the configured service account has access to, so missing or partial permissions can result in no results. Third, Copilot does not guarantee deterministic retrieval—even when data is indexed, it only returns top relevant results based on semantic matching, so exact title matches can still be missed. This behavior is consistent across knowledge sources where partial indexing or retrieval limits can cause documents to not appear even though they exist.

In short, the issue is usually due to indexing delay, permissions, or semantic search limitations—not a configuration mistake. To improve results, ensure the ADO Wiki connector is fully indexed, verify permissions of the crawl/service account, and try querying with more contextual or descriptive prompts instead of exact titles.

Was this reply helpful? Yes No