decompress a True Flat .zip file (no parent folder) in azure blob storage using azure logic app Standard

Question

decompress a True Flat .zip file (no parent folder) in azure blob storage using azure logic app Standard

Abhishake Jaiswal 160

we have a logic app WF that gets triggered when email arrives in a mailbox. It gets the attachment in email and uploads to Azure blob storage.
Now we need to unzip files that come with .zip extensions.
we are facing issue in trying to unzip truly flat zip files - that do not have a parent folder.

we tried using 3 connectors
Extract an archive from a blob path to a folder
Extract archive from content to a folder
Extract an archive from a blob path to a folder based on a URI

but all are failing in flat files case with below error.

{

"code": "ServiceProviderActionFailed",

"message": "The service provider action failed with error code 'BadRequest' and error message 'The specified blob does not exist.\nRequestId:bfexxxxx-a01e-zzzz-yyyy-ffffff00000\nTime:2025-10-31T05:25:40.7756972Z\r\nStatus: 404 (The specified blob does not exist.)\r\nErrorCode: BlobNotFound\r\n\r\nContent:\r\n<?xml version="1.0" encoding="utf-8"?><Error><Code>BlobNotFound</Code><Message>The specified blob does not exist.\nRequestId:bfexxxxx-a01e-zzzz-yyyy-ffffff00000nTime:2025-10-31T05:25:40.7756972Z</Message></Error>\r\n\r\nHeaders:\r\nServer: Windows-Azure-Blob/1.0 Microsoft-HTTPAPI/2.0\r\nx-ms-request-id: bfexxxxx-a01e-zzzz-yyyy-ffffff00000\r\nx-ms-client-request-id: qwerty-d3c7-4d9e-be40-asdfghjklpoi\r\nx-ms-version: 2024-08-04\r\nx-ms-error-code: BlobNotFound\r\nDate: Fri, 31 Oct 2025 05:25:40 GMT\r\nContent-Length: 215\r\nContent-Type: application/xml\r\n'."

}

Is this a known limitation ?do we have a workaround for this ?
we do not have issues with .zip email attachments that have a inbuild folder structure.

Abhishake Jaiswal 160 Reputation points

2025-11-02T09:44:19.2466667+00:00

hi Pravallika ,

we are connecting via Managed Identity which has RBAC permissions on storage account using in built serviceProviderConnection for AzureBlob.

step1 : Workflow triggers from arrival of email with attachment.

step 2 : on identifying that attachment is .zip and for specific business activity, the current Workflow is invoked via HTTP call.

step 3: Workflow uploads the zip file to a specific location in azure blob storage account.

step 4 : if its a zip file, workflow tries to unzip the file in same path under a new subfolder.

step 5: Workflow also uploads the same zip file to a fileshare

step 6 : if its a zip file, workflow tries to unzip the file in similar path under a unzipped files folder.

we are facing same error for unzipping flat files for fileshare location and azure blob storage.

I do not know of any restrictions. we are able to unzip non-flat .zip files (The ones that have folder structure) Could you advise what sort of restrictions are you referring ?

Regards

Abhishake Jaiswal
Pravallika KV 3,565 Reputation points Microsoft External Staff Moderator

2025-11-03T07:13:51.74+00:00
Hi Abhishake Jaiswal,

Thanks for the confirmation. Glad that your issue is resolved.

The specified blob does not exist

If the ZIP is flat (no folder structure), the extraction logic sometimes miscalculates the destination path and tries to write a blob to a non-existent folder path, or the connector expects a folder prefix that doesn’t exist. Hence the misleading “BlobNotFound” (404) error.

Even if Windows can open the ZIP, Logic Apps built-in connectors are stricter. Usually, the issues are compression type, central directory quirks, encoding, or metadata entries. Repackaging or using a more robust extractor (Azure Function) fixes it reliably.

Solution:

Those zip files use non-standard compression or metadata formats that Azure’s extractor doesn’t support e.g., ZIP64, Deflate64, AES-encrypted zips, bad encoding, or missing folder paths.

Re-compress the ZIP by using a standard tool (Deflate) like 7-Zip, WinRAR before sending to Logic App.
Rupesh Asati 1,020 Reputation points Microsoft External Staff Moderator

2025-11-20T16:16:45.83+00:00

Hi Abhishake Jaiswal,
Following up to see if the above provided answer was helpful. If it answers your query, please do upvote. If you have any further queries, do let us know.

Thanks

2 answers

Your answer

Abhishake Jaiswal 160 Reputation points

