Forum Discussion
Data sharing with another area
Hi Anonymous,
Are you wanting to restrict data based on columns or rows?
FOr column level security in the model, you will need Tabular Editor:
Object-Level Security (OLS) with Power BI - Microsoft Fabric | Microsoft LearnIf you're ingesting all the data into a warehouse, you can also apply column level security at the warehouse level:
Column-Level Security in Fabric Data Warehousing - Microsoft Fabric | Microsoft LearnIf you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution.
Super UserHi Anonymous,
Here’s how I’d enable “automatic” consumption while protecting compensation columns.
- Use a semantic model with Object-Level Security (OLS)
Build a dataset on top of fopag and apply OLS to hide the compensation columns from that specific area. Grant them Build permission on the dataset so they can connect to it (Live connect, Analyze in Excel, or their own reports) without ever seeing those columns. OLS lets you secure specific columns/tables in a model. See: Object-level security (OLS). - Or publish a curated “safe” table and share it via OneLake/Warehouse
Have Dataflow Gen2 write fopag (minus compensation columns) to a Lakehouse/Warehouse in a shared (or new) workspace, then:- Share it via OneLake shortcuts to the requesting area’s workspace (no copying, central governance). See: OneLake shortcuts.
- Or expose it through the Warehouse SQL endpoint so they can pull it directly with ODBC/JDBC/SQL tools into their BI. See: Connect to Fabric Data Warehouse and Warehouse connectivity.
- Label and govern the data
Apply sensitivity labels (e.g., “Confidential – HR”) to the dataset/table so protection and auditing follow the data across exports and usage. See: Sensitivity labels in Power BI and Information protection in Fabric.
If you found this helpful, consider giving some Kudos. If I answered your question or solved your problem, mark this post as the solution.