Pipeline fails with “LakehouseOperationFailed: Unauthorized” despite having admin and Lakehouse perm

[NaveenUpadhye]

We are experiencing repeated “Unauthorized” failures when running a Fabric pipeline that writes data to a Lakehouse table, even though the user and workspace have full administrative permissions.

“Can use” access on the Lakehouse artifact in Fabric, and

simple  CREATE TABLE dbo.Permission_Test (...) in notebook  runs successfully under the same user identity for that lakehouse, confirming general write permissions.

[NaveenUpadhye]

here is the access info for lakehouse -->

[v-aatheeque · Accepted solution]

Hi @NaveenUpadhye 

“LakehouseOperationFailed: Unauthorized” error is usually not caused by missing admin permissions. Instead, it occurs because pipelines run under a different execution identity (Workspace Managed Identity or Service Principal), which does not inherit your user permissions.

Even though your notebook can successfully write to the Lakehouse under your user account, the pipeline’s runtime identity may not have equivalent access at the Lakehouse artifact level or at the OneLake folder level.

Please ensure that the identity used by the pipeline (Workspace Managed Identity or Service Principal) has:

• Can Use or Admin access on the Lakehouse artifact, and
• If OneLake granular permissions are enabled, write permissions on the Lakehouse Tables and Files folders.
• Re‑run the pipeline to verify resolution.

Hope this helps !!

Thank You.

[v-aatheeque]

Hi @NaveenUpadhye 

Have you had a chance to look through the responses shared earlier? If anything is still unclear, we’ll be happy to provide additional support.

[v-aatheeque]

Hi @NaveenUpadhye 

Following up to confirm if the earlier responses addressed your query. If not, please share your questions and we’ll assist further.

[NaveenUpadhye]

Thanks for the reply.

destination  is lakehouse , where I have the admin access and I mentioned earlier I can able to create or update the tables with notebook in the same lakehouse.

[AsgerLB]

Hi @NaveenUpadhye 

Have you validated the connection used for the destination configurations of the copy data activity? Sometimes signing in again helps. Also remember to share relevant connections if the author of the pipeline is another than the one trying to run it.

Br.

Asger