Copilot Studio

Copilot Studio with Adobe PDF Services

(3) Share

Report

Posted on by CU07110950-0

I am trying to build a Copilot Studio solution with the following requirements:

Allow users to upload a PDF file
Perform Adobe PDF Services operations (e.g., compressing the PDF)
Return the processed file back to the user

I have attempted two approaches in Copilot Studio:

Implementing the flow as a custom topic
Creating it as a tool by importing the Adobe PDF Services action for PDF compression

Both the method return a similar error

However, both approaches were unsuccessful.

The same requirement has been successfully implemented in Power Automate, where the process works flawlessly using file uploads and updates via SharePoint.

Has anyone encountered a similar scenario in Copilot Studio, or are there recommended patterns or limitations I should be aware of when handling file uploads and returning processed files in Copilot Studio?

Categories:

Topic creation & management

I have the same question (0)

All responses (3)

Answers (0)

Sort by

Suggested answer

Giraldoj 903 Moderator on at

Like (0)

Report
Copy link

Link copied!

Hi there!

What about trying Agent Flows?

They work similarly to Power Automate, and you can call an Agent Flow directly from your Copilot Studio agent. This approach will help you debug issues more effectively.

Honestly, making custom logic calls directly from the agent didn’t work very well for me.

Was this reply helpful? Yes No
Karan_Shewale_MSFT Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

In Microsoft Copilot Studio, handling end-to-end file operations (upload → process → return file) is currently limited compared to Power Automate. While Adobe PDF compression works reliably in Power Automate, Copilot Studio does not yet fully support returning binary file outputs (such as processed PDFs) back to users through custom topics or tools. Even when using Adobe PDF Services actions, Copilot Studio is optimized for text-based interactions and structured data, not file streaming or downloads. The recommended pattern is to offload file upload and processing to Power Automate or an external API, store the result in SharePoint or Blob Storage, and then return a download link or confirmation message to the user in Copilot Studio, rather than the file itself.

Was this reply helpful? Yes No
MS-24021619-0 2 on at

Like (0)

Report
Copy link

Link copied!

Please disregard my questions/request below, I found the solution in the meantime: the Copilot Studio can access pdf files via Microsoft 365 Copilot (Search) MCP (Frontier) server. Keeping the post below for context.

I have the same issue. While I understand @KS-17111010-0's previous response, I am struggling a little with the implications.

I have an agent that is triggered when an MS Form is completed. In the form, the user has to input a link to a SharePoint folder where documents are stored. The AI agent accesses the folder via the Microsoft SharePoint and OneDrive MCP and is supposed to analyse the document(s) stored in the folder. If the documents are .docx files, this works perfectly via the Microsoft Word MCP. However, if the documents stored in the SharePoint folder are PDF files, the agent cannot access them and fails, providing generic recommendations instead of creating file-specific responses.

I am puzzled by this, as M365 Copilot has no issue accessing SharePoint and analysing PDF files stored in it, and I thought that the Agent 365 tooling servers were supposed to enable the M365 Copilot experience within Copilot Studio. Am I missing something (e.g. the easy solution) here? Any ideas how to solve this?

Was this reply helpful? Yes No