Azure Blob Storage event to trigger pipeline not working .

Question

Azure Blob Storage event to trigger pipeline not working .

JS 0

folks ..

I have a created a Blob storage event as per the docs here , tied it to pipeline and event is started . however when a file is uploaded nothing happens . I read thru similar posts but still cant find the missing info to get this working .

1.png

2.png

I also see the file in preview section ...

3.png

read thru some of the posts here which says i need an event subscription but not always .. I checked

by going to go storage account > event subscription i see nothing here...

thoughts /advice be very appreciated . Thanks in advance.

JS 0 Reputation points

2025-05-12T19:48:41.9433333+00:00

ignore the // i did a typo while changing the actual name ...

I have container name as XYZ

blob path begin with XYX/

and if you see the attachment 3 i could see the file under that folder in preview mode.

++ I dont see anything getting created in Event Subscription.
JS 0 Reputation points

2025-05-13T15:45:37.4466667+00:00

HI,

I recreated a trigger event again and still not seeing this registered in event subscription .
Ganesh Gurram 7,295 Reputation points Microsoft External Staff Moderator

2025-05-13T16:22:12.4233333+00:00
@JS - Thanks for the update!

If the trigger was published but the subscription creation silently failed, you can find it in the activity log.

Go to your Storage Account > Monitoring > Activity Log

Filter by eventSubscriptions/write

Look for any Failed entries around the time you clicked Publish All in Synapse.

This can help identify permission issues or misconfiguration errors.

Please check that the Storage Account and the Synapse workspace are in the same region (e.g., both in East US).
JS 0 Reputation points

2025-05-13T16:38:45.8533333+00:00
Ganesh,

Go to your Storage Account > Monitoring > Activity Log

I am not seeing the activity log

5.JPG

I can confirm Storage Account and the Synapse workspace are in same region.
Ganesh Gurram 7,295 Reputation points Microsoft External Staff Moderator

2025-05-13T19:16:28.5233333+00:00

@JS

Please check the below image for detailed errors:

I hope this information helps.
Ganesh Gurram 7,295 Reputation points Microsoft External Staff Moderator

2025-05-14T18:54:54.4133333+00:00

@JS

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.

1 answer

Your answer

JS 0 Reputation points

2025-05-12T19:48:41.9433333+00:00

ignore the // i did a typo while changing the actual name ...

I have container name as XYZ

blob path begin with XYX/

and if you see the attachment 3 i could see the file under that folder in preview mode.

++ I dont see anything getting created in Event Subscription.
JS 0 Reputation points

2025-05-13T15:45:37.4466667+00:00

HI,

I recreated a trigger event again and still not seeing this registered in event subscription .
Ganesh Gurram 7,295 Reputation points Microsoft External Staff Moderator

2025-05-13T16:22:12.4233333+00:00

@JS - Thanks for the update!

If the trigger was published but the subscription creation silently failed, you can find it in the activity log.

Go to your Storage Account > Monitoring > Activity Log

Filter by eventSubscriptions/write

Look for any Failed entries around the time you clicked Publish All in Synapse.

This can help identify permission issues or misconfiguration errors.

Please check that the Storage Account and the Synapse workspace are in the same region (e.g., both in East US).
JS 0 Reputation points

2025-05-13T16:38:45.8533333+00:00

Ganesh,

Go to your Storage Account > Monitoring > Activity Log

I am not seeing the activity log

5.JPG

I can confirm Storage Account and the Synapse workspace are in same region.
Ganesh Gurram 7,295 Reputation points Microsoft External Staff Moderator

2025-05-13T19:16:28.5233333+00:00

@JS

Please check the below image for detailed errors:

I hope this information helps.
Ganesh Gurram 7,295 Reputation points Microsoft External Staff Moderator

2025-05-14T18:54:54.4133333+00:00

@JS

We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.

Answer 1

@JS

Based on the review and configuration you've shared, it appears the root cause is an incorrect container name format in your event trigger configuration. Please ensure the following points are addressed:

Correct Container Name Format - In the trigger configuration, the container name should be set as test
Incorrect - //test/
Correct - test

Incorrect formatting can prevent the necessary Event Grid subscription from being created, which is required to trigger your pipeline.

Ensure Event Subscription Exists - Go to your Storage Account > Events > Event Subscriptions. If you do not see a subscription created for your Synapse pipeline, this confirms the trigger didn't register correctly. After correcting the container name, publish the trigger again to auto-create the subscription.

Trigger Configuration in Synapse Studio - Ensure the trigger is Started and Published. Make sure the "Blob path begins with" is set correctly (e.g., test/). Check that the correct event type ("Blob Created") is selected.

Permissions - Ensure that the Synapse Managed Identity has Storage Blob Data Reader permission on the Storage Account.

Try Recreating the Trigger - If issues persist, delete and re-create the trigger with the correct settings. Re-publish and confirm the Event Subscription is created.

For more details refer:

I hope this information helps.

Kindly consider upvoting the comment if the information provided is helpful. This can assist other community members in resolving similar issues.

Share via

Azure Blob Storage event to trigger pipeline not working .

1 answer

Your answer