CIS.M365.5.1.6.2: Ensure that guest user access is restricted
| ID | CIS.M365.5.1.6.2 |
| Severity | Medium |
| Suite | CIS Microsoft 365 Foundations Benchmark |
| Product | Entra ID |
| Feature | External identities |
| Security area | External access and sharing |
| Resource type | Tenant |
| User impact of fixing | Low |
| Effort to fix | Low |
| Benchmark | CIS Microsoft 365 Foundations Benchmark 7.0.0, 5.1.6.2 (L1, E3 Level 1, E5 Level 1) |
| Framework controls | cis-m365:5.1.6.2nist-800-53-r5:AC-6 Least Privilege |
| MITRE ATT&CK | T1087.004, T1069.003 |
| Reads from | Microsoft Graph |
What this checks and how to fix it
Section titled “What this checks and how to fix it”5.1.6.2 (L1) Ensure that guest user access is restricted
Microsoft Entra ID, part of Microsoft Entra, allows you to restrict what external guest users can see in their organization in Microsoft Entra ID. Guest users are set to a limited permission level by default in Microsoft Entra ID, while the default for member users is the full set of user permissions.
These directory level permissions are enforced across Microsoft Entra services including Microsoft Graph, PowerShell v2, the Azure portal, and My Apps portal. Microsoft 365 services leveraging Microsoft 365 groups for collaboration scenarios are also affected, specifically Outlook, Microsoft Teams, and SharePoint. They do not override the SharePoint or Microsoft Teams guest settings.
The recommended state is at least Guest users have limited access to properties and memberships of directory objects or more restrictive.
Rationale
Section titled “Rationale”By limiting guest access to the most restrictive state this helps prevent malicious group and user object enumeration in the Microsoft 365 environment. This first step, known as reconnaissance in The Cyber Kill Chain, is often conducted by attackers prior to more advanced targeted attacks.
Impact
Section titled “Impact”The default is Guest users have limited access to properties and memberships of directory objects.
When using the ‘most restrictive’ setting, guests will only be able to access their own profiles and will not be allowed to see other users’ profiles, groups, or group memberships.
There are some known issues with Yammer that will prevent guests that are signed in from leaving the group.
Remediation action
Section titled “Remediation action”- Navigate to Microsoft Entra ID admin center.
- Click to expand Entra ID > External Identities select External collaboration settings.
- Under Guest user access set Guest user access restrictions to one of the following:
- State: Guest users have limited access to properties and memberships of directory objects
- State: Guest user access is restricted to properties and memberships of their own directory objects (most restrictive)
PowerShell
Section titled “PowerShell”- Connect to Microsoft Graph using Connect-MgGraph -Scopes “Policy.ReadWrite.Authorization”
- Run the following command to set the guest user access restrictions to default:
# Guest users have limited access to properties and memberships of directory objectsUpdate-MgPolicyAuthorizationPolicy -GuestUserRoleId '10dae51f-b6af-4016-8d66-8c2a99b929b3'- Or, run the following command to set it to the “most restrictive”:
# Guest user access is restricted to properties and memberships of their own directory objects (most restrictive)Update-MgPolicyAuthorizationPolicy -GuestUserRoleId '2af84b1e-32c8-42b7-82bc-daa82404023b'Note: Either setting allows for a passing state.
Related links
Section titled “Related links”- Microsoft Entra ID admin center
- Restrict guest access permissions in Microsoft Entra ID
- Cyber Kill Chain
- CIS Microsoft 365 Foundations Benchmark v7.0.0 - Page 269
Mito check, based on CIS Microsoft 365 Foundations Benchmark. Author: oed-metzb; contributors: Mynster9361. Open-source licences.
Open-source licences. CIS Benchmark material © Center for Internet Security, Inc.; CISA SCuBA baselines are public domain (CC0).
© 2026 Virtual Petals. Mito is a Virtual Petals service, hosted in Microsoft Azure UAE North.
