Question 100
Two Azure subscriptions belong to management group mg-sales. The same internal audit service must read resource settings in both subscriptions and in future subscriptions added to mg-sales, but cannot modify anything. Where should Reader be assigned?
Explanation
Correct Answer
Azure RBAC assignments at a management-group scope are inherited by its descendant subscriptions and resource scopes. Assigning Reader to the audit principal on mg-sales gives consistent read-only access to both existing subscriptions and subsequent subscriptions moved under that hierarchy. It does not grant general write privileges. This placement is justified because the requirement explicitly covers the full hierarchy and future descendants; otherwise, separate subscription-level grants would usually be less expansive.
Incorrect Answers
Directory Readers concerns Microsoft Entra identity objects, not the Azure resource configurations in the two subscriptions. It also does not define an RBAC assignment scope across resource management groups. The audit service needs Azure Resource Manager Reader at the mg-sales management-group scope to inspect the specified resources.
A Reader grant at a single subscription does not cross into a sibling subscription. It would miss both the other current subscription and new subscriptions added to the management group. The audit service has a justified organization-unit-wide requirement, so mg-sales is the appropriate common ancestor scope for one inherited assignment.
Tenant-root management-group Reader would inherit into far more subscriptions than those owned by sales. It could expose unrelated business units and fail the explicit boundary at mg-sales. Assigning at the nearest management group containing the intended subscriptions satisfies future inheritance without extending the audit service across the whole tenant.