Sharing via Security Group not Working

Hi MikeJokeBI, 

when you say no user has access after it has been shared, can you expand on that? What do they see? Do they see an empty report with an error, do they never get to the report itself? 

Does your report's semantic model sit in the same workspace as the report? Is it a composite model that connects to other models? 

permissions here can be nebulus, especially when semantic models cross over between workspaces. 

I agree with Parchitect that an app is the way to go, but if sharing the report directly doesn't work, then you won't have much luck with the app until you figure out why. 

Hi MikeJokeBI,

What's the purpose of sharing the Workspace? If it's just to consume dashboard then I would use an app and use audience and set security group. 

This can also be a licences issue depending on your workspace. The consumers need license if it's below F64 capacity. So assign right license. https://learn.microsoft.com/en-us/power-bi/fundamentals/service-features-license-type

//Parchitect

Hello Parchitect,

thanks for the super quick answer.

Unfortunately I havn't worked with APP in Power BI yet.

We already either directly shared the Dashboards, or created Workspaced for each Department (Sales, Logistics, etc.) and stored all Department relevant Dashboards in the specific Workspace.
Then we managed the access via the Workspace.

Every User has the MS 365 E5 License with PowerBI Pro.

But based on your message it looks like we should change our setup for sharing Dashboards?

Yes, the strategy should be for easier governance at scale:

* Workspace access for content creators

* Apps for report consumers

You should not directly share dashboard to users, if possible do it through security groups but only to the dashboard and underlaying source. The better way i mentioned is Apps, which is easy to setup.

Create an App in your test workspace, add report then audience with the security group, and if the report uses a semantic model from other workspace, add the security group to it there. If it works then its likely related to how its currently being shared. If it does not work, add a single test user directly to audience. That will tell us whiether the problem is with the Entra security group or somewhere else in the access. 

// Parchitect

Hi MikeJokeBI 
We would like to inquire whether have you got the chance to check the solutions provided by tayloramy & Parchitect in commiunity to resolve the issue. We hope the information provided helps to clear the query. Should you have any further queries, kindly feel free to contact the Microsoft Fabric community.

Thanks,
Srikanth Cheri
Community Support Team.

Hi MikeJokeBI 

Hope you're doing well! Just wanted to follow up and see if you got a chance to test after the AD/Security Group update. Did the suggested approach resolve your issue.

Thank you.