Update functions-bindings-storage-blob-trigger.md
Hello,
I see some Blob trigger functions occur errors as it cannot access a queue storage. To avoid this issue, proposing an additional note to allow the access.
@yuna-s : Thanks for your contribution! The author(s) have been notified to review your proposed change.
Learn Build status updates of commit db86f4e:
:white_check_mark: Validation status: passed
| File | Status | Preview URL | Details |
|---|---|---|---|
| articles/azure-functions/functions-bindings-storage-blob-trigger.md | :white_check_mark:Succeeded |
For more details, please refer to the build report.
For any questions, please:
- Try searching the learn.microsoft.com contributor guides
- Post your question in the Learn support channel
@ggailey777
Can you review the proposed changes?
When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged" @MicrosoftDocs/public-repo-pr-review-team
@ggailey777
Can you review the proposed changes?
IMPORTANT: When the changes are ready for publication, add a #sign-off comment to signal that the PR is ready for the review team to merge.
@MicrosoftDocs/public-repo-pr-review-team
emailed author
@yuna-s how did you get into the situation where your function app didn't have access to Queue Storage in the storage account you are using for AzureWebJobsStorage? I'm disinclined to accept your suggestion because I don't think this situation is very likely to occur.
I will go ahead and update this article to include blob trigger as something that required the queue storage.
Please let me know if I am misunderstanding your scenario.
hi @ggailey777 Thank you for your checking! Your suggestions is nice. Some customer enables Firewall on Azure Storage and it blocks requests to queue storage. Using Firewall on the Storage is not unusual sinario. I think it would be more kindly that making it clear to customers that Blob trigger also needs access to Queue storage.
Thanks @yuna-s this is very good information! I'll keep it in mind as I work on our troubleshooting documentation.