Skip to content

Commit dc13439

Browse files
authored
Create README.MD
1 parent d6695cc commit dc13439

1 file changed

Lines changed: 23 additions & 0 deletions

File tree

DataverseIndexer/README.MD

Lines changed: 23 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,23 @@
1+
# Dataverse Indexer
2+
3+
Sample solution showing how to index the content of a SharePoint library into a Copilot Studio agent as knowledge source files, along with a workaround to get nice citations that point to the source files in SharePoint.
4+
5+
Benefits for this approach:
6+
1. Faster latency to get response.
7+
2. Better indexing to search for content and summarize answers.
8+
3. Embedded [image understanding](https://learn.microsoft.com/en-us/microsoft-copilot-studio/knowledge-add-file-upload#annotated-image-support-preview) for PDF files.
9+
4. Support for [more](https://learn.microsoft.com/microsoft-copilot-studio/knowledge-add-file-upload#supported-document-types) file types.
10+
5. Support files up to 512 MB.
11+
6. Clickable citations that point to the source file.
12+
7. Can work unauthenticated..
13+
14+
Downsides:
15+
1. No role-based access control – users of the agent have access to generated answers used with content from the uploaded files.
16+
2. Need to refresh the files (re-run / schedule the flow) to push updates from SharePoint to Copilot Studio.
17+
18+
Instructions:
19+
1. Import solution on your target environment (can be different from the one hosting your Copilot Studio agent).
20+
2. Update environment variables for the mandatory inputs.
21+
3. In your Copilot Studio agent, update the Conversation boosting topic with the provided YAML (make a backup of your current YAML for peace of mind, especially if you had customized the default behavior).
22+
4. Make sure the cloud flow is turned on
23+
5. Run the cloud flow.

0 commit comments

Comments
 (0)