Forum Discussion
Post PatronStorage trigger event
Dears,
I have a folder in a lakehouse which users use to add some excel files on a daily basis
So far, after adding the files, the users are then triggering manually a fabric data factory pipeline which transforms the excel files into tables in the lakehouse
I would like that the users do not have to manually run the pipeline, but instead, this would be triggered by a storage event trigger from the fabric data factory pipeline
But some of my team members state that this can become expensive as the trigger will have to keep watching the folder and hence it may cost a lot of money
My undertsanding is a bit diffferent
Seems to me that its the onelake that will generate an event (created event) which then calls an event grid that will call the pipeline to run it automatically
This is the definition I saw in AI :
Q1 : Is my undertanding correct? and is this doable for fabric data factory pipelines?
Q2 : This trigger type (storage) is in public preview or in GA?
Q3 : Can we expect this to be expensive because it will keep watching the folder, or as I expect , its onelake itself that will generate an event and only on file creation? not keeping watching
Thank you so much,
Pedro
Hey fabricpribeiro,
Your are already aware of the topic pretty well. But just so it helps others, I will try to answer your questions directly.
Q1 - Is your undertanding correct? and is this doable for fabric data factory pipelines?
Yes. OneLake events are notifications triggered by changes within the data lake (creation/modification/deletion of files and folders). There is no constant watching happening. OneLake itself fires the event, and the pipeline only wakes up when that event arrives.
The exact flow under the hood is: OneLake --> emits event --> Activator receives it --> triggers the pipeline.
Q2 - This trigger type (storage) is in public preview or in GA?
GA. Azure and Fabric Events (which includes OneLake events) are Generally Available. This was announced in April 2025.
Q3 - Will it be expensive because it keeps watching?
No cost for watching. The architecture is push-based, not polling. So you only pay for pipeline runs when a file actually lands, not for idle watching time. Your teammates' concern doesn't apply here.
And I think, by now, you would have convinced your team😉
Hi fabricpribeiro,
Based on our understanding, there is no charge for monitoring a folder, as processing occurs only when an event is triggered. Given your workload, approximately 60 small files per month on F16, the impact is negligible.
Additionally, you do not need to create or manage any Eventhouse. Microsoft Fabric automatically provisions the required event infrastructure in a fully managed, serverless manner, without idle compute costs.
Additionally, kindly refer to the links below:
Fabric OneLake Events in Fabric Real-Time Hub - Microsoft Fabric | Microsoft Learn
Activator capacity consumption, usage reporting, and billing - Microsoft Fabric | Microsoft LearnWe hope the above information resolves the issue. Should you have any further queries, please feel free to contact the Microsoft Fabric community.
Thank you.
12 Replies
- lbendlin
Super User
Reflexes/Eventhouses are very expensive, and not overly reliable.
Instead, consider running a schedule that only processes files that were added since the last scheduled run.
Or place your Excel files on a SharePoint and use Power Automate to process them.
fabricpribeiroThanks for your reply
This expects to work on 3 projects. Each project adds 20 files por month, each file with 2K rows, not more then that
Do you still consider it expensive which such a low number of rows? or you think its ok?
My capacity is F16
- lbendlin
The triggers aren't expensive. Keeping the Eventhouse running is.
- stoic-harsh
Hey fabricpribeiro,
Your are already aware of the topic pretty well. But just so it helps others, I will try to answer your questions directly.
Q1 - Is your undertanding correct? and is this doable for fabric data factory pipelines?
Yes. OneLake events are notifications triggered by changes within the data lake (creation/modification/deletion of files and folders). There is no constant watching happening. OneLake itself fires the event, and the pipeline only wakes up when that event arrives.
The exact flow under the hood is: OneLake --> emits event --> Activator receives it --> triggers the pipeline.
Q2 - This trigger type (storage) is in public preview or in GA?
GA. Azure and Fabric Events (which includes OneLake events) are Generally Available. This was announced in April 2025.
Q3 - Will it be expensive because it keeps watching?
No cost for watching. The architecture is push-based, not polling. So you only pay for pipeline runs when a file actually lands, not for idle watching time. Your teammates' concern doesn't apply here.
And I think, by now, you would have convinced your team😉
- v-pnaroju-msft
Community Support
Thankyou, lbendlin and stoic-harsh for your responses.
Hi fabricpribeiro,
We appreciate your inquiry through the Microsoft Fabric Community Forum.
We would like to inquire whether have you got the chance to check the solutions provided by lbendlin and stoic-harsh to resolve the issue. We hope the information provided helps to clear the query. Should you have any further queries, kindly feel free to contact the Microsoft Fabric community.
Thank you. - v-pnaroju-msft
Hi fabricpribeiro,
We are following up to see if what we shared solved your issue. If you need more support, please reach out to the Microsoft Fabric community.
Thank you. - v-pnaroju-msft
Hi fabricpribeiro,
We are checking in to see whether the information we shared resolved your issue. If you still need help, please reach out to the Microsoft Fabric community.
Thank you.
- v-pnaroju-msft
Hi fabricpribeiro,
Based on our understanding, there is no charge for monitoring a folder, as processing occurs only when an event is triggered. Given your workload, approximately 60 small files per month on F16, the impact is negligible.
Additionally, you do not need to create or manage any Eventhouse. Microsoft Fabric automatically provisions the required event infrastructure in a fully managed, serverless manner, without idle compute costs.
Additionally, kindly refer to the links below:
Fabric OneLake Events in Fabric Real-Time Hub - Microsoft Fabric | Microsoft Learn
Activator capacity consumption, usage reporting, and billing - Microsoft Fabric | Microsoft LearnWe hope the above information resolves the issue. Should you have any further queries, please feel free to contact the Microsoft Fabric community.
Thank you.
- v-pnaroju-msft
Hi fabricpribeiro,
We are checking in to confirm whether the solution we provided resolved your issue. If you still need help, please reach out to the Microsoft Fabric community.
Thank you.
