As Fabric/Power BI administrators, there is currently no straightforward, tenant‑wide way to identify which semantic models have Row‑Level Security (RLS) applied.
Today, the only option is to:
- Scan workspaces individually using Workspace IDs
- Drill down one level to the semantic model
- Extract metadata to determine whether RLS is configured
While this approach works, it is manual, time‑consuming, and not scalable for large environments with hundreds or thousands of workspaces.
Proposed Idea
Introduce a built‑in, centralized way for administrators to view RLS configuration metadata across the entire Fabric tenant, without needing to scan each workspace individually.
Ideally, this would include:
- A tenant‑level report or admin view showing all semantic models with RLS enabled
- Exposure of RLS metadata via:
- Fabric Admin Portal
- Enhanced Admin APIs or XMLA/Metadata endpoints
- Filters by workspace, dataset/semantic model, or RLS presence (Yes/No)
Why This Matters
This capability would significantly improve:
- Security auditing and compliance
- Governance and risk management
- Operational efficiency for admins
Administrators need fast answers to questions like:
- Which semantic models are protected by RLS?
- Where is sensitive data being restricted (or not)?
- Are RLS policies consistently applied across the organization?
Business Value
- Reduces manual monitoring effort
- Improves security posture and compliance readiness
- Enables proactive governance at scale
- Aligns with enterprise‑grade admin expectations for Fabric
Summary
A tenant‑wide, readily available view of semantic models with RLS enabled would be a major enhancement for Fabric administrators. Having this information centrally available—rather than derived through workspace‑by‑workspace scans—would make auditing, governance, and security management far more effective.
Recent ideas
Blocker: Purview must scan Fabric Warehouse tables/columns or we will deprecate Purview
Purview + Fabric Warehouse ≠ enterprise‑ready governance. In our environment, the Fabric Warehouse is the system of record, but Purview can only catalog the warehouse container—not the tables or co...Joshua_Hernande2 hours agoNew MemberNew172Views1like1CommentPower Query Parameter create/use when connecting to a dataflow
In power query when you connect to a table in a dataflow there are no options to create or use a parameter for that dataflow. When connecting to SQL there is an option when setting up the connection ...ben_holmes10 hours agoNew MemberNeed Clarification198Views3likes1CommentParameterize Dataflow Gen2 data source connection
Allow the Dataflow Gen2 data source connection GUID to be parameterized and stored in a Variable Library. This would allow the same Dataflow to use different connections depending on the workspace/e...frithjof_v10 hours agoCommunity ChampionNeeds Votes36Views2likes1CommentExpose Power Query as a Standalone Runtime and Command-Line Interface (CLI)
Summary Power Query has evolved into one of Microsoft's most powerful data transformation technologies and is now used across Excel, Power BI, Fabric, Dataflows, Power Platform, and other products. ...juansgr_10 hours agoNew MemberAbandoned27Views0likes2CommentsExpose User Prompt and Agent Response Logs for Fabric Data Agents
Idea: As an engineer responsible for managing and improving Microsoft Fabric Data Agents, I currently have no way to view how users are interacting with the agents I’ve built. While it’s likely that...JoshuaPitzer12 hours agoAdvocate INew1.2KViews26likes2Comments