Incorrect "Submitter" name in Microsoft Fabric

[kishore_kunal]

Hi Everyone,

I’m facing an issue in Microsoft Fabric where the Submitter field in the Spark Monitor does not reflect the actual user who triggered or executed the notebook.

For example, even when I manually run a notebook or trigger it via a pipeline, the Submitter shown is a different user (often someone who ran the pipeline earlier or no longer involved).

This is creating confusion in audit and ownership tracking.

[v-pagayam-msft]

Hi @kishore_kunal ,
We haven't heard back from you regarding our last response and wanted to check if your issue has been resolved. If our response addressed your query, please mark it as Accept Answer and click Yes if you found it helpful. If you have any further questions, feel free to reach out.
Thank you for being a part of the Microsoft Fabric Community Forum!

[v-pagayam-msft]

Hi @kishore_kunal ,
Following up to check whether you got a chance to review the suggestion given.If it helps,consider accepting it as solution,it will be helpful for other members of the community who have similar problems as yours to solve it faster. Glad to help.
Thank you.

[v-pagayam-msft]

Hi @kishore_kunal ,
May I ask if you have gotten this issue resolved?
If it is solved, please mark the helpful reply or share your solution and accept it as solution, it will be helpful for other members of the community who have similar problems as yours to solve it faster.
Thank you.

[v-pagayam-msft · Accepted solution]

Hi @kishore_kunal ,

Thank you for reaching out in Microsoft Community Forum.

Please follow below steps to resolve the error;
1.The Submitter in Spark Monitor often reflects the identity tied to the pipeline's linked service or cached token—not necessarily the person who triggered the run.
2.For reliable tracking, refer to Microsoft Purview Audit Logs or Fabric Activity Logs, which capture the actual user who triggered the action.
3.If pipelines are involved, ensure that the linked service or trigger is configured with the correct user or service principal to reflect proper ownership.
4.Inside notebooks, log the user context manually (e.g., os.getenv("USER")) to help trace the actual executor during runtime.

Please continue using Microsoft Community Forum.

If this post helps in resolving your issue, kindly consider marking it as "Accept as Solution" and give us a 'Kudos' to help others find it more easily.