Apr 09 2017 09:58 PM
We have a sharepoint online tenant, In which one sitecollection is shared externally to certain domains. For most of the domains and users it is working fine when we share the external user contribute permission.
But for one domain which has one active user when the sub site is shared as contribute or even owner it shows shared but with a lot of Deny access. But for other external user it is just showing the contribute access allowed and not the deny.
Now the user can see the landing page ( one list view web part , document library , contact web part)
But when it click the list and tries to go to the list page the url keeps redirecting and to login.microsoft and then back to the list endlessly.
I already deleted the user once then re added it but to no use, Elevated to owner permission still no use. Any suggestions would be helpful
Thanks
Apr 09 2017 11:15 PM
Apr 10 2017 07:46 PM
I can see the permission Read , contribute and list of deny permissions.
Apr 10 2017 10:46 PM
Apr 24 2017 10:47 PM
SolutionIt was problem with the user role in azure AD , changed that to User which fixed the issue.
Feb 13 2018 08:44 AM
The solution for this issue is to add your own domain to the list of allowed domains(tenantname.onmicrosoft.com) on the Tenant and to the site collection that is being shared externally. In my testing, in some cases by just populating external user's work email address in the user's profile did work and in some cases, I had to add our own domain to allowed list.
Please let me know if this solution worked for you.
Mar 14 2018 09:46 PM
Hi Kanwar - can you please share in detail what you had to do to remove the DENY? I have checked my external user too and they are marked as a user role within Azure AD.
Jan 14 2019 09:57 AM
Hello All, I am also facing the similar issue - When given the READ only access to a external user. I am seeing the permissions are as attached. User is not able to access the site.
May i know why i am seeing the Deny permissions? How can i remove this Deny permission.
Thanks & Regards,
Bhanu
Apr 24 2017 10:47 PM
SolutionIt was problem with the user role in azure AD , changed that to User which fixed the issue.