How are you handling user-uploaded file attachments in the new Copilot Studio agent experience?

(0) Share

Report

Posted on by OB-09100801-0

Hi everyone,

I’m testing user-uploaded file attachments in the new Copilot Studio agent experience and looking for practical guidance from the community.

Scenario:

A user attaches a file directly in the chat with a new Copilot Studio agent. I need the agent to pass that file to another component, such as:

- Power Automate / agent flow

- SharePoint or Azure Blob Storage tool

- custom connector / REST API tool

- connected agent

I’ve tried Power Automate, SharePoint/Blob tools, PowerFx, explicit agent instructions, different models, and connected-agent orchestration. So far, it looks like the new agent can maybe read the uploaded file internally, but does not expose the actual file binary/content bytes to tools, flows, or connected agents.

In classic Copilot Studio, there were topic-based patterns like System.Activity.Attachments. In the new agent experience, I haven’t found an equivalent mechanism.

Has anyone found a working way to:

1. access user-uploaded file content in the new agent experience;

2. pass that file to a flow/tool/connected agent;

3. or implement a reliable workaround?

If direct attachment passthrough is not possible, what approach are you using instead — SharePoint staging, Power Apps upload form, Dataverse file column, Azure Blob SAS URL, or passing only fileId/fileUrl/blobPath?

Any practical examples or lessons learned would be very helpful.

I have the same question (0)

All responses (2)

Answers (0)

Sort by

BD-02060115-0 2 on at

Like
a
(0)

Report
Copy link

Link copied!

Same issue for me in new agent experience. But in classic one agent was able to pass the excel file to the agent flow and then agent flow create file in sharepoint.

New agent experience, doesn't show the agent flow tool input related to the file

Was this reply helpful? Yes No
Suggested answer

Assisted by AI

sannavajjala87 515 Super User 2026 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!
Hi,

You’re not missing anything , what you’re seeing is the current limitation of the new Copilot Studio agent experience.
Right now, when a user uploads a file in chat, the agent can reference or reason over it internally, but the actual file (binary/content bytes) is not exposed to downstream tools like Power Automate, custom connectors, or even connected agents. There isn’t an equivalent to System.Activity.Attachments in the new experience yet, so you can’t directly pick up the file and pass it along.
Because of that, most working patterns today rely on indirection rather than passthrough. The approaches I’ve seen work reliably are:

Pre-upload pattern (recommended): Have users upload files to SharePoint, Blob, or Dataverse first, then pass the file URL/ID into the agent. The agent works with metadata, and your flow/tool retrieves the file directly from the source.

Power Apps front door: Use a simple Power Apps form for file upload and trigger your flow from there. The agent can then operate on the stored file reference.

Link-based handoff: Instead of passing file content, pass a fileUrl, itemId, or blobPath to your tool/flow, which then performs the actual processing.

Custom API pattern: If you control the backend, expose an endpoint that accepts a reference (not the binary), and let the API fetch the file using service credentials.

What doesn’t work reliably today:

Passing file bytes directly to a flow/tool

Accessing attachment content from agent memory/context

Chaining file attachments across connected agents

So in short: direct attachment passthrough isn’t supported yet, and the most stable design is to treat the agent as an orchestrator working with file references, not file payloads.
Hopefully this saves you some time , I went down the same path and ended up standardizing on SharePoint + URL handoff.

Was this reply helpful? Yes No