404 The specified queue does not exist - for blob trigger Azure Function

Question

I'm making a simple Azure Function that works on a blob trigger.

I decided to deploy it using the CLI. I can see the function in my Azure Functions overview tab. Let me give a little bit of a context here: My blob storage is on a storage account called A where I have a container called storage. When I created my Azure Function, a new storage account & resource group were created because for some reason I wasn't able to deploy linux workers on my existing ones. So now I basically have one storage account for my Azure Functions and a storage account with a container where I upload power point files.

After deploying it, the function doesn't seem to work at all. In my Log stream I see an error that says

2025-05-06T13:23:19Z [Warning] Error response [xxx] 404 The specified queue does not exist. (00.0s)

This is weird to me because I use blob trigger and I don't know why does it expect a queue? I tried almost anything from the Internet to solve this but my knowledge is limited as I've started using the Azure Functions more active recently. I have set my BlobStorageConnectionString to my storage account key where I upload my files. AzureWebJobsStorage points out to the storage account that was made during the creation of the Azure Function, which I assume is okay?

So, is there a way to fix this error? If anyone has ever stumbled upon an issue like this, can you share more info about how can I resolve this problem and move forward?

Change AzureWebJobsStorage to point to the storage account that contains the pptx-storage container (Storage Account A). — Dasari Kamali
– Dasari Kamali, Commented May 6 at 14:27
Changed, now I get [Warning] Error response [xxx] 403 This request is not authorized to perform this operation. (00.0s). Should I give some access to my Azure Function so it's able to connect with the Storage account? — anthino12
– anthino12, Commented May 6 at 14:36
Make sure the AzureWebJobsStorage connection string is correct and uses access keys. — Dasari Kamali
– Dasari Kamali, Commented May 6 at 15:07
Can you check the Storage Account's Networking settings? Make sure Public access from all networks is enabled so the Function can connect. — Dasari Kamali
– Dasari Kamali, Commented May 7 at 10:09
Yeah, it seems to work now. It was protected by some private endpoints, Public access made it work. Thanks — anthino12
– anthino12, Commented May 8 at 8:46

Dasari Kamali · Accepted Answer · 2025-05-08 09:15:03Z

1

403 This request is not authorized to perform this operation.

The issue you are encountering is due to the storage account that contains the pptx-storage container was protected by some private endpoints, which blocked the Azure Function from accessing it.

To resolve the issue,

Go to the Azure Storage account where your blob container (pptx-storage) is located.
Then, navigate to the Networking > Public network access section, select the option Enabled from all networks as shown below.

answered May 8 at 9:15

Dasari Kamali

4,3732 gold badges5 silver badges13 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

404 The specified queue does not exist - for blob trigger Azure Function

1 Answer 1

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Related