Copilot studio Agent Dataverse index issues

Question

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?

Answer 1

The Dataverse knowledge source must be fully indexed and in a supported state before an agent can retrieve answers. A status of Unknown for several days indicates that Dataverse search or the knowledge configuration is not correctly set up.

Check and fix the following points:

1. Verify Dataverse search is enabled for the environment
   Copilot Studio agents require Dataverse search to use Dataverse-based knowledge sources. If Dataverse search is not enabled, the knowledge source cannot be prepared and will not reach Ready status.
   • Ask an admin to turn on Dataverse search for the environment as described in What is Dataverse search and Configure Dataverse search for your environment.
2. Ensure the table and columns are searchable in Dataverse search
   The table and the relevant text columns (for example, Question, Answer) must be configured as searchable so that Copilot Studio can index and query them.
   • In Power Apps, open the table, go to Data experiences → Views, open the Quick Find view, and make sure the relevant columns are included as searchable columns. Then Save and Publish the view so Dataverse search can index them.
3. Wait for indexing and preparation to complete
   After enabling Dataverse search and configuring searchable columns, Dataverse may take time to index data. For unstructured data and Dataverse-backed knowledge, indexing can take from several minutes up to longer depending on environment size. The Copilot Studio knowledge source will only be usable when its status changes from Preparing/Unknown to Ready.
4. Re-add the Dataverse table as knowledge after search is configured
   If the Dataverse table was added as a knowledge source before Dataverse search or searchable columns were configured, the system may not have indexed it correctly. Remove the Dataverse table from the agent’s knowledge, then add it again after confirming Dataverse search and searchable fields are correctly configured.
5. Confirm the knowledge status before testing
   Only knowledge sources with status Ready can be used in Test your agent. If the status remains anything else (such as Preparing, Unknown, or Error), the agent will not return answers from that table.

If, after enabling Dataverse search and re-adding the table, the status still does not move to Ready after sufficient time, treat it as an indexing issue in the environment and escalate through support with details of the environment and table configuration.

---

References:

• Unstructured data as a knowledge source
• Use SharePoint content for generative answers
• Test your agent's knowledge sources
• What is Dataverse search?
• Add Dataverse tables as a knowledge source
• Agent Inventory data source
• Add Power Platform connectors as knowledge (preview)