Forum Discussion
Lakehouse Grant Read Permission Problem
Hello everyone,
I have tried a lot of things but I could not find a way to grant someone to read specific table (metadata and data) in lakehouse by using Spark without giving read permission to him/her in workspace of lakehouse.
Any help appreciate.
After some tests, I got the exactly same error message. The cause could be the third to last limitation of schemas in this list: https://learn.microsoft.com/en-us/fabric/data-engineering/lakehouse-schemas#public-preview-limitations .
There could be two solutions though they aren't perfect.
1. Stop using schema.
2. Use Pyspark instead like following, the address is an ABFS address.
df = spark.read.load("abfss://[email protected]/0558838e7/Tables/dbo/sales") display(df)
14 Replies
You can give someone access to just the lakehouse in the workspace, but not a specific table - goof article (https://www.mssqltips.com/sqlservertip/8053/how-to-manage-access-control-for-a-microsoft-fabric-lakehouse/)
But if you create a warehouse, those tables can have acces granted individually. This is one of the limitations of a Lakehouse versus a Warehouse. I am sure they are working on item level access, but it is not here yet in LakehouseSo as far as I understand from your words if I want to use lakehouse instead of warehouse, there should be more lakehouses in order to provide granular security. Am I right?
Hi ismail_ozturk,
You should be able to do this with OneLake RBAC: OneLake security access control model (preview) - Microsoft Fabric | Microsoft Learn
This is still in preview, so it might not work 100% and it might change.
If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution.
There is a more complicated way to grant access to the underlying folder structure (Tables\dimCategory), but I think it is still in preview.
Yeah it is still in preview and does not work for now as fas as I tested.
