SharePoint Groups vs Microsoft 365 Groups vs Entra ID Security Groups
Learn the differences between SharePoint groups, Microsoft 365 groups and Entra ID security groups. See where each can be used, whether groups can contain other groups, who manages them, how guests work and what appears in audit records.

SharePoint groups control permissions within a site. Microsoft 365 groups and Entra security groups can also give people access, but their membership is managed in Microsoft Entra. To understand someone's access, identify which group holds the SharePoint permission and which people belong to it, including through nested security groups.
A SharePoint role assignment can point at three fundamentally different kinds of group, and each one answers "who is in it, who manages it, and where does its history live" differently. Confusing them is how permission reviews go wrong: a reviewer counts the members of a SharePoint group, finds two, and misses the Entra ID security group inside it that carries forty contractors.
The three group types at a glance
| SharePoint group | Microsoft 365 group | Entra ID security group | |
|---|---|---|---|
| Where it lives | Inside one site collection | Entra ID (with a connected SharePoint site, mailbox, Teams team) | Entra ID |
| Scope | That site collection only | Tenant-wide object; used by many workloads | Tenant-wide object; used by many workloads |
| Can contain | Users, Entra ID security groups, Microsoft 365 groups | Users only (owners and members) | Users, other security groups, devices, service principals |
| Nesting | No (cannot contain SharePoint groups) | No | Yes (security groups in security groups) |
| Guests | Yes, if the site allows sharing | Yes, if guest access is enabled | Yes |
| Managed by | Site owners, in the site | Group owners, in Outlook, Teams, Entra ID or Graph | Entra ID administrators or group owners; may be dynamic |
| Membership changes audited in | Unified Audit Log (SharePoint operations) | Entra ID audit log and the Unified Audit Log | Entra ID audit log and the Unified Audit Log |
| Login name in SharePoint | The group's own name (no claim prefix) | `c:0o.c | federateddirectoryclaimprovider |
SharePoint groups
SharePoint groups are the oldest mechanism. Team sites get three by default, Owners, Members and Visitors, usually bound to Full Control, Edit and Read on the root web. Site owners can create more.
Key properties:
- Site-scoped. A SharePoint group exists only inside its site collection. "Finance Visitors" on the Finance site and "Finance Visitors" on the HR site are unrelated objects with different integer ids.
- No nesting. A SharePoint group cannot contain another SharePoint group. It can contain Entra ID security groups and Microsoft 365 groups, which is where nesting sneaks in.
- Membership is a SharePoint operation. Adding or removing a member is a SharePoint event (
AddedToGroup,RemovedFromGroup) attributed to the site owner or administrator who did it, and it appears in the Unified Audit Log under the SharePoint workload. - Visible in the site. Site settings, People and groups, lists them with their members, but only the direct members. An Entra ID group inside shows as one row.
List a SharePoint group's direct members with PnP PowerShell:
Get-PnPGroupMember -Group "Finance Visitors" | Select-Object Title, LoginName, PrincipalType
PrincipalType 1 is a user; 4 is a directory group you need to expand separately.
Microsoft 365 groups
A Microsoft 365 group is an Entra ID object with attached services: a group mailbox, a SharePoint team site, optionally a Teams team and a Planner plan. When you create a team site or a team, SharePoint automatically adds the group's owners to the site's Owners SharePoint group and its members to the Members SharePoint group, using the group's two Entra ID roles (Owners and Members) as claims.
Key properties:
- Tenant-wide object, but one site. The group id is a GUID in Entra ID; the connected site is one site collection. A Microsoft 365 group can also be granted on other sites just like any directory group, which is the case that surprises people.
- No nesting. A Microsoft 365 group cannot contain groups. Its membership is flat, which makes it easy to expand but also means large groups get large.
- Owner-managed. Group owners add members from Outlook, Teams or Microsoft 365 Groups in Entra ID without touching SharePoint. The change is an Entra ID audit event (
Add member to group.) and, for Teams-connected groups, a Teams event too, so do not rely on SharePoint operations alone to find it. - Guest membership follows the group. If guest access is enabled for the group, guests added to it get the connected site's Members permissions automatically.
In a SharePoint role assignment the login name looks like c:0o.c|federateddirectoryclaimprovider|<group id> for the members role, with _o appended for the owners role. Expand it with Graph:
GET https://graph.microsoft.com/v1.0/groups/{id}/members?$select=id,displayName,userPrincipalName,userType
Entra ID security groups
Security groups are the general-purpose directory group. They have no attached services, can be assigned to applications, roles, licenses and SharePoint sites, and, critically, can contain other security groups.
Key properties:
- Nesting is allowed, so check it carefully. Entra security groups can contain other groups. When a security group is used for SharePoint access, nested membership needs to be checked carefully: SharePoint shows the outer group as one entry and does not show the groups inside it, so you have to expand them in Entra ID. Microsoft warns that nested security groups can cause performance issues and does not recommend them, and lists the nesting combinations Entra ID does not support.
- Dynamic membership. A security group can have a rule such as
user.department -eq "Finance". Membership then changes whenever user attributes change, so a person may not be named on the membership event. - Mail-enabled security groups are supported by SharePoint. Distribution groups are for email, so use a security group or Microsoft 365 group to grant access.
- Management is wherever the group is managed. Entra ID admins, group owners, an HR-driven provisioning system, or a dynamic rule. Changes are Entra ID audit events, so look there as well as in SharePoint operations.
Flatten a security group, including nesting, with transitiveMembers:
Get-MgGroupTransitiveMember -GroupId $groupId -All -Property id,displayName,userPrincipalName,userType |
ForEach-Object { $_.AdditionalProperties } |
Where-Object { $_.'@odata.type' -eq '#microsoft.graph.user' } |
Select-Object displayName, userPrincipalName, userType
To see the structure rather than the flattened result, list direct members and recurse into anything whose @odata.type is #microsoft.graph.group.
Why the distinction matters for reviews and audits
Different owners. A SharePoint group is controlled by site owners. A Microsoft 365 group is controlled by its group owners, who may know nothing about the sites it has been granted on. A security group is controlled by whoever manages the directory. A permission review that only asks the site owner covers one of three.
Different audit trails. SharePoint group changes are SharePoint events. Directory group changes are Entra ID events. A review of "who changed access to this site" that only looks at SharePoint operations misses every membership change in directory groups. Directory-group membership changes can affect SharePoint access even when nobody changes the permissions directly on a site.
Different retention. Entra ID's own audit log retains 30 days (with the right licensing; 7 days on Free). The Unified Audit Log retains 180 days on Audit (Standard) and one year on Audit (Premium). If you need longer history, check the available Microsoft audit-retention options and save relevant records before they expire.
Nesting hides scale. A SharePoint group with "two members" can be one user and one security group containing three nested groups and four hundred people. Member counts can mislead, so review transitive membership.
A practical review checklist
- On the inheritance boundary, list every role assignment with
$expand=Member,RoleDefinitionBindings. - Classify each principal by claim prefix: user, SharePoint group, Microsoft 365 group, security group, claim, sharing link.
- For SharePoint groups, list direct members and classify those too.
- For Microsoft 365 groups, list
members(flat). - For security groups, list
transitiveMembersand, if you need the route, walkmembersrecursively. - Record
userTypefor every user;Guestis the external population. - Repeat for every unique-permission object below the site, because each one is its own boundary.
FAQ
- Can I nest a Microsoft 365 group inside a security group?
- No. Microsoft lists adding Microsoft 365 groups to security groups or to other Microsoft 365 groups, and adding security groups to Microsoft 365 groups, among the nesting scenarios Entra ID does not support.
- Why do group membership changes take time to affect SharePoint?
- Directory group changes can take time to reach SharePoint, so removing someone from a group may not remove their access immediately.
- Are distribution lists usable for SharePoint permissions?
- No. Distribution groups are for email. To grant access, use security groups, mail-enabled security groups or Microsoft 365 groups.
Related reading
Related guides
All guides
SharePoint Permissions11 min readintermediate
How to Find Out Why a User Has Access to a SharePoint Site
Learn how to find out whether someone has SharePoint access directly, through inherited permissions or through groups inside other groups. Follow the steps using the admin interface, REST and PowerShell.

Microsoft 365 Security9 min readbeginner
Does Microsoft 365 Copilot Respect SharePoint Permissions? What Can It See?
Copilot follows SharePoint permissions, so it only shows each person what they can already open. Learn what that includes, when a sharing link counts, how to find content open to everyone, and how to limit what Copilot finds while you fix it.

SharePoint Permissions8 min readbeginner
How to See Who Has Access to a SharePoint Site, Folder, or File
Use SharePoint's own screens to see who has access to a site, a folder or a single file, and learn what each screen leaves out, from the people inside groups to site admins and sharing links.