Power BI Snowflake Access Control
Budget: $100 – $150 CAD
I need a small, end-to-end proof of concept that links a Snowflake dataset to a Power BI report and then restricts what each persona can see once the report is published.
Scope
• Build a simple Employee table in Snowflake with First Name, Last Name, Date of Birth and Salary.
• Design the Snowflake roles and grants from scratch (none exist yet) so that one persona can see every column while another sees everything except Salary.
• Connect Power BI to Snowflake, import that table and create a single tabular page that lists the data.
• Configure column-level security (or equivalent) so:
– User A sees all four columns.
– User B sees all except Salary.
The solution must work when the report is shared through the Power BI Service, ideally by mapping the Snowflake roles to our Active Directory groups, but I’m open to other proven methods if that is cleaner.
Deliverables
1. Snowflake SQL script: table DDL, role creation, grants.
2. Power BI (.pbix) file with the security rules in place.
3. Step-by-step notes or a short loom/written walkthrough explaining how to recreate the setup and how to add more personas later.
Acceptance criteria: logging in with two test accounts clearly demonstrates the difference in column visibility, with no back-door access to Salary for the restricted user.
Use whatever tooling you prefer—Snowflake worksheets, Power BI Desktop, Azure AD—just keep it reproducible and clean.
Scope
• Build a simple Employee table in Snowflake with First Name, Last Name, Date of Birth and Salary.
• Design the Snowflake roles and grants from scratch (none exist yet) so that one persona can see every column while another sees everything except Salary.
• Connect Power BI to Snowflake, import that table and create a single tabular page that lists the data.
• Configure column-level security (or equivalent) so:
– User A sees all four columns.
– User B sees all except Salary.
The solution must work when the report is shared through the Power BI Service, ideally by mapping the Snowflake roles to our Active Directory groups, but I’m open to other proven methods if that is cleaner.
Deliverables
1. Snowflake SQL script: table DDL, role creation, grants.
2. Power BI (.pbix) file with the security rules in place.
3. Step-by-step notes or a short loom/written walkthrough explaining how to recreate the setup and how to add more personas later.
Acceptance criteria: logging in with two test accounts clearly demonstrates the difference in column visibility, with no back-door access to Salary for the restricted user.
Use whatever tooling you prefer—Snowflake worksheets, Power BI Desktop, Azure AD—just keep it reproducible and clean.
Related categories:
SQL
Active Directory
Business Intelligence
Data Visualization
Data Analysis
Power BI
Database Management
Snowflake