This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. We're covering it all. You won't want to miss it.
Learn moreDid you hear? There's a new SQL AI Developer certification (DP-800). Start preparing now and be one of the first to get certified. Register now
We are connecting our PBI file to an existing dataset on a Premium workspace using the Power BI Service data connector (Open up Power BI Desktop>Get Data>Power BI Service). The existing dataset on the service is using Row-Level Security which uses the UserName() function in Dax. When I connect my new PBI file pointed to the service's dataset the UserName() is returning NT Authority\System. Has anyone run into this, how would I return the username of whomever is running the report? I assume since I am not logging into app.powerbi.com directly to access this dataset, it has no idea of who I am, so it's returning the System account. Anyone using this method with RLS and have a working solution?
@Anonymous,
I can reproduce your issue, I will consult this issue internally, and post back.
Regards,
Lydia
Any update to this? We have the same issue. Our Users work with Power BI Desktop using direct Connection to datasets in the service.
It has been a long time, but this issue still occurs.
It can be solved by adding a role to a dataset. It is very similiar to below case:
Using Username() in DAX with Row-Level Security | Microsoft Power BI Blog | Microsoft Power BI
It seems that with workspaces in shared capacities USERNAME() returns a guid value, while in Premium capacitites it returns "NT AUTHORITY\SYSTEM".
Check out the April 2026 Power BI update to learn about new features.
Sign up to receive a private message when registration opens and key events begin.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
| User | Count |
|---|---|
| 36 | |
| 33 | |
| 31 | |
| 21 | |
| 16 |
| User | Count |
|---|---|
| 66 | |
| 55 | |
| 31 | |
| 24 | |
| 23 |