how to trigger the activator when file created in a specific container in azure blob

[Gowthamdas]

how to trigger the activator when file created in a specific container and with specific folder in azure blob storage?

Filter conditions is not works as we expect, it still triggers when file uploaded in other containers with the same storage account,
but my requirement is to trigger with my specified container and specific folder and also not recursively!!!

[Gowthamdas]

Screen shot that i have created with only blob created

i dropped the file into archive folder, but as per our filter rule it should not run unfortunately it rann..
output i got from Activator subject: /blobServices/default/containers/fabric-activator-test/blobs/archive/xyz.parquet

And it is also get triggered if i drop a file from another container and the path is : /blobServices/default/containers/test-gm-dev/blobs/xyzfile.parquet


I really surpraised with this filter, hy why you are not filtering...

[v-saisrao-msft]

Hi @Gowthamdas,

Thank you for reaching out to the Microsoft Fabric Forum Community.

If you want to trigger Data Activator only when a file is uploaded directly to the root of a specific container, and not from subfolders or other containers, your current filter setup is almost correct. The main issue is that Azure Event Grid filters like StringBeginsWith or StringNotContains only do basic substring checks, not actual path or folder-based filtering. This is why uploads from subfolders or different containers are still triggering events.

To make the triggers more precise, try these settings:

• subject begins with: /blobServices/default/containers/fabric-activator-test/blobs/
• subject does not contain: /blobs/archive/ or any other subfolder names you want to exclude

Since Event Grid can't dynamically exclude all folders, the most effective approach is to add filtering logic within the Data Activator rule or use an Eventstream transformation. You can extract the subject field and set up logic to include only events from the root of your container and exclude specific folder paths as needed.

Below is the link for your reference:

Add Azure Blob Storage event source to an eventstream - Microsoft Fabric | Microsoft Learn

Hope this helps.

Thank You.

[Gowthamdas]

Also tried with yours technique, still triggers for every thing inside the 'act' sub folder and also trigger with other container☹️
can some one try realtime test and let me know if all goes well...

[Gowthamdas]

@burakkaragoz I appreciate your immediate response,

But i also tried using this, still if i drop file in another container it will begin to run

For Advanced filters, use:

• Key: subject
• Operator: String begins with
• Value: /blobServices/default/containers/YOUR_CONTAINER_NAME/blobs/YOUR_FOLDER_NAME/
  
  
  
  Let me try one more time!!!

[Gowthamdas]

Exact use case: Like i want to drop file inside the container, not with specific folder

[burakkaragoz]

Hi @Gowthamdas ,

Ah, I see the issue now! You want to trigger only when files are dropped directly in the container root, not in any specific folder.

Try this exact filter:

Key: subject Operator: String begins with
Value: /blobServices/default/containers/YOUR_CONTAINER_NAME/blobs/

AND add a second filter to exclude subfolders:

Key: subject Operator: String does not contain Value: /blobs/*/

This way it will trigger for files like:

• /blobServices/default/containers/mycontainer/blobs/myfile.txt 
• /blobServices/default/containers/mycontainer/blobs/document.pdf 

But NOT for:

• /blobServices/default/containers/mycontainer/blobs/folder1/file.txt 
• /blobServices/default/containers/othercontainer/blobs/file.txt 

Alternative approach - use exact path matching: Instead of "String begins with", try "String matches pattern" with: /blobServices/default/containers/YOUR_CONTAINER_NAME/blobs/[!\/]*

This pattern excludes any files that have additional forward slashes (subfolders).

The key is making sure you're filtering out both other containers AND subfolders within your target container. Try the dual filter approach first - it's usually more reliable.

[burakkaragoz]

Hi @Gowthamdas ,

Looking at your screenshot, the issue is with your Advanced filters configuration. The current filter pattern you're using isn't specific enough and may be causing triggers from other containers.

Here's the correct filter pattern for your specific container and folder:

For Advanced filters, use:

• Key: subject
• Operator: String begins with
• Value: /blobServices/default/containers/YOUR_CONTAINER_NAME/blobs/YOUR_FOLDER_NAME/

Example based on your screenshot:

/blobServices/default/containers/fabric-activator-test/blobs/your-specific-folder/

Important notes:

1. Remove the wildcard (/*) - This makes it recursive and triggers for all subfolders
2. Use exact path matching - Don't use pattern matching like {*/}-*
3. End with forward slash if you want folder-level filtering

Alternative approach using multiple filters: If you need more control, add multiple string filters:

• Filter 1: subject String begins with /blobServices/default/containers/fabric-activator-test/
• Filter 2: subject String contains /blobs/your-folder-name/
• Filter 3: subject String does not contain /blobs/your-folder-name/subfolder/ (to avoid recursion)

Double-check these settings:

• Make sure you're selecting the correct Azure Blob Storage account
• Verify the container name matches exactly (case-sensitive)
• Test with a simple file upload to confirm the trigger works as expected

The key is being very specific with the path structure rather than using wildcards that can match unintended locations.

---

If my response resolved your query, kindly mark it as the Accepted Solution to assist others. Additionally, I would be grateful for a 'Kudos' if you found my response helpful.
This response was assisted by AI for translation and formatting purposes.