Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Get certified as a Fabric Data Engineer: Check your eligibility for a 50% exam voucher offer and join us for free live learning sessions to get prepared for Exam DP-700. Get started

Reply
arpost
Kudo Collector
Kudo Collector

Is it possible to get username of the user who triggered a pipeline run?

Greetings, community. I have a couple scenarios where I want to get the username of the person who is invoking a pipeline. I am not seeing this in any of the System Variables, but I'm hoping there's a way to do this. Use cases include:

  1. Using the triggering user's email address for email notifications.
  2. Logging who triggered the pipeline run for audit/compliance.
1 ACCEPTED SOLUTION
nilendraFabric
Solution Sage
Solution Sage

Hi @arpost 

 

Microsoft Fabric does not provide a direct way to retrieve the username of the person who triggered a pipeline run through system variables or built-in functions. However, there are a few potential workarounds you can consider:
1. Activity Logs:
While not directly accessible within the pipeline, you can check the activity logs to identify the user who triggered or reran a pipeline. This information is stored separately from the pipeline execution itself.
2. Custom Parameter:
You could add a custom parameter to your pipeline that requires the user to input their username or email address when triggering the pipeline manually. This approach would work for on-demand runs but not for scheduled runs.
3. Power Automate Integration:
If you’re triggering the pipeline through Power Automate, you might be able to pass the user’s information as a parameter to the pipeline. This method would require additional setup and would only work for flows triggered by specific users.

 

Please accept this solution if this resolved your query.

 

thanks

View solution in original post

3 REPLIES 3
nilendraFabric
Solution Sage
Solution Sage

Hi @arpost 

 

Microsoft Fabric does not provide a direct way to retrieve the username of the person who triggered a pipeline run through system variables or built-in functions. However, there are a few potential workarounds you can consider:
1. Activity Logs:
While not directly accessible within the pipeline, you can check the activity logs to identify the user who triggered or reran a pipeline. This information is stored separately from the pipeline execution itself.
2. Custom Parameter:
You could add a custom parameter to your pipeline that requires the user to input their username or email address when triggering the pipeline manually. This approach would work for on-demand runs but not for scheduled runs.
3. Power Automate Integration:
If you’re triggering the pipeline through Power Automate, you might be able to pass the user’s information as a parameter to the pipeline. This method would require additional setup and would only work for flows triggered by specific users.

 

Please accept this solution if this resolved your query.

 

thanks

@nilendraFabric and @v-kongfanf-msft, thank you for replying. I was afraid this meant there wasn't a way to get at that data. While the ideal state would be scheduled runs only, there are numerous cases where manual runs are required.

 

@nilendraFabric, I think #2 would likely be about the only way to do this to address manual runs, but the lack of a value in a scheduled run would be a problem as that raises a new question: how do you identify that it was an automated run?

 

While I know activity logs capture data like this, the need is around custom logging and alerting based on triggering user. Sounds like a feature request is in order.

v-kongfanf-msft
Community Support
Community Support

Hi @arpost ,

 

This information is not directly available in the system variables, you can check the activity logs to identify the user who triggered or reran the pipeline.


Best Regards,
Adamk Kong

 

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Helpful resources

Announcements
Feb2025 Sticker Challenge

Join our Community Sticker Challenge 2025

If you love stickers, then you will definitely want to check out our Community Sticker Challenge!

JanFabricDE_carousel

Fabric Monthly Update - January 2025

Explore the power of Python Notebooks in Fabric!

JanFabricDW_carousel

Fabric Monthly Update - January 2025

Unlock the latest Fabric Data Warehouse upgrades!