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

A new Data Days event is coming soon! This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. Don't miss out.

Reply
AditiPattnaik
Advocate II
Advocate II

OneLake Security Errors. Security Sync and SQL Query InternalError.

Hi,
I was trying one lake security on a shortcut table. From source Lakehouse i have applied onelake security role. However it is not reflecting in the target Lakehouse and throwing these two errors:image (2).png

 

image (1).png

 Can anyone tell me what could be the possible solution?

5 REPLIES 5
v-karpurapud
Community Support
Community Support

Hi @AditiPattnaik 

We would like to confirm whether the issue has been resolved. If it is still outstanding, please share any additional information so we can assist you further.

Thank you.

v-karpurapud
Community Support
Community Support

Hi @AditiPattnaik 

I wanted to check if you’ve had a chance to review the information provided. If you have any further questions, please let us know. Has your issue been resolved? If not, please share more details so we can assist you further.

Thank You.

Hey @v-karpurapud 

I still have go through, will definitely get back once done.

Thank you.

Hi @AditiPattnaik 

Thank you for the update. Looking forward to your response.

Regards,

Microsoft Fabric Community Support Team

 

v-karpurapud
Community Support
Community Support

Hi @AditiPattnaik 


Thank you for reaching out to the Microsoft Fabric community forum.

 

The error occurs because OneLake shortcuts use a passthrough security model, meaning the security roles applied in the source Lakehouse must synchronize to the target Lakehouse shortcut and SQL endpoint. If the security sync does not complete successfully, the shortcut will not reflect the correct permissions, which can result in security sync failures and SQL InternalError. As explained in the Microsoft documentation and Fabric blog, shortcut access is always controlled from the source Lakehouse, and the SQL endpoint depends on the security sync service to validate access: https://learn.microsoft.com/en-us/fabric/onelake/security/get-started-onelake-security https://blog.fabric.microsoft.com/en-us/blog/understanding-onelake-security-with-shortcuts/

To resolve this, please open the target Lakehouse SQL endpoint and click Metadatasync, then refresh after a few minutes. Also ensure the OneLake security role is applied at the table level in the source Lakehouse, and recreate the shortcut if it was created before applying security. Verify the user has both the required workspace role and OneLake security role permissions, as shortcut access is governed by source permissions.

If you have any further questions, feel free to reach out and we'll be glad to assist.

 

Regards,

Microsoft Fabric Community Support Team.

 

Helpful resources

Announcements
April Fabric Update Carousel

Fabric Monthly Update - April 2026

Check out the April 2026 Fabric update to learn about new features.

Fabric SQL PBI Data Days

Data Days 2026 coming soon!

Sign up to receive a private message when registration opens and key events begin.

New to Fabric survey Carousel

New to Fabric Survey

If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.