Currently I’m managing a tenant with 60+ subscriptions in Azure.
We operate in the following way:
- Separate cloud only admin
- No standing privileges on admin accounts
- No direct assignments on users, only security groups (exception for break glass accounts)
Currently we use Role Assignable Groups in combination with PIM, so if Admin A needs to get Owner permission on a subscription, he can PIM (because of eligible assignment) to a security group that is actively assigned to the Owner role on that subscription.
At the moment we’re rapidly approaching the limit of 500 role assignable groups within a tenant. The main goal of having these role assignable is to limit who can modify these security groups (such as group administrators).
We tried using RMAU’s to secure these groups, we got it working with PIM but only with active assignments.
My main question is, how should we continue?
I want to limit which security principles can modify security groups used in Azure in some way.
Some possible options I’m thinking of:
- RMAU in combination with access packages
- Switch to RMAU and permanent assignments in the groups but eligible in Azure