Add a Dataverse knowledge source
Integrating Dataverse tables as your knowledge source allows you to ground your copilot in the data contained in your tables. This process involves adding synonyms and glossary definitions of the tables and columns in your data. For more information, see Improve copilot responses from Microsoft Dataverse.
To add Dataverse tables as a knowledge source, perform the following steps:
Open the copilot.
Select Add knowledge from either the Overview or Knowledge pages.
Select Dataverse (preview).
Locate one or more of your Dataverse tables to add. Up to 15 Dataverse tables can be added per knowledge source. To narrow your selections, use the search field.
Note
Table recommendations are based on the name of your copilot.
Preview the tables to ensure the appropriate tables were added. The preview only displays 20 rows and a set of columns, however, all the rows and columns are included in the knowledge source.
Review the knowledge name and description. The description should be as detailed as possible, especially if generative AI is enabled, as the description aids AI orchestration.
Optionally, to help improve the quality of the answers, add synonyms to columns of the tables that you selected. Select the Back button to accept changes.
Optionally, to help improve the quality of the answers, add a glossary to knowledge sources. Select the Back button to accept changes.
Select Add to finish adding the knowledge source.
Synonyms and Glossary
Synonyms, Glossary entries, and definitions for the Synonyms and Glossary entries aid in AI orchestration. They provide grounding data to improve generated responses. By providing extra information for the AI to understand and interpret the information in the tables, you increase the likelihood of the AI to recognize your users requests, and return responses based on the information provided to the AI.
For scenarios where your Dataverse table contains a column composed of numeric values, you need to provide a synonym for the AI to understand what's in the column. For example, your copilot is providing travel assistance, and the Dataverse table contains a column named "cr_123_abc" that uses flight numbers to correspond to cities.
However, the AI doesn't know how to qualify this information, unless explicitly told how it should be interpreted. So, a description for this column is added: "cr_123_abc represents the departure city for each flight represented by the flight code."