The ultimate Microsoft Fabric, Power BI, Azure AI, and SQL learning event: Join us in Stockholm, September 24-27, 2024.
Save €200 with code MSCUST on top of early bird pricing!
Find everything you need to get certified on Fabric—skills challenges, live sessions, exam prep, role guidance, and more. Get started
We are looking if the current behavior is expected as for us it is quite weird:
1. We are making 2 Links , as per below images, one is for all of the people in your organization, and one is for one of the person, in which outside of the list in direct access (let's call this A ).
2. We are trying to give the access of the 2nd link to other people (Not A), in which, we expect that other people should not be able to access since the link is only given to A. However in fact, the other people able to access it, as the first link is already given for everyone in the organization to be able to access.
May I know if this behavior is expected, or is this a bug? We expect that in actual, the 2nd Link should only be able to be opened by A as it only be shared to him, but in fact since the first link has been shared to everyone in organization, it impacted the 2nd link too.
Thank you for everyone who can explain us about this.
Hi @Gio93ivan
The URLs can be provided and available to every one in an organization. What should not be available to every one is the data that resides in the semantic model. For a user to see data in either Link he needs to be added to a security group and the security group was granted permission as viewer on the semantic model.
So check if those people are added to the Workspace (which is not recommended) of the semantic model, they must have been added and granted permission on the semantic model somewhere.
Regards
Amine Jerbi
If I answered your question, please mark this thread as accepted
and you can follow me on
My Website, LinkedIn and Facebook
Hi @aj1973 ,
Thank you for your reply, We have checked the workspace Access and also the semantic model , this particular person in which we give the 2nd link, is not part of any of it, and yet, they are still able to access it.
So, we still believe that above weird behavior of the sharing is still the case on this one.
Are you guys using security groups for access ? Sorry but I keep the doubts on 😉
Regards
Amine Jerbi
If I answered your question, please mark this thread as accepted
and you can follow me on
My Website, LinkedIn and Facebook
Actually, this is one of my suspicion as well so for this particular scenario, we make sure there is no security group access at all.
May I know why, just out of curiosity !
Security groups can save a lots of headache as such.
For info do you know that a Workspace can't have more than 100 User Principal for exemple !?
Regards
Amine Jerbi
If I answered your question, please mark this thread as accepted
and you can follow me on
My Website, LinkedIn and Facebook
At the moment, the organization user is still very small, thus we have no plan yet to use security groups.
There is plan however, in the future if the organization become bigger and there's clear role of how should the PBI is being used, we will use the security groups feature.
Still, since the security group is out of the picture at the moment, this weird share behavior is still intact and I am more towards think that this is a bug instead of intended behavior...
Join the community in Stockholm for expert Microsoft Fabric learning including a very exciting keynote from Arun Ulag, Corporate Vice President, Azure Data.
Check out the August 2024 Power BI update to learn about new features.
User | Count |
---|---|
55 | |
26 | |
14 | |
14 | |
12 |
User | Count |
---|---|
106 | |
39 | |
28 | |
22 | |
22 |