Hello colleague @Karn Dalmia
It seems that there might be a few issues with your configuration. Here are some suggestions that might help:
- Blob container location: The blob container is located in your Azure Storage account, not on your local machine or Storage Explorer. You can find the name of the container in the
[BlobTrigger(samples-workitems/{name}, Connection = AzureWebJobsStorage)]
attribute in your code. In this case, the container name issamples-workitems
. - Connection string: In your
local.settings.json
file, you are using theUseDevelopmentStorage=true
connection string, which is used to connect to the local Azure Storage emulator. However, it seems that you are trying to trigger the function using a blob in your actual Azure Storage account. To connect to your Azure Storage account, you need to use the connection string for your account. You can find this connection string in the Azure portal under your storage account's "Access keys" section. - Function name: In your
PBIZeroTouchBlob.cs
file, you have named your functionPBIZeroTouchBlob
, but in the[Function(nameof(PBIZeroTouch))]
attribute, you have named itPBIZeroTouch
. Make sure that the function name in the attribute matches the actual function name. - Blob path: In the
[BlobTrigger(samples-workitems/{name}, Connection = AzureWebJobsStorage)]
attribute, you are usingsamples-workitems/{name}
as the blob path. This means that the function will only trigger when a blob is added or modified in thesamples-workitems
container with a name that matches the{name}
parameter. Make sure that the blob path matches the actual path of the blob that you are trying to trigger the function with. - Function trigger: Make sure that your function is actually being triggered by adding or modifying a blob in the specified container. You can check the logs of your function in the Azure portal to see if it is being triggered and if there are any errors. I hope this helps! Let me know if you have any further questions.
I hope this helps.