Definitely worth mentioning that trigger names cannot include underscores

[jpborsi]

Hugely frustrating time sink that could have been neatly solved by mentioning this particular quirk in the documentation somewhere. (if it's already mentioned somewhere and I missed it, I apologize.)

For python developers, normal variable naming conventions include underscores. Not supporting that in the triggers is odd, but excusable if it's documented somewhere.

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 5ecb1e79-f603-03fd-2ef9-c6cf08ffaacd
• Version Independent ID: 35c99e36-f224-350b-a258-2e0cfb8ab154
• Content: Azure Blob storage trigger for Azure Functions
• Content Source: articles/azure-functions/functions-bindings-storage-blob-trigger.md
• Service: azure-functions
• GitHub Login: @craigshoemaker
• Microsoft Alias: cshoe

[NavtejSaini-MSFT]

@jpborsi We are checking this and we will get back to you.

[PramodValavala-MSFT]

@jpborsi Thanks for catching that! We have assigned this issue to the content author to review and update accordingly.

@craigshoemaker Here is the regex in the host runtime that seems to be used for validating the binding name.

[gsouf]

Might actually be that containers cannot contain underscore, as unusual as it can be: https://learn.microsoft.com/en-us/rest/api/storageservices/naming-and-referencing-containers--blobs--and-metadata