Unanswered

Where are uploaded documents used for Generative AI saved in Dataverse?

(1) Share

Report

Posted on by Wuertz

Hello,

I'm looking to locate where in Dataverse the documents are stored for generative AI purposes. Currently deploying the chatbot to Teams prevents the bot from reading documents on SharePoint. That's a use case for me. Until that functionality is available, I want to use a PowerAutomate flow to skip the CoPilot step and add documents to the Dataverse directly.

For example, slides and FAQ from standing Monday calls. I receive the email and use the flow to post them to Dataverse for use in Copilot bot deployed to teams. Thank you.

Categories:

General topics

I have the same question (0)

All responses (8)

Answers (0)

HenryJammes on at

Like (0)

Report
The SharePoint data source generative answers should work in Teams. For that you need to properly setup your app registration and single-sign on:
Configure user authentication with Microsoft Entra ID - Microsoft Copilot Studio | Microsoft Learn
Generative answers with Search and summarize - Microsoft Copilot Studio | Microsoft Learn
Configure single sign-on for the Microsoft Copilot Studio app in Teams - Microsoft Copilot Studio | Microsoft Learn

To answer your question, files are stored in the Chatbot Subcomponent (botcomponent) table, in the filedata (FileData) column.

For that, you first need to create the row in Dataverse:

Then attach the file to it:

Was this reply helpful? Yes No
Wuertz 8 on at

Like (0)

Report

Appreciate the response Henry, I will work on the former and test the latter in case I run into issues!

Was this reply helpful? Yes No
jamesbio 29 on at

Like (0)

Report

Hi @HenryJammes, I wanted to see if this is correct?

We have similar requirements to the user above and are currently using an external flow with the addition of a custom API that is fed into the flow and the response is read back into the bot. This is working and we have been using it for a while (even before switching from OpenAI directly to Azure's OpenAI) in production.

We would like to be able to reference SharePoint sites completely within the PowerUsers/CoPilot environment without requiring users to follow the unfriendly flow of needing to sign in within the chat and just automatically using their credentials from within Teams. We don't currently use this in production and rely on our customized APIs.

Side note: It also causes confusion with business users that think they can just set up a bot, reference a SharePoint site, publish, and walk away. They then wonder why it doesn't work in production and create tickets. We are a public company with many users (and a large contract with Microsoft), so this in itself creates a backlog for our IT support (mostly handled by ServiceNow).

If we follow: https://learn.microsoft.com/en-us/microsoft-copilot-studio/configure-sso-teams

when publishing a CoPilot with Generative AI to Teams you can bypass this step for users?

In this step instead of setting manual would you select Teams?

If I'm missing something can you please outline what is needed? I am omitting a lot of material from the three links you referenced which we have read in the past, but from the first link our understanding was it had to be set to Manual for SharePoint or OneDrive:

Thank you.

Was this reply helpful? Yes No
HenryJammes on at

Like (0)

Report

Hi @jamesbio, agreed that there is cliff for no-code/low-code user creating a bot with a SharePoint data source when deploying it means registering an app, configuring it appropriately (with admin consent for the API permissions) and deploying it to Teams (I believe through the app manifest so that SSO works).

Was this reply helpful? Yes No
Wuertz 8 on at

Like (0)

Report

Hi Henry, I've worked with my IT who followed the instructions you linked to but the Teams bot still can't generate answers from internal SharePoint sites. It can answer when testing within Copilot and has been published. Any other advice?

Was this reply helpful? Yes No
HenryJammes on at

Like (0)

Report

Do you have screenshots for your app registration and API permission?

Was this reply helpful? Yes No
Wuertz 8 on at

Like (0)

Report

Was this reply helpful? Yes No
jamesbio 29 on at

Like (0)

Report

Okay, we would like to devote some time to check this out. Our current workflow does the job with our own APIs and consuming SharePoint data.

It looks like the documentation may have been updated even though the recent update shows a couple of months ago. There was a warning you can see from the red screenshot and the highlighted section regarding SharePoint and OneDrive data.

Is it now possible to allow SSO credentials from the user's Teams session and not have to configure the manual setup as before (red screenshot)?

Or will the end result still require the user to click login from within the app and enter a code from their email, phone, or authenticator?

Was this reply helpful? Yes No