We’re currently evaluating an option that will provide the functionality offered by nested groups, but removes the complexity nested groups adds. We appreciate your patience on this ask and want to ensure we deliver a solution that benefits all of our customers. Below are use cases that we’d like for you to stack rank, with #1 being priority for you. We thank you for the continued comments and feedback.
Use case A: nested group in a cloud security group inherits apps assignment
Use case B: nested group in a cloud security group inherits license assignment
Use case C: nesting groups under Office 365 groups
416 votes49 comments · Azure Key Vault » Managing application secrets · Flag idea as inappropriate… · Admin →
In public preview.
An error occurred while saving the commentAnonymous commented
I would call this the single biggest gap in the ability to put together an effective enterprise cloud governance strategy. Allowing ANYONE in your company to do this with no way to disable is completely inappropriate. You allow similar functionality in other areas (Azure AD app registrations, Azure Devops organizations, o365 groups, etc), how does MS not see allowing this major capability as a problem. I get it that you want people to play around with Azure, but as company cloud administrations, it is essential that we be able to secure our tenants!