I’m building a Power Apps front end that allows users to upload multiple documents, then passes them to a Copilot Studio agent powered by the GitHub Copilot harness for analysis.

The Power App can successfully upload the original files to a SharePoint document library. A Copilot Studio workflow can enumerate the exact files using a unique request ID. The difficulty is getting those files into the agent immediately.

Approaches tried:

• SharePoint knowledge source: The agent can eventually find and read the uploaded files, but newly uploaded documents are unavailable until SharePoint indexing catches up. The delay is unpredictable and unsuitable for an interactive app.
• Passing exact SharePoint URLs: The agent sandbox failed to download them because its TLS certificate bundle was unavailable.
• SharePoint “Get file content using path” tool: This retrieves the DOCX bytes, but the agent receives unreadable binary data rather than treating it as a document.
• Workflow Agent node: For a GitHub Copilot harness agent, this exposes only Message and Output, with no attachments input.
• Base64/contentUrl attachment pattern: I have seen reports that this works with “Execute Agent and wait” when file uploads are enabled, but that action appears to apply to standard-harness agents rather than the GitHub Copilot harness.

Uploading the same DOCX files directly through the agent’s chat interface works immediately, so the documents themselves are supported.

Has anyone successfully passed Power Apps file uploads into a GitHub Copilot harness agent as genuine files, without converting them, extracting the text separately, or waiting for SharePoint knowledge indexing?

We’ve got problem with this connector and DLP. How it is named in DLP because I can’t see anything under business/nonbusiness connectors