What causes LakehouseForbiddenError?

The service principal or user running the pipeline is not a Workspace Member or Contributor. The Fabric item (Lakehouse) has item-level permissions that deny access to the pipeline identity. The pipeline is running in a workspace where the managed identity has no role assignment. Cross-workspace access: the Lakehouse is in a different workspace than the pipeline, with no shared access. The Fabric capacity is paused or the workspace is in a suspended state

How do I fix LakehouseForbiddenError?

Add the pipeline's service principal or user as a Workspace Member or Contributor in Fabric workspace settings.

High severitycredentials

Power BI Refresh Error:
LakehouseForbiddenError

What does this error mean?

A Fabric pipeline or dataflow was denied access to a Lakehouse (403). The pipeline identity needs Workspace Member or Contributor role on the Fabric workspace.

Common causes

1The service principal or user running the pipeline is not a Workspace Member or Contributor
2The Fabric item (Lakehouse) has item-level permissions that deny access to the pipeline identity
3The pipeline is running in a workspace where the managed identity has no role assignment
4Cross-workspace access: the Lakehouse is in a different workspace than the pipeline, with no shared access
5The Fabric capacity is paused or the workspace is in a suspended state

How to fix it

1Add the pipeline's service principal or user as a Workspace Member or Contributor in Fabric workspace settings.

Beyond the docs

Common practitioner solutions not covered in the official documentation.

1Check Lakehouse item-level permissions: Fabric portal → Lakehouse → Manage permissions
2For cross-workspace scenarios, share the Lakehouse explicitly with the pipeline's identity
3Verify the Fabric capacity is active and the workspace is not suspended
4If using a managed identity, ensure the Azure resource has Fabric workspace access assigned

Frequently asked questions

Does this error affect all users or just the dataset owner?

All users — scheduled and manual refreshes run under the credentials stored in the dataset settings, not individual user accounts.

Can expired OAuth tokens cause this error?

Yes — if the data source uses OAuth (SharePoint, Dynamics 365, Azure), the token expires periodically and must be re-authorized by the dataset owner.

Will this error clear itself after I update the credentials?

Yes — once you re-enter valid credentials in the dataset settings, the next refresh (scheduled or triggered manually) will succeed.

How do I know which dataset is using which credentials?

Go to Power BI Service → Settings → Datasets → Data source credentials for the affected dataset. Each connection shows the credential type and the account it's stored under.

Source · learn.microsoft.com/en-us/fabric/data-factory/connector-troubleshoot-lakehouse