# Can't access files in azure blob storage for pipeline inputs

**URL:** https://community.seqera.io/t/cant-access-files-in-azure-blob-storage-for-pipeline-inputs/1424
**Category:** Ask for help
**Tags:** platform, azure-batch, azure
**Created:** [November 15, 2024, 8:09am UTC](https://community.seqera.io/t/cant-access-files-in-azure-blob-storage-for-pipeline-inputs/1424 "2024-11-15T08:09:07Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![eparisis](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/eparisis/32/1240_2.png) [@eparisis](https://community.seqera.io/u/eparisis)
#### Post date: [November 15, 2024, 8:09am UTC](https://community.seqera.io/t/cant-access-files-in-azure-blob-storage-for-pipeline-inputs/1424/1 "2024-11-15T08:09:07Z")

</div>

Hi everyone. I tried to load my pipeline in seqera platform but I cant get the workflow to run because the input files for my pipeline wont get read correctly from my blob storage.

Every time the pipeline starts it throws the error line `ERROR ~ Status code 400, InvalidResourceName`. I managed to replicate the issue for the azure batch executor too when trying to import files from azure blob too. When I reference my database file for example with `--database az://storagename.my-data/database` I get this error again on the line where my script will perform an action on that file like `def database_size = database.size()`.

My credentials and settings to my compute environment look fine. When running with local files on azure batch everything runs smoothly.

At this point I cant launch my pipelines on platform and have not been able for about 2 weeks. I posted this issue on slack too but havent found a solution until now.