Snowflake data masking policy implementation to Power BI

The issue here is: When a dashboard developer creates a Dashboard, then publishes the Dashboard to Power BI service, it will continue to use the original credential set EVEN IF SNOWFLAKE SSO IS ENABLED. So, you basically get RBAC for the development process but you're then stuck once you deploy. It's a tricky hole to fall into.

Power BI service needs to offer a way to say, "When SSO is configured, use the Viewers credentials to access the data. Do not use the Developers credentials." That needs to be coupled with a way to say, "Always query this data" or "Use a per-user caching mechagnism to persist RBAC behavior from the data source." I think the best part about this approach is that it shouldn't be uppended by whichever user pool you use in the backend. This is just general interoperability functionality that Microsoft could prioritize to have a more robust ecosystem, but for some reason have not--a possibly simple change in behavior, order of operations on the backend, namespace configuration for caching, ... It shouldn't require they partner with Snowflake at all.

What would be great is to see this show up as a feature request, get prioritized, and be released. Not to scope creep this, but it would also be amazing if Power BI service could do this with any remote User Pool backend, such as AWS Cognito. Because we'd love to do the same thing but withn S3, Glue, Athena, and LakeFormation based lakehouse.