Using AD groups for setting security in Sharepoint

Question

Recently we experience issues with SharePoint security set using AD groups:

Members of these groups are intermittently getting access denied. A few hours later they are able to access the resource (eg site) without error.

The strange thing is that if the AD group is encapsulated in a SharePoint security group, the issue is not present. Members of the AD group when encapsulated are not getting this erroneous behaviour.

trevor seward · Answer

While AD groups may be 'best practice' from a Search performance perspective, they hamper end user control over permissions on a site and increase soft costs for IT. I think there's a good hybrid approach, where security groups are used for primary divisional/portal sites, but let users manage security on team-focused sites.

bart_vermeersch · Answer

To go back to my initial issue ;-)&nbsp;We found there are two seperate issues, the one we figured out properly goes as follows:&nbsp;Target audiences set on navigation menu (I know it's not best practice from perfomance point of view).If the target audience contains&nbsp;a (synced) AD group, it sometimes fails (members of the AD group don't see the menu item).&nbsp;If&nbsp;a SharePoint groups is created with the AD group as only member, and this SharePoint group is put in the target audience, we don't experience any issues.&nbsp;So we are creating SharePoint groups (for every AD groups) and use these for target audience.&nbsp;

abhimanyu singh · Answer

Bart Vermeersch wrote:&nbsp;[..]The strange thing is that if the AD group is encapsulated in a SharePoint security group, the issue is not present. Members of the AD group when encapsulated are not getting this erroneous behaviour.Would need more clarification on this last paragraph of yours, specifically&nbsp;what do you mean by "encapsulation"?&nbsp;&nbsp;I am not sure about the error, however for the other part&nbsp;- from what I can understand, this is actually a best practice. For any given site (or collection), there are by default at least three SP Groups - Site Visitor, Site Members, and Site Owners. You would typically add AD Security Groups to one of these default groups and are good to go. Should you need any specific access control, you create an SP Group&nbsp;and add the relevant AD Security Group there.&nbsp;&nbsp;

jason e. heiser · Answer

From the Search perspective you to take a hit when individual permissions are used as opposed to AD. When you add individuals to a SP group a full crawl will be launched at the next pass of content in order to calculate the ACLs for each individual. So - if you add 100 individuals you will have 100 ACLs calculated for every piece of content. If you have 1 AD group with 100 users you only have&nbsp;1% of the hit in the crawl.&nbsp;Precisely as Trevor Seward&nbsp;stated the general guidance from Technet is this :Considering the previous advantages and disadvantages, here are the recommendations:For intranet sites that are broadly accessed by your users, use security groups because you do not care about the individual users who accessed the intranet site home page.For collaboration sites that are accessed by a small group of users, add users directly to SharePoint groups. In this case, there is more of a need to know who is a member so the group members know each other’s e-mail addresses and how to contact one another.

trevor seward · Answer

Was the audience being compiled after a member was added/removed from the AD group? Compilation only occurs on Sunday in the early AM hours (enforced Online, adjustable on-prem).

Forum Discussion

Using AD groups for setting security in Sharepoint

7 Replies

Resources