Forum Discussion
Notebook failing with access issue
Hi,
I’d like to highlight an issue related to executing Notebooks in Fabric ADF:
The Notebook was created by User A, who does not have Contributor access to the Production workspace. As a result, the Notebook execution fails when triggered by Fabric ADF.
However, when Contributor access is granted to the user in the Production workspace, the scheduled pipeline works as expected.
The core concern is that the pipeline should be able to execute the Notebook regardless of whether the creator has Contributor access to the ADF workspace.
Thanks,
Girish
In Fabric, the security context under which a notebook runs depends on how it is triggered:
• Interactive Run: Executes under the current user’s security context.
• Pipeline Activity: Executes under the security context of the pipeline owner.
• Scheduler: Executes under the security context of the user who set up or last updated the scheduleIf the pipeline is scheduled or triggered by a user without Contributor access, or if the pipeline is configured to run under the context of the notebook creator (who lacks Contributor access), execution will fail. To ensure reliable execution:
• The pipeline should be triggered by a user or service principal with at least Contributor access to the workspace.
• Alternatively, use a service principal or managed identity with the necessary permissions to run all production pipelines, decoupling execution from individual user permissions.Avoid relying on individual user accounts for production pipeline execution.
4 Replies
In Fabric, the security context under which a notebook runs depends on how it is triggered:
• Interactive Run: Executes under the current user’s security context.
• Pipeline Activity: Executes under the security context of the pipeline owner.
• Scheduler: Executes under the security context of the user who set up or last updated the scheduleIf the pipeline is scheduled or triggered by a user without Contributor access, or if the pipeline is configured to run under the context of the notebook creator (who lacks Contributor access), execution will fail. To ensure reliable execution:
• The pipeline should be triggered by a user or service principal with at least Contributor access to the workspace.
• Alternatively, use a service principal or managed identity with the necessary permissions to run all production pipelines, decoupling execution from individual user permissions.Avoid relying on individual user accounts for production pipeline execution.
Hi nilendraFabric ,
Thanks for explaining in detail.
As of now the pipelines in prod are scheduled by user, can you provide more details on how to execute the pipelines via service principle or managed identify ?
Thanks,
Girish
Hey Girish, for the pipeline to run the Notebook smoothly in Fabric ADF, the Notebook owner (User A) must have Contributor access to the target workspace, even if they’re not directly executing it.
Thanks nilendraFabric Ashim123 , can you assist how to change ownership of the notebook or pipeline ?
Thanks,
Girish
