Storage account capping upload size of csv files to Azure blob storage

Question

We have set up an automated flow to upload csv files for our clients to our Azure blob storage. They upload using a form which triggers a flow that adds the csv file to their client folder in the blob storage.

However we have found the files are being capped at 12MB (resulting in any large files being truncated and stored in the blob storage with exactly 11.44MB).

Where might I find this "cap" and adjust it to allow larger files to be transferred fully intact?

The upload is performed via Create Blob (V2) Please see below the Create blob outputs, settings and Storage account

Answer 1

To address this issue, here are some steps and considerations:

1. Check Azure Function or App Service Limits: If you're using Azure Functions or an App Service to handle the file upload, verify if there are any set limits on the request size. Azure Functions, for example, have a maximum request size limit which might cause truncation of larger files.
2. Examine "Create Blob (V2)" Configuration: Ensure that the "Create Blob (V2)" action in your flow does not have any limitations set on the file size. This can be a configuration setting in the flow itself.
3. Review Azure Blob Storage Settings: Azure Blob Storage itself doesn't impose a 12MB cap on blob sizes. Block blobs can be up to 190.7 TiB in size. However, check if there are any configurations or policies set at the storage account level that might be causing this behavior.
4. Network Issues: Sometimes, network configurations or limitations might result in truncation of files. Ensure that there are no such restrictions in the network where the upload is being initiated.
5. Debugging the Flow: Add debugging or logging steps in your flow to capture the file size at various stages of the upload process. This can help identify at which point the truncation is happening.
6. Azure Support: If the issue persists and no clear cause is identified, consider reaching out to Azure support for a more in-depth investigation.

For a more detailed analysis, you would need to share specific details of the flow, the Azure configurations, and any relevant logs or error messages.

Given the nature of this issue, it's also advisable to check the latest Azure documentation and community discussions, as similar issues might have been encountered and resolved by others.

Accept the answer if the information helped you. This will help us and others in the community as well.