Get certified for free when you join Fabric Data Days 2026 and dive into Fabric, Power BI, SQL, AI, and other essential data skills.
Join nowJuly 7 - July 17 | Round 2 of the Power BI Dataviz World Championships. Don't miss your chance! Learn more
Running on-premise Power BI in a highly regulated environment, security scans flagged the Public security group as a vulnerability and we are looking for work arounds to pass the audit. I'm having a hard time finding any information regarding the usage of the Public security group and the effects if we removed the group.
Short of just removing it and seeing how the system responds, does anyone have any suggestions or experience with disabling or removing the Public security group?
Hi @gantta_del ,
Specifically for security groups what is the vulnerability, can you provide screenshots of that and explain it.
Also for security groups, it is the IT administrator who creates and maintains these groups. Specific information about security groups can be found in the following blog.
Looking forward to your reply.
Best Regards,
Henry
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Thanks for the link, but I'm looking specifically at the SQL Server Database security groups. I wasn't present when the Power BI service was initially installed, but our team has inherited responsibility for managing the service.
As I understand it, the Power BI installation running on a VM comes out of the box with a SQL Server database security group named Public. The vulnerability test identified this group as invalid and should look to create permissions based on least-privileged requests for the security groups.
Join us in Barcelona for FabCon and SQLCon, the Fabric, Power BI, SQL, and AI community event. Save €200 with code FABCMTY200.
Join Fabric Data Days 2026: 60 days of free live/on-demand sessions, challenges, study groups, and certification opportunities.
| User | Count |
|---|---|
| 4 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |