🪲 Wrong Emergency Access Group detected with too many users produces a loop

[JeffTurner69]

Describe the bug

Wrong Emergency Access Group detected with too many users (above 3k) produces a loop. The group is called constantly during test discovery.

Call that is performed thousands of time until the devops pipeline times out:
2025-09-29T15:27:41.3795089Z �[33;1mVERBOSE: Using graph cache: https://graph.microsoft.com/v1.0/groups//members?$select=id%2cuserPrincipalName%2cuserType&$skiptoken=

Is there any way I can skip the emergency access user/group check? I tried by removing test MT.1005.

To Reproduce

Steps to reproduce the behavior:

1. Run Maester where a emergency group is detected with above 3500 users.
2. Loop will start.

Expected behavior

Maester should not end up in a loop or it should be possible to manually configure the emergency accounts/groups

Debug Output

Call that is performed thousands of time until the devops pipeline times out:
2025-09-29T15:27:41.3795089Z �[33;1mVERBOSE: Using graph cache: https://graph.microsoft.com/v1.0/groups//members?$select=id%2cuserPrincipalName%2cuserType&$skiptoken=

Module Version

Issue exists in Maester 1.3 and 1.3.37-preview.

Environment Data

Name Value

---

PSVersion 5.1.22621.5909
PSEdition Desktop
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
BuildVersion 10.0.22621.5909
CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1

Screenshots

N/A

Additional context

N/A

[SamErde]

@JeffTurner69, can you please retest to see if this is fixed as of preview release v1.3.98?