RLS testing UI (Test RLS roles directly in the service without publishing workarounds)
Hi Team,
Hope you are doing well!
Now:
Testing Row-Level Security today requires publishing to production first. There is no safe way to validate who sees what before going live. Misconfigured roles are only discovered after the fact, a direct governance and compliance risk.
GOAL :
A native testing pane inside the Power BI Service where developers can simulate any role, impersonate a specific user by email, and immediately see which rows and tables are accessible, without touching the live environment.
Three capabilities: role simulation without publishing, per-table access visibility, and an automated assertion suite that flags regressions whenever the data model changes.
Why ?
Security incidents caused by misconfigured RLS are entirely preventable. This feature makes them so. It also reduces the time developers spend on manual validation cycles from hours to minutes, and provides compliance teams with a formal, exportable audit record of every validation session.
Thank you for considering this, I believe it would be a great addition to the Fabric and power bi experience
1 Comment
- ThornKevin
Advocate I
Waiting since forever for such a feature. Would love to get at least something comparable to Azure RBAC Permission evaluator UI: - Select EntraID User, Group or Identity - Evaluate all roles across hierarchy (in this case, data domain, workspace, Lakehouse item, OneLakeSecurity Object plus CLS or RLS restrictions) Especially to push usage of directLake mode while using multiple lakehouses as source for visuals is a nightmare. No chance to validate if a user is able to see all visuals. In our case, there is one Lakehouse with 20 OneLakeSecurity roles and each has 60 tables assigned where all of them have RLS Rules defined. No chance to test this…..
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_Hernande3 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_holmes11 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_v11 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_12 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...JoshuaPitzer13 hours agoAdvocate INew1.2KViews26likes2Comments