Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!View all the Fabric Data Days sessions on demand. View schedule
Hi everyone,
I wanted to share a useful approach I’ve been using in Microsoft Fabric to detect which user has manually triggered a pipeline or notebook, as this can be very helpful for logging, auditing, and security purposes — especially when combined with a System Run Report or other operational dashboards.
While Fabric now correctly returns @pipeline().TriggerType = "1" when a pipeline is triggered by a schedule, manual runs still require additional logic if you want to capture who initiated them.
For example, when I run a pipeline or notebook manually, I log the triggering user using the following discovery logic.
Below is a Python snippet you can run inside a Fabric Notebook to detect who triggered the run:
This code safely checks:
The job instance metadata
The Fabric runtime context
And as a fallback, Microsoft Graph /me
It returns the display name or UPN of the user who manually triggered the run.
This logic helps ensure your logs clearly differentiate between manual, scheduled, and orchestrated pipeline runs — with proper user tracking for manual triggers.
By logging this user information into your System Run Report or operational tables, you can generate insights like:
Who manually executed pipelines or notebooks
When and how often manual interventions occurred
Scheduled vs manual run ratios
Security auditing for sensitive pipelines
Recently, I noticed that Fabric has fixed the previous bug — now, when triggered by a schedule, the value of @pipeline().TriggerType correctly returns "1" 🎉.
So with this fix and the manual user detection logic above, we can now fully distinguish all run types dynamically at runtime.
Hope this helps others who want more robust runtime tracking and reporting in Fabric!
Cheers,
Hi @Yazdan,
Thanks for sharing your insights on detecting which user manually triggered a pipeline. Definitely consider turning this into a blog post so others can benefit from your experience more easily
Power BI Community Blog - Microsoft Fabric Community
We also appreciate you sharing this with the community
Thank you.
Check out the November 2025 Fabric update to learn about new features.
Advance your Data & AI career with 50 days of live learning, contests, hands-on challenges, study groups & certifications and more!