Improved Domain Info Scripts: Now with RBAC Details and Error Fix #51
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
remove error for not public blob
Improve user enumeration functionality by adding user roles and group memberships.
add comments
Identify RBAC assignments for users and groups, along with their corresponding resources
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Hi,
I've added new fields to the scripts Get-AzDomainInfo.ps1 and Get-AzureADDomainInfo.ps1.
I often need this information during penetration testing, so I implemented these features to streamline the process. I also fixed a small error that occurred when using Invoke-WebRequest to check if the blob is public accessible.