Blog Post

Azure Integration Services Blog
1 MIN READ

Logic app creates unreadable base64 encoded files using HTTP action on Azure Blob Storage

talsaifi's avatar
talsaifi
Icon for Microsoft rankMicrosoft
Dec 21, 2020
When the logic app creates a file using HTTP action PUT method on Azure Blob Storage, the file cannot be read as it appears as corrupted when trying to open the file.   The main reason for this i...
Updated Dec 21, 2020
Version 1.0
logic apps
c-sekhar's avatar
c-sekhar
Copper Contributor
Sep 06, 2023

I'm using base64ToBinary while using the CreateBlob v2 - in the body. I also specify the Content Type as well to indicate its an Excel FIle. 

When I create the file and view the file content, the content matches exactly to the content when I manually upload in the portal - into the same container. But the file size is different - the CreateBlob shows a significantly larger file size. And when I download the files - the one directly uploaded through portal opens just fine in Excel but the one uploaded through CreateBlob doesn't. 

When I compare the metadata, I see that the CreateBlob file has the metadata attributes that of a ZIP file and not a EXCEL file. But the file that I uploaded manually in the portal has the metadata which represents a Excel file. 

Can someone please help?