web
You’re offline. This is a read only version of the page.
close
Skip to main content
Community site session details

Community site session details

Session Id :
Power Automate - Using Connectors
Unanswered

Power Automate: Corrupted Images to Lakehouse Files via HTTP Pre-Auth Connector

(1) ShareShare
ReportReport
Posted on by 2

I'm using Power Automate with a custom HTTP pre-authorized connector to copy files from SharePoint to my Microsoft Fabric Lakehouse's "Files" section (ADLS Gen2).

My flow: SharePoint "Get file content" (base64) -> base64ToBinary() -> HTTP PUT/PATCH to ADLS Gen2 REST API. Images (JPG, PNG) are transferred, but they end up corrupted in the Lakehouse.

I can successfully copy the image from Lakehouse to SharePoint when i upload it manually. I'm not sure what i'm doing wrong. Any help is appreciated!

 
Categories:
I have the same question (0)
  • Michael E. Gernaey Profile Picture
    47,125 Super User 2025 Season 2 on at
    Power Automate: Corrupted Images to Lakehouse Files via HTTP Pre-Auth Connector
     
    Did you resolve this issue? If so can you share what you did?
     
  • Michael E. Gernaey Profile Picture
    47,125 Super User 2025 Season 2 on at
    Power Automate: Corrupted Images to Lakehouse Files via HTTP Pre-Auth Connector
     
    If you save the file content just in regular azure storage or in SharePoint more specifically or onedrive is the file viable?
     
    Let's verify that first.
  • MB1567 Profile Picture
    2 on at
    Power Automate: Corrupted Images to Lakehouse Files via HTTP Pre-Auth Connector

    @Michael E. Gernaey, thank you for responding! I tried using the "content" directly and also tried base64, but neither resolved the issue.

    My files are around 4 MB, and I even tested with a smaller file, but it still didn't work.

    I followed the approach mentioned here: https://hatfullofdata.blog/power-automate-save-a-file-to-onelake-lakehouse/
    https://hatfullofdata.blog/power-automate-save-a-file-to-onelake-lakehouse/. First, create the file and then append. The reason I had to do that was when I used the URI: https://onelake.dfs.fabric.microsoft.com/workspace/lakehouse/Files/test.jpg, it said I was missing a required header (An HTTP header that's mandatory for this request is not specified.). Then I tried the article about first creating the file and then appending and flushing it.

  • Michael E. Gernaey Profile Picture
    47,125 Super User 2025 Season 2 on at
    Power Automate: Corrupted Images to Lakehouse Files via HTTP Pre-Auth Connector
     
    Is it a requirement to make them base64? I haven't done this particular set of actions myself set so I always ask, when people say something is corrupted and they have used base64, was it really required.
     
    Also how big are the files? Do you need to Chunk them at all?
     
    Also just so I understand you are doing a PUT and then a PATCH, can I ask why? Again I have not specifically used those Actions in the manner, so I just want to make sure I am answering you properly. 

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Telen Wang – Community Spotlight

We are honored to recognize Telen Wang as our August 2025 Community…

Congratulations to the July Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Power Automate

#1
Tomac Profile Picture

Tomac 986 Moderator

#2
stampcoin Profile Picture

stampcoin 699 Super User 2025 Season 2

#3
Riyaz_riz11 Profile Picture

Riyaz_riz11 577 Super User 2025 Season 2

Featured topics