The ultimate Fabric, Power BI, SQL, and AI community-led learning event. Save €200 with code FABCOMM.
Get registeredEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
I have 2 lakehouses with their respective SQL Analytics endpoint, I am implementing column-level security on the first one and want to have a shortcut for some tables into the second one, but from what I am seeing is that I need to re-implement the security for that shortcut table in second lakehouse? In other words the security implemented in the first lakehouse for those tables will not be taken into account when I am going to be querying their shortcuts in second?
Solved! Go to Solution.
Hello @koltonist
Yes, you are 100% correct. If you create shortcuts to tables in a second Lakehouse, the column level security from the first Lakehouse won't transfer automatically. You'll have to set up the security settings again for the shortcut tables in the second Lakehouse. Therfore, by setting up the security settings again, you can keep the data safe and make sure users can only see the columns they are allowed to access.
If you need additional info, Pls read the below official documentations. It might helps you
Implement column-level security in Fabric data warehousing - Microsoft Fabric | Microsoft Learn
Referencing data to a Lakehouse using shortcuts - Microsoft Fabric | Microsoft Learn
Column-level security in Fabric data warehousing - Microsoft Fabric | Microsoft Learn
Thank you!!!
Did I answer your question? Mark my post as a solution!
Proud to be a Super User!
Hi @koltonist,
We haven’t heard back from you regarding your issue. If it has been resolved, please mark the helpful response as the solution and give a ‘Kudos’ to assist others. If you still need support, let us know.
Thank you
Hi @koltonist,
I wanted to check if you had the opportunity to review the information provided by @suparnababu8. Please feel free to contact us if you have any further questions. If the response has addressed your query, please accept it as a solution and give a 'Kudos' so other members can easily find it.
Thank you.
Hello @koltonist
Yes, you are 100% correct. If you create shortcuts to tables in a second Lakehouse, the column level security from the first Lakehouse won't transfer automatically. You'll have to set up the security settings again for the shortcut tables in the second Lakehouse. Therfore, by setting up the security settings again, you can keep the data safe and make sure users can only see the columns they are allowed to access.
If you need additional info, Pls read the below official documentations. It might helps you
Implement column-level security in Fabric data warehousing - Microsoft Fabric | Microsoft Learn
Referencing data to a Lakehouse using shortcuts - Microsoft Fabric | Microsoft Learn
Column-level security in Fabric data warehousing - Microsoft Fabric | Microsoft Learn
Thank you!!!
Did I answer your question? Mark my post as a solution!
Proud to be a Super User!
Are there plans from Microsoft to make it possible to inherit the T-SQL security?
Hi @koltonist,
May I ask if you have resolved this issue? If so, please mark the helpful reply and accept it as the solution. This will be helpful for other community members who have similar problems to solve it faster.
Thank you.
Hi @koltonist
I'm not sure on the future plans. Inheriting T-SQL security would be valuable feature for lot of users are expecting from microsoft. So, as I mentioned earlier, this idea got enough votes, the will try to bring this in future.
Thank you!!
Did I answer your question? Mark my post as a solution!
Proud to be a Super User!
User | Count |
---|---|
17 | |
9 | |
5 | |
3 | |
3 |
User | Count |
---|---|
46 | |
23 | |
17 | |
13 | |
12 |