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!Get Fabric certified for FREE! Don't miss your chance! Learn more
I have a issue trying to construct data pipeline trigger where when i took over the data pipeline from a team member as his credentials is unable to refresh certain dataflows, but when i trigger the pipeline to refresh other items like dataflow gen2 and notebook, it is still using the previous user credentials. How to change it to use my credentials instead?
Solved! Go to Solution.
Hi @Yongjun ,
Thanks for reaching out to Microsoft Fabric Community.
What you’re seeing is expected behavior in Fabric. Taking over a pipeline only changes the ownership of the pipeline item itself. Ownership of related items needs to be changed separately. This includes notebooks, Dataflow Gen2, and any other items referenced by the pipeline. These related items continue to run using the identity that last modified or configured them, even after the pipeline ownership is transferred.
In addition, pipeline items require an extra step after takeover. You must ensure that the Last Modified By user is updated. This can be done by opening the pipeline, making a small edit (for example, renaming an activity), and saving it. The same approach applies to related items: open each notebook or dataflow, update or re-authenticate the connections if required, make a minor change if needed, and save the item so that it runs under the correct identity.
For reference:
Take ownership of Fabric items - Microsoft Fabric | Microsoft Learn
Also thanks to @AntoineW for recommending best practices.
Hope this helps. Please reach out for further assistance.
Thank you.
Hi @Yongjun ,
Just checking in to see if you query is resolved and if any responses were helpful.
Otherwise, feel free to reach out for further assistance.
Thank you.
Hi @Yongjun ,
Thanks for reaching out to Microsoft Fabric Community.
What you’re seeing is expected behavior in Fabric. Taking over a pipeline only changes the ownership of the pipeline item itself. Ownership of related items needs to be changed separately. This includes notebooks, Dataflow Gen2, and any other items referenced by the pipeline. These related items continue to run using the identity that last modified or configured them, even after the pipeline ownership is transferred.
In addition, pipeline items require an extra step after takeover. You must ensure that the Last Modified By user is updated. This can be done by opening the pipeline, making a small edit (for example, renaming an activity), and saving it. The same approach applies to related items: open each notebook or dataflow, update or re-authenticate the connections if required, make a minor change if needed, and save the item so that it runs under the correct identity.
For reference:
Take ownership of Fabric items - Microsoft Fabric | Microsoft Learn
Also thanks to @AntoineW for recommending best practices.
Hope this helps. Please reach out for further assistance.
Thank you.
Hi @Yongjun ,
Just wanted to check if the response provided was helpful. If further assistance is needed, please reach out.
Thank you.
A best practise is to use a service principal / workspace identity to connect to sources to avoid having personal user cerdentials and issue of refresh items.
References :
Share feedback directly with Fabric product managers, participate in targeted research studies and influence the Fabric roadmap.
Check out the February 2026 Fabric update to learn about new features.
| User | Count |
|---|---|
| 29 | |
| 14 | |
| 13 | |
| 6 | |
| 6 |
| User | Count |
|---|---|
| 55 | |
| 45 | |
| 28 | |
| 18 | |
| 11 |