feat(query): implemented query that checks if the use of user access administrator is not restricted for terraform/azure #7842
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.








Reason for Proposed Changes
azurerm_role_assignementis restricting the use ofUser Access Administratorrole through its name or id.Proposed Changes
get_resthat check's the two possibilities of defining theUser Access Administratorrole, by using the fieldrole_definition_nameand defining it toUser Access Administratoror its respective ID (18d7d88d-d35e-4fb5-a5c3-7773c20a72d9)."Either role_definition_id or role_definition_name must be set."so, I did not covered the case when both are defined.scopefield should also be taken into account. Following this guidance, the query only covers the highest permission levels - the tenant root (/) and management group (/providers/Microsoft.Management/managementGroups/<mg>). According to the Microsoft RBAC scope documentation, assigning the User Access Administratir role at these level grants permissions over all resouces in the tenant.I submit this contribution under the Apache-2.0 license.