Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and more.
Get startedGrow your Fabric skills and prepare for the DP-600 certification exam by completing the latest Microsoft Fabric challenge.
HI,
My Main fact table i have connected to Azure databricks direct query.
and users table i have created with in desktop for now as table.
when i joined both first of all Apply security filter in both directions is greyed out, i am not sure why it is greyed out, if i change the filter to both its appearing but unable to turn on the apply security, however, i just used it as is. my RLS is working fine.
but when i publish the same and make sure users are ghranted access to semantic model and they are added to role in security section.
when i am tetsing the RLS in service i am getting below error, can you explain me this behaviour and cause of the issue here?
@amitchandak @Arul @lbendlin @mwegener @GilbertQ @ibarrau
Solved! Go to Solution.
Security option will be enabled for both directional relationship to allow applying RLS in both the direction,
As per screenshot shared as you have one to many relationship this is not applicable thus grayed out.
You issue is related to the accessing Azure resources only
@AnkitKukreja @arvindsingh802 thank you for your time answering me.
what about the apply security is greyed out? can you shed some light on that? that is causing the issue in service and RLS is not working.
Security option will be enabled for both directional relationship to allow applying RLS in both the direction,
As per screenshot shared as you have one to many relationship this is not applicable thus grayed out.
You issue is related to the accessing Azure resources only
Hi! @johnbasha33
That is tough to suggest without taking look at the model and all the relevant details, I would suggest you to give a read to this doc again and see if you've missed something.
https://learn.microsoft.com/en-us/fabric/security/service-admin-row-level-security
Hi @johnbasha33
401 error generally points out to unauthorized access, have a look at Arvind's suggestion.
It seems IP filterring has been confirgured in your Azure env, please connect with your Azure Admin to add Power BI IP ranges to the access list
Join the community in Stockholm for expert Microsoft Fabric learning including a very exciting keynote from Arun Ulag, Corporate Vice President, Azure Data.
Check out the June 2024 Power BI update to learn about new features.
User | Count |
---|---|
55 | |
39 | |
33 | |
31 | |
25 |