2025-11-02T09:44:19.2466667+00:00

hi Pravallika ,

we are connecting via Managed Identity which has RBAC permissions on storage account using in built serviceProviderConnection for AzureBlob.

step1 : Workflow triggers from arrival of email with attachment.

step 2 : on identifying that attachment is .zip and for specific business activity, the current Workflow is invoked via HTTP call.

step 3: Workflow uploads the zip file to a specific location in azure blob storage account.

step 4 : if its a zip file, workflow tries to unzip the file in same path under a new subfolder.

step 5: Workflow also uploads the same zip file to a fileshare

step 6 : if its a zip file, workflow tries to unzip the file in similar path under a unzipped files folder.

we are facing same error for unzipping flat files for fileshare location and azure blob storage.

I do not know of any restrictions. we are able to unzip non-flat .zip files (The ones that have folder structure) Could you advise what sort of restrictions are you referring ?

Regards

Abhishake Jaiswal
Pravallika KV 3,565 Reputation points Microsoft External Staff Moderator

2025-11-03T07:13:51.74+00:00

Hi Abhishake Jaiswal,

Thanks for the confirmation. Glad that your issue is resolved.

The specified blob does not exist

If the ZIP is flat (no folder structure), the extraction logic sometimes miscalculates the destination path and tries to write a blob to a non-existent folder path, or the connector expects a folder prefix that doesn’t exist. Hence the misleading “BlobNotFound” (404) error.

Even if Windows can open the ZIP, Logic Apps built-in connectors are stricter. Usually, the issues are compression type, central directory quirks, encoding, or metadata entries. Repackaging or using a more robust extractor (Azure Function) fixes it reliably.

Solution:

Those zip files use non-standard compression or metadata formats that Azure’s extractor doesn’t support e.g., ZIP64, Deflate64, AES-encrypted zips, bad encoding, or missing folder paths.

Re-compress the ZIP by using a standard tool (Deflate) like 7-Zip, WinRAR before sending to Logic App.
Rupesh Asati 1,020 Reputation points Microsoft External Staff Moderator

2025-11-20T16:16:45.83+00:00

Hi Abhishake Jaiswal,
Following up to see if the above provided answer was helpful. If it answers your query, please do upvote. If you have any further queries, do let us know.

Thanks

Answer 1

Hi Abhishake Jaiswal,

Thanks for the confirmation. Glad that your issue is resolved.

The specified blob does not exist

If the ZIP is flat (no folder structure), the extraction logic sometimes miscalculates the destination path and tries to write a blob to a non-existent folder path, or the connector expects a folder prefix that doesn’t exist. Hence the misleading “BlobNotFound” (404) error.

Even if Windows can open the ZIP, Logic Apps built-in connectors are stricter. Usually, the issues are compression type, central directory quirks, encoding, or metadata entries. Repackaging or using a more robust extractor (Azure Function) fixes it reliably.

Solution:

Those zip files use non-standard compression or metadata formats that Azure’s extractor doesn’t support e.g., ZIP64, Deflate64, AES-encrypted zips, bad encoding, or missing folder paths.

Re-compress the ZIP by using a standard tool (Deflate) like 7-Zip, WinRAR before sending to Logic App.

Hope it helps!

Please do not forget to click "Accept the answer” and Yes, this can be beneficial to other community members.

User's image

If you have any other questions, let me know in the "comments" and I would be happy to help you.

Answer 2

this worked for uploading to blob storage by changing connector
existing connectors :

upload zip to blob storage
Connector : Azure Blob Storage
Operation note: Upload a blob to an Azure storage container.
Connector type : In-app
Extract zip file
Connector : Azure Blob Storage
Operation note : Extract an archive from a blob path to a folder.
Connector type: In-app

new connector used

Create blob (v2)
Extract Archive to folder (V2)

Though we noted that the folder extraction works fine for blob storage,
if we try unzip of same zip file on file share, the file share connector was not working.
Connector : Azure File Storage
Operation note : Extract an archive file inside the specified folder. Only ZIP archives are supported.
Connector type : In-app

error message received :
"code": "ServiceProviderActionFailed",

"message": "The service provider action failed with error code 'BadRequest' and error message 'Service request failed.\r\nStatus: 400 (The specifed resource name contains invalid characters.)\

I individually checked each file name, and they are all valid.
What surprises me that azure blob storage allows this action, but file share does not for same zip file.
could you help to advise why we have this different behaviour?

Share via

decompress a True Flat .zip file (no parent folder) in azure blob storage using azure logic app Standard

2 answers

Your answer