Forum Discussion
OneLake Security DatamartsUserNotAuthorized issue
Hi sahinad ,
Try below steps to fix the issue.
1. Audit the affected artifact (datamart or lakehouse):
Go to the workspace > open the datamart > check “Manage permissions”.
Look for any lingering references to the deleted role or its ObjectID.
2. Reassign permissions explicitly:
If the error message includes an ObjectID, manually assign permissions to that ID using Power BI or Fabric Admin tools.
Alternatively, create a new role with the same intended access and assign it to the user.
3. Use PowerShell or REST API to inspect bindings:
Use Microsoft Fabric’s API or PowerShell to list all role bindings for the artifact.
Remove any bindings that reference the deleted role.
4. Clear OneLake security cache (if supported):
There’s no direct “cache clear” button, but re-saving permissions or restarting the workspace may help force re-evaluation.
5. Check for workspace-level security inheritance:
Sometimes roles are inherited from workspace settings. Ensure the deleted role isn’t still referenced there.
Refer below link.
https://learn.microsoft.com/en-us/fabric/onelake/security/get-started-security
If my response as resolved your issue please mark it as solution and give kudos.
Hi sahinad ,
Try below steps to fix the issue.
1. Audit the affected artifact (datamart or lakehouse):
Go to the workspace > open the datamart > check “Manage permissions”.
Look for any lingering references to the deleted role or its ObjectID.
2. Reassign permissions explicitly:
If the error message includes an ObjectID, manually assign permissions to that ID using Power BI or Fabric Admin tools.
Alternatively, create a new role with the same intended access and assign it to the user.
3. Use PowerShell or REST API to inspect bindings:
Use Microsoft Fabric’s API or PowerShell to list all role bindings for the artifact.
Remove any bindings that reference the deleted role.
4. Clear OneLake security cache (if supported):
There’s no direct “cache clear” button, but re-saving permissions or restarting the workspace may help force re-evaluation.
5. Check for workspace-level security inheritance:
Sometimes roles are inherited from workspace settings. Ensure the deleted role isn’t still referenced there.
Refer below link.
https://learn.microsoft.com/en-us/fabric/onelake/security/get-started-security
If my response as resolved your issue please mark it as solution and give kudos.
Thank you Anonymous.
I have recreated the role and assigned the role to the user using its ObjectID and it worked. That's quite interesting. I had tried this before with the user name and it wasn't successful.
