This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I created a storage event trigger in Azure Synapse Analytics. In the "Data preview" pane, I am able to see that Azure detects files which match the trigger criteria. However, when I publish the trigger and upload a matching file, the trigger does not fire. I have check that the event subscription has been created and is configured correctly. Our team also uses this event type for other triggers. I have tried expanding the path all the way to the container level, but Azure still does not detect the blob creation event.
Thanks for posting your question in the Microsoft Q&A forum.
Azure Synapse Analytics storage event triggers may fail to fire despite correct configuration due to permissions, network settings, or event filtering issues.
Monitor > Triggers). Inactive triggers won’t fire.Events > Event Subscriptions and verify no delivery failuresPlease don't forget to close up the thread here by upvoting and accept it as an answer if it is helpful
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(99.2, 65%, 19%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ECB%3C/text%3E%3C/svg%3E)
It sounds like you’ve configured everything correctly on the Synapse and storage side, but the pipeline still isn’t being triggered when uploading a matching file via a blob client. One possible cause here is how Azure Event Grid integrates with Blob Storage events, especially when using SDKs or custom clients.
Here’s what might be happening:
When you upload a file using a Blob Storage client (such as the Azure SDK or Java-based clients), the upload process might not trigger a BlobCreated event automatically — especially if the upload is done in blocks or if certain headers are missing. Since Synapse event triggers rely on these events via Event Grid, the trigger won't fire if the event is never published.
Recommended workaround:
After uploading the file, you can use the beginCopyFromURL() method from the Azure Blob SDK to copy the file to itself. This copy operation will generate a BlobCreated event, which can successfully fire the trigger. Here's a code snippet in JavaScript as an example:
const { BlobServiceClient } = require("@azure/storage-blob");
const blobServiceClient = BlobServiceClient.fromConnectionString(connectionString);
const containerClient = blobServiceClient.getContainerClient(containerName);
const blobClient = containerClient.getBlobClient(blobName);
const sourceURL = blobClient.url;
await blobClient.beginCopyFromURL(sourceURL);
This operation essentially re-creates the blob, causing Event Grid to recognize it as a new creation and invoke the trigger as expected.
For additional information, please refer to the similar thread on MS Q&A platform:
https://learn.microsoft.com/en-us/answers/questions/1343530/storage-event-trigger-will-not-start-azure-synapse
I hope this information helps. Please do let us know if you have any further queries.
Kindly consider upvoting the comment if the information provided is helpful. This can assist other community members in resolving similar issues.
Thank you.
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.
Just checking in to see if the below suggestion helped. If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know. As your feedback is valuable and can assist others in the community facing similar issues.
Hi everyone! I appreciate the responses. I am not sure what fixed the issue, but after reverting to an old trigger configuration (that was not working at the time it was configured), the trigger started to work.
I'm glad that you were able to resolve your issue and thank you for posting your solution so that others experiencing the same thing can easily reference this! Since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others ", I'll repost your solution in case you'd like to accept the answer.
I'm glad that you were able to resolve your issue and thank you for posting your solution so that others experiencing the same thing can easily reference this! Since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others ", I'll repost your solution in case you'd like to accept the answer.
Issue:
Azure Synapse Pipeline Trigger Won't Fire
Solution:
"I'm not certain what resolved the issue, but after reverting to an old trigger configuration (which was not working when initially set up), the trigger began to work."
If I missed anything please let me know and I'd be happy to add it to my answer, or feel free to comment below with any additional information.
Hope this helps. Do let us know if you have any further queries.
If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.
Following up to see if the above suggestion was helpful. If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.