Apologies for the delay in updating this item. We are aware of the challenges around this limit and are actively working to be able to raise it; however, we don’t have an ETA yet.
We will update this item as we get more clarity on the timeline. Stay tuned and thank you for the understanding.
An error occurred while saving the commentJean-Marc Brissette commented
With the limit for RBAC Role assignment at 2000, the number of role per resource groups can be attained relatively quickly with larger deployments. I was thinking of 2 ways to bypass the issue, either allow us to increase the limit to Role Assignments in a subscriptions or allow us to do resource group nesting. That way we could apply the roles to the main resource group to use inheritance instead of using multiple role assignments for all the similar resources.
The Azure Resource Manager team is actively investigating the scenarios around renaming resource groups. To help us better understand the use-cases and to determine which implementations may be viable to address the problem, we would appreciate if you could fill out this 3-minute survey:
454 votesunplanned · 53 comments · Azure portal » Resource management · Flag idea as inappropriate… · Admin →