Hello jibran_wani, yes it is still an issue. However, I might be able to shed a little more light.
I opened a support ticket with Microsoft and they had one of their contractors working on their development team trying to figure it out. He spent almost 2-weeks inspecting my pbix and recreating the problem. I was told it had something to do with the way I had my table relationships and some of my calculated columns.
Apparently, using calculated columns to reference other tables (like "related", lookup, and such) can create such a back door. And, has something to do with how I have table relationships outside of the original master fact table. I have a table called "Roster" that contains all my RLS as well as department numbers, account numbers, and other identifiers. However, our Company's data has some flaws so I have no choice but to connect certain tables to each other through a common identifier and then just connect one of them to the Roster. From what I was told that could create the "back door" effect that I am experiencing. This gives the user access to data they wouldn't normally see in visuals, but since Copilot queries the tables directly, it can access that data.
I was able to fix some of the calculations and relationships to lessen the issue, but could not fix all, otherwise, I lose much much-needed functionality of the report.
Yes, I did originally post in the Community Issues then posted here at the advice of one of the Super Users.
I posted this in the community forum and am now reposting it here at the advice of a Super User response. While testing the "Preview" toggle of Copilot within Power BI Service, I observed that i...