Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I have created a Get-DirectoryRoles cmdlet for the Recon module to retrieve all the entra ID (directory) roles and their associated members, a switch exist to request only builtin roles or customs roles. Cmdlet tested against test tenant working well.
Actually this is just a copy paste from the existing Get-SecurityGroups Cmdlet but adapted for the entra ID (directory) roles.
It's data that is better to visualize in azure hound, but it's nice to get a quick overview when performing recon with GraphRunner. Hope you like this initiative.
I'am planning on making a cmdlet that assign a role to a user, group or service principal for the Persistence module (tell me before I made it, but I think it could be usefull)