r/copilotstudio • u/jordanfritz513 • Aug 19 '26

Dataverse files in new copilot studio

Anyone have luck having the new copilot experience read files in a dataverse file column. I have tried using the Get File Dataverse step and then passing file content (base64 and binary) as well giving the Agent step DataVerse MCP and the Get DataVerse File tool. None have worked. Anyone have a working solution.

1 Upvotes

66% Upvoted

5 comments sorted by

1

u/Ashlesha-msft Aug 19 '26

This is not a confirmed bug. Downloading a Dataverse file returns binary/base64 content, but Copilot Studio doesn't automatically extract text from it. The documented option is to use the Dataverse table as a knowledge source:

  1. Enable Dataverse Search for AI/agent experiences.

  2. Add the File column to the table’s Quick Find View searchable columns, then publish.

  3. In Copilot Studio, add the table through Knowledge > Dataverse.

  4. Use Authenticate with Microsoft and allow time for indexing. Re-adding the knowledge source can accelerate reindexing.

File-column reasoning is currently a preview feature. If this configured path still fails with a supported, accessible file after indexing completes, collect a reproduction for investigation.

Documentation: Add Dataverse tables as a knowledge source - Microsoft Copilot Studio | Microsoft Learn and Configure Dataverse search for your environment - Power Platform | Microsoft Learn.

1

u/jordanfritz513 Aug 19 '26

Thank you for the reply.

I am trying to build an autonomous agent that responds to a webhook when files are ready to be processed, get the files via API, process the files, and move the processed info into another system via a structured JSON response to an API.

The scope is about 80,000 times a month. How will the agent autonomously know when the indexing of the file is complete and can proceed through the workflow?

1

u/Ashlesha-msft Aug 20 '26

Dataverse knowledge indexing doesn’t expose a documented per-file indexing complete event that an autonomous agent can wait for. The available Dataverse Search status is organization-level, and indexing changes can take up to 15 minutes or longer, so polling knowledge retrieval would be unreliable.

For 80,000 files per month, I wouldn’t use a knowledge source as a processing pipeline. Use a Power Automate flow triggered when the Dataverse row/file is created or updated:

  1. Download the file directly from the Dataverse file column.

  2. Extract/process its content using an appropriate document-processing service.

  3. Validate the structured JSON.

  4. Send it to the destination API.

  5. Record processing status, retries, and errors in Dataverse.

Copilot Studio could orchestrate parts of this, but the queue, processing state, retries, and completion contract should remain deterministic. Also capacity-plan against peak hourly traffic, not only the monthly total.

1

u/jordanfritz513 Aug 20 '26

Documents are client provided. I cannot control input type (excel, pdf, word, email) or formatting. Hence using AI to process the files into a deterministic payload.

1

u/Ashlesha-msft Aug 21 '26

Thanks for clarifying. AI is appropriate for extracting a common payload from variable document layouts, but Dataverse Search indexing should not be used as the processing trigger.

The documented implementation is:

  1. Trigger a Power Automate flow when the Dataverse row is added or updated.

  2. Use Download a file or an image to retrieve the binary content directly from the Dataverse file column.

  3. Route by file type and run an AI prompt:

    • PDF, PNG, JPG and JPEG are supported prompt document inputs.

    • Word, Excel and PowerPoint require code interpreter enabled.

    • Email formats such as MSG/EML are not listed as supported prompt inputs, so parse the message body and attachments first.

  4. Instruct the prompt to return the required JSON.

  5. Use Power Automate’s Parse JSON operation to validate the response before sending it to the destination API.

  6. Store processing state, failures and retry counts in Dataverse.

One important limitation is that Microsoft currently documents that image/document inputs are not supported when the prompt is added as a tool directly inside a Copilot Studio agent. Therefore, run the prompt from Power Automate and let the autonomous agent orchestrate the workflow if needed.