Upload File to SharePoint Document Library Code Apps Groups or EntraID Connector

(1) Share

Report

Posted on by JD-18061111-0

I am able to upload a file directly to SharePoint from a canvas app using either the Office365Groups connector.

This works fine in Canvas app. But the exact same request fails in CodeApps.

Office365Groups.HttpRequest(
            "https://graph.microsoft.com/v1.0/sites/" & nfDocumentSiteId & "/drives/" & nfDocumentDriveId & "/root:/" & Last(
                Split(
                    ctxDocumentPath,
                    "WISP Documents/"
                )
            ).Value & Concatenate(
                GUID(),
                ".jpeg"
            ) & ":/content",
            "PUT",
            Self.Media
        )

the above works perfectly and this is the request

However I cannot replicate this in PowerApps Code apps using the same connector (same id) my files are corrupted.

I have tired every permutation of content/content-type in body, in header.
 
Anyone who can get this working that would be great, also although the large file upload option works in dev, its blocked in production as the published power app cannot acess teh sharepoint endpoint directly.

Categories:

Building Power Apps

Power Apps Pro Dev & ISV

I have the same question (0)

All responses (2)

Answers (0)

Sort by

Suggested answer

11manish 2,730 on at

Like (0)

Report
Copy link

Link copied!

Since the upload succeeds but the resulting file is corrupted, the most likely root cause is that the Code App is sending encoded content rather than the raw

binary stream required by the Microsoft Graph /content endpoint.

The first thing I would verify is the actual payload being sent. If the Code App cannot reliably transmit raw binary data in production, the recommended

architecture is:

Code App -> Power Automate (or Azure Function) -> Microsoft Graph / SharePoint

This approach avoids binary serialization issues, works consistently across environments, and is currently the most supportable pattern for file uploads from Code

Apps.

Was this reply helpful? Yes No
Suggested answer

Valantis 6,184 on at

Like (1)

Report
Copy link

Link copied!

Hi @JD-18061111-0,

The corruption happens because Code Apps serialize binary content differently than Canvas Apps when passing it through connectors.

The Graph /content PUT endpoint expects raw binary and Code Apps can't reliably deliver that directly.

The confirmed working pattern: expose the file from the Code App as base64, pass it to a Power Automate flow via the Power Apps connector, decode it in the flow using dataUriToBinary() or base64ToBinary(), and upload to SharePoint using the SharePoint connector Create file action or directly via Graph.

This also solves your production issue where the published app can't reach the SharePoint endpoint directly the flow runs under its own connection credentials and doesn't require direct browser access to SharePoint.

Best regards,

Valantis

✅ If this helped solve your issue, please Accept as Solution so others can find it quickly.

❤️ If it didn’t fully solve it but was still useful, please click “Yes” on “Was this reply helpful?” or leave a Like :).

🏷️ For follow-ups @Valantis.

📝 https://valantisond365.com/

💼 LinkedIn

▶️ YouTube

Was this reply helpful? Yes No