User1 has the Contributor role at the scope of subscription Sub1, which contains resource group RG1. User1 must be able to grant colleagues Azure role assignments for the resources in RG1, but must not be able to manage access anywhere else in Sub1 or change governance settings such as policy assignments or locks. You can create one additional role assignment for User1. Which assignment follows the principle of least privilege?
Show answer and explanation
Correct answer: A · Role Based Access Control Administrator at the RG1 scope
Contributor excludes Microsoft.Authorization write and delete operations, so User1 is missing only the right to create and remove role assignments. Role Based Access Control Administrator adds exactly roleAssignments/write and roleAssignments/delete, and does not allow access to be managed in other ways, such as Azure Policy. Assigned at RG1, it applies only to that resource group, while the subscription-level Contributor role continues to cover resource management. For tighter delegation, you can add a condition that limits which roles User1 can assign.
Why the other choices do not fit
- User Access Administrator grants Microsoft.Authorization/*. At RG1, that also includes policy assignments, locks, and custom role definitions, which is more than role assignment management requires.
- Owner at RG1 allows role assignments, but it grants every other Microsoft.Authorization operation as well. User1 already manages resources through Contributor, so Owner adds far more than needed.
- The role is appropriate, but the scope is not. At Sub1, User1 could assign roles on every resource group in the subscription, breaking the requirement to stay within RG1.
