Cross-filtering does not limit data access at data source, whereas RLS does. So, if you simply need to have a report filtered down to various items, you should manage that filtering of the report directly through the reports filtering, visuals cross-filtering, and your measures, but if you need the data end-users have access to view to be restricted, this is where RLS comes into play. Hope this helps!

@@Learn-PowerBI I meant cross filter dax function.

Ah, the CROSSFILTER() function would not be able to accomplish any RLS type solution. This function is used for overriding the default models relationship filter direction between the tables specified. For instance, you have a location lookup to your sales table (active one-to-many relationship) and for some reason you want your sales table to filter your lookup table for one of your measures, you could use CROSSFILTER() to adjust the active relationship in the model to change the relationship specified in the model to filter location lookup by the sales table. This function is a pretty niche DAX function that you likely won't be needing in a majority PBI projects. If you see yourself trying to use this function, there is likely an issue with your base model that might need to be adjusted to get the full model to function as intended.

Hello - I'll work on getting a video for this published, wont be able to get it out for a weeks though, sorry! As a stop-gap or to get going on your own, here Microsofts explanation of how to set this up, learn.microsoft.com/en-us/power-bi/developer/embedded/cloud-rls. As a high level overview of how RLS in embedded reports work, see this explanation (not sure if this is helpful or not but hopefully it helps get you started!): - When a user accesses the embedded report, they are authenticated through your app's authentication process. - After authentication, your application will generate an embed token for the user. This embed token is generated through an API call to Power BI, and the information used to generate this token will typically include the user's identifier and the roles that apply to that user, this can include dynamic or static RLS rules that are covered in this course. This embed token is crucial as it dictates what data the user is allowed to see based on the RLS roles and rules defined in the Power BI model. - When the embedded report is accessed by the user, the Power BI service uses the information in the embed token to apply the RLS rules. The filtering based on RLS is performed on the Power BI service side, not in your application. The embedded report in your application will only show the data the user is allowed to see based on the RLS rules. Certainly a lot more in-depth than just RLS for report viewing directly within Power BI service, but totally possible to get setup. I'll work on getting a video out for this ASAP!