After Creating Trigger on Azure Storage Event - It Fails to trigger Pipeline

[mukul008]

I want Folder Name  which is newly created in my Azure blob storage account

I tried the Trigger (Preview) in fabric pipeline and I was able to successfully create the Alert (which connects to my Azure blob storage account). An activator and event stream was also automatically created too.

I have a Set Variable activity in the pipeline. It is supposed to get me folder name so that I can use that folder name and later use it to load different files present in it to load in my KQL DB.

However, even after successful creating the trigger event for this pipeline, when I Create new folder in  the azure blob storage account, it does not trigger the Microsoft fabric pipeline to run.

I am also not sure what to put in Subject Property and what operator should we use, when we configure trigger.

I tried different versions but still no success in trigeering pipeline.

For ex.

• /blobServices/default/containers/test-upload-container/blobs/{new-folder}/*
• /blobServices/default/containers/test-upload-container/blobs/{new-folder}/

What am I missing ? Please help

i am refrencing this doc to create it - Data pipelines storage event triggers in Data Factory (Preview) - Microsoft Fabric | Microsoft Learn

[Anonymous · Accepted solution]

Hi @mukul008 

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.

[mukul008]

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-menakakota]

Hi @mukul008 ,

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 @mukul008 ,

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 @mukul008   ,

I would also take a moment to thank @Anonymous  , for actively participating in the community forum and for the solutions you’ve been sharing in the community forum. Your contributions make a real difference. 

I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions. If the  response has addressed your query, please accept it as a solution so that other community members can find it easily. 

 
Thank you.