Forum Discussion
After Creating Trigger on Azure Storage Event - It Fails to trigger Pipeline
Hi Anonymous
It sounds like you've set up most of the components correctly, but there might be a few details to check to ensure your trigger works as expected.
Subject Property: This field should match the path of the folder or file you want to monitor. For a newly created folder, you can use a wildcard to capture any new folder creation. For example:
/blobServices/default/containers/test-upload-container/blobs/{new-folder}/*
/blobServices/default/containers/test-upload-container/blobs/{new-folder}/
Ensure that {new-folder} is replaced with the actual folder name or a wildcard if you want to capture any new folder creation.Operator: The operator should be set to StartsWith to capture any event that starts with the specified path. This is useful for capturing new folder creation events.
Event Type: Make sure you are selecting the correct event type, such as Microsoft.Storage.BlobCreated, to trigger the pipeline when a new folder or blob is created.
Permissions: Verify that the Azure Blob Storage account and the Fabric pipeline have the necessary permissions to access and trigger events.
Preview Limitations: Since the storage event triggers are in preview, there might be some limitations or bugs. Ensure you are following the latest documentation and updates from Microsoft.
Regards,
Nono Chen
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hi Anonymous
It sounds like you've set up most of the components correctly, but there might be a few details to check to ensure your trigger works as expected.
Subject Property: This field should match the path of the folder or file you want to monitor. For a newly created folder, you can use a wildcard to capture any new folder creation. For example:
/blobServices/default/containers/test-upload-container/blobs/{new-folder}/*
/blobServices/default/containers/test-upload-container/blobs/{new-folder}/
Ensure that {new-folder} is replaced with the actual folder name or a wildcard if you want to capture any new folder creation.
Operator: The operator should be set to StartsWith to capture any event that starts with the specified path. This is useful for capturing new folder creation events.
Event Type: Make sure you are selecting the correct event type, such as Microsoft.Storage.BlobCreated, to trigger the pipeline when a new folder or blob is created.
Permissions: Verify that the Azure Blob Storage account and the Fabric pipeline have the necessary permissions to access and trigger events.
Preview Limitations: Since the storage event triggers are in preview, there might be some limitations or bugs. Ensure you are following the latest documentation and updates from Microsoft.
Regards,
Nono Chen
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hi Anonymous Thanks for the reply
i will try mentioned points but can you please elaborate about the below point..
Permissions: Verify that the Azure Blob Storage account and the Fabric pipeline have the necessary permissions to access and trigger events.
FYI - i have Storage Blob Data Contributor access for Storage account
any other access we require?or what type of access we needed?
once again Thank you!!
v-menakakotaCommunity Support
Hi Anonymous ,
May I ask if you have resolved this issue? If so, please mark the helpful reply and accept it as the solution. This will be helpful for other community members who have similar problems to solve it faster.
Thank you.
- v-menakakota
Hi Anonymous ,
May I ask if you have resolved this issue? If so, please mark the helpful reply and accept it as the solution. This will be helpful for other community members who have similar problems to solve it faster.
Thank you.