Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

The Power BI Data Visualization World Championships is back! It's time to submit your entry. Live now!

Reply
sahinad
Regular Visitor

OneLake Security DatamartsUserNotAuthorized issue

Hi,

OneLake Security got stuck with a deleted role and it is not functioning properly anymore.

I have deleted this role but the error keeps coming back. Hours have passed, but it's not getting any better.

Any advice?

Thanks.

error_details.png

datamartsnotauthorized.png

  

1 ACCEPTED SOLUTION
dinesh_7780
Resolver V
Resolver V

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.

View solution in original post

2 REPLIES 2
dinesh_7780
Resolver V
Resolver V

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 @dinesh_7780.

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.

Helpful resources

Announcements
December Fabric Update Carousel

Fabric Monthly Update - December 2025

Check out the December 2025 Fabric Holiday Recap!

FabCon Atlanta 2026 carousel

FabCon Atlanta 2026

Join us at FabCon Atlanta, March 16-20, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.