Guest users should be reviewed on a regular schedule
This check looks at whether external guest accounts in your Microsoft Entra directory get a recurring review so that people who no longer need access are removed. The safe setting is a regular review, for example a recurring access review scoped to guest users, with a clear owner for the result.
Why it matters
Guests are usually invited for one project and then forgotten. Microsoft's guidance on external identities points out that many collaborations have no clear end date, so it is not obvious when someone stops needing access, and that employees can end up granting access to external accounts that should have been removed long ago.
Each stale guest is an identity outside your control that can still be a member of groups, Teams or applications. A recurring review keeps the list short and puts the decision with the people who know the resource best, such as group owners.
Source: Microsoft Learn, Use Microsoft Entra ID Governance to review and remove external users who no longer have resource access.
How to check it yourself
In the Microsoft Entra admin center open Entra ID > Users and filter on user type Guest to see how many there are and when they were created. Then open ID Governance > Access Reviews and look for a recurring review whose scope is Guest users only.
A read-only listing of guests with Microsoft Graph PowerShell:
Connect-MgGraph -Scopes "User.Read.All"
Get-MgUser -All -Filter "userType eq 'Guest'" `
-Property DisplayName,UserPrincipalName,CreatedDateTime,ExternalUserState |
Select-Object DisplayName,UserPrincipalName,CreatedDateTime,ExternalUserStateGuests whose invitation is still pending long after creation are a good first cleanup candidate.
How to fix it
Create a recurring access review for guests. Access reviews have their own licence requirement, so check Microsoft's licensing page before you start. Steps in the portal:
- Sign in to the Microsoft Entra admin center as at least an Identity Governance Administrator.
- Browse to ID Governance > Access Reviews and select New access review.
- Choose Teams + Groups, pick the groups that contain guests, and set the scope to Guest users only.
- Pick reviewers (group owners work well), set a recurrence such as every quarter, and turn on Require reason on approval.
- Decide what happens to denied or unanswered guests. Start with a setting that only removes access, and consider the option that blocks sign-in for 30 days and then deletes the account only after you trust the process.
Microsoft also publishes a sample PowerShell script on GitHub that lists guests without group membership, which helps you build the first review group. ConfigCobra never makes these changes for you: it reports the finding and suggests the steps.
What changes when you fix it
Group owners or the guests themselves receive review requests by email and have to answer within the review period. Guests who are denied, or who do not answer when the review is set to act on non-responses, lose access to the reviewed groups and applications.
If you choose the block-then-delete option, the guest cannot sign in for 30 days and the account is then removed from the directory, which also removes everything that depended on that identity. Run the first review in a mode that only recommends, so owners can correct mistakes before anyone loses access.
Included in
| Benchmark | CIS ID | Profile |
|---|---|---|
| CIS Microsoft Azure Foundations v6.0.0 | 5.3.2 | Level 1 |
More checks in Identity Services
- Ensure that Azure Admin Accounts Are Not Used for Daily OperationsCIS 5.3.1
- Ensure That Use of the 'User Access Administrator' Role is RestrictedCIS 5.3.3
- Ensure that All 'Privileged' Role Assignments are Periodically ReviewedCIS 5.3.4
- Ensure Disabled User Accounts do not Have Read, Write, or Owner PermissionsCIS 5.3.5
Check this on your Microsoft Azure
ConfigCobra runs this check with every other control of the CIS Microsoft Azure Benchmarks, read-only.