Answered

Copilot studio Agent Dataverse index issues

(1) Share

Report

Posted on by JH-15051849-0

We are testing a Copilot Studio agent and would like to test/use Dataverse as a data source. At a very basic level, the Dataverse table has been created with the following columns: Category Question and topic Answer to customer The challenge is that our Copilot Studio agent cannot find any relevant answers or data from our Dataverse table. Under ‘Knowledge’, our Dataverse table shows a status of: ‘Unknown’. It has remained in this state for several days. Removing and re-adding the knowledge source does not help. What are we doing wrong?

I have the same question (0)

All responses (3)

Answers (0)

Sort by

Sajeda_Sultana 189 on at

Like
a
(0)

Report
Copy link

Link copied!
Hi @JH-15051849-0,

It looks like the issue is probably that the Dataverse table isn’t being indexed properly, which is why it stays on “Unknown” and your agent can’t find any answers yet.

A few things to try:

Keep the table simple: Copilot Studio can be a bit sensitive to table structure. For testing, try a very simple table with just Question and Answer as plain text columns. If you’re also using Category, make sure Question is the field being indexed and Answer is the one returned in responses.

Confirm data and permissions: Check that the table actually has rows in it, and that your Copilot Studio agent has permission to read that Dataverse table in the current environment.

Check the environment: Make sure the agent and the Dataverse table are in the same environment. This is a common one that trips people up.

Nudge the indexing: “Unknown” usually means the indexing process never really started or failed quietly. Sometimes it helps to remove the Dataverse knowledge source, publish the agent, then add the table again as a knowledge source and publish once more.

Try a tiny test table: As a sanity check, create a brand‑new table with just 2–3 rows (only Question and Answer), connect that as a knowledge source, and see if it indexes and answers correctly. If that works, the problem is likely with the structure or data of your original table

✅ 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 @Sajeda_Sultana

Was this reply helpful? Yes No
Suggested answer

JH-15051849-0 6 on at

Like
a
(0)

Report
Copy link

Link copied!

I have tried removing the Dataverse source, publishing the agent, and then adding our original Dataverse table again. It still says “unknown”.

I also created a new Dataverse table with 4 rows and 2 columns:
Question
Answer

I get the same result even after publishing, removing the source, and adding it again.

It works with other data sources, for example when the agent uses a list or an Excel file.

Was this reply helpful? Yes No
Suggested answer

Sajeda_Sultana 189 on at

Like
a
(0)

Report
Copy link

Link copied!
Hi @JH-15051849-0,

Thank you for testing that. It points more toward the Dataverse indexing service itself not initializing correctly in your environment.

A few things that may still be worth checking:

Make sure this is a full Dataverse environment and not Dataverse for Teams, since support can differ.

Verify the Copilot Studio agent and Dataverse table are in the same environment.

Double-check security roles and table permissions so the indexing service can read the data.

If possible, try the same setup in another environment or trial tenant to see whether the behavior changes.

At this point, you’ve already covered the standard troubleshooting steps very thoroughly.

I’d recommend opening a Microsoft support ticket, because this increasingly looks like a platform-side indexing issue rather than something misconfigured in your setup.

✅ 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 @Sajeda_Sultana

Was this reply helpful? Yes No