Answered

How to transfer or pass a file attachment from one Agent to another in Copilot Studio?

(1) Share

Report

Posted on by TB-22061018-0

Hi everyone,

I am currently working on a scenario in Copilot Studio where I need to pass a file attachment from one Agent to another.

For example, if a user uploads a document to Agent A, how can I securely transfer that exact file (or its content) to Agent B for further processing?

Is there a recommended approach, specific variable type, or Power Automate flow integration required for this agent-to-agent file transfer?

Any advice or documentation you could share would be greatly appreciated. Thank you!

pic for blog.png

Your file is currently under scan for potential threats. Please wait while we review it for any viruses or malicious content.

Categories:

Building Copilot Studio chatbots in Microsoft Teams

Copilot Studio pre-built agents/templates

I have the same question (0)

All responses (3)

Answers (1)

Sort by

Verified answer

Giraldoj 923 Moderator on at

Like
a
(1)

Report
Copy link

Link copied!

Hi there,

Currently, there isn’t a supported way to transfer a file between agents through an orchestration file. The only workaround I can suggest is to provide the receiving agent (Agent B) with the file’s URL or path as part of the input.

Agent B could then use a “get file content” action to retrieve and read the file. However, this approach adds unnecessary complexity to the solution.

If you could elaborate on what Agent B needs to do with the document, it might be possible to simplify things. In many cases, a well-designed AI Builder prompt or a streamlined workflow could achieve the same result in a much simpler and more maintainable way.

Was this reply helpful? Yes No
Suggested answer

chiaraalina 2,425 Super User 2026 Season 1 on at

Like
a
(0)

Report
Copy link

Link copied!
Hi @TB-22061018-0

Maybe try the architecture that uses external storage combined with reference passing.

Step 1: User uploads file to Agent A
File captured via Question node or System.Activity.Attachments

Step 2: Agent A invokes storage flow
Agent A calls an Agent Flow/Power Automate and flow receives file metadata and base64 content from agent

Flow trigger: “When an agent calls the flow”

Input parameter: File (or Record with attachments)

Step 3: Flow stores file externally
File saved to SharePoint, OneDrive, or Dataverse with unique identifier. The file is saved to persistent enterprise storage.

Step 4: Flow returns reference
Returns file ID, URL, or metadata to Agent A. No base64, no binary -> only identifiers.
Example:

{
"fileId": "abc123",
"fileUrl": "https://tenant.sharepoint.com/...",
"fileName": "contract.pdf"
}

Step 5: Agent A passes reference to Agent B
Context variable or conversation transfer includes file reference

Agent A calls Agent B and the file reference is included: fileUrl, fileId

Step 6: Agent B retrieves file
Agent B calls flow to fetch file using reference

Was this reply helpful? Yes No
Giraldoj 923 Moderator on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @TB-22061018-0
Just following up to make sure you found the answer you were looking for. If you still need help or have any additional questions, feel free to reply and I’ll be happy to assist.

If my response helped you resolve the issue, please select ✅ Does this answer your question? This marks the question as answered and makes the solution easier for others to find.

Was this reply helpful? Yes No