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 groupsAnonymous commented
Thank you for the update Philippe Signoret
Please can you provide a timeline on when the unsupported scenarios will be supported please?Anonymous commented
It's funny that you have a feedback category of "Role-based Access Control" yet the directory itself fails to provide the most basic role based control possible.
Why does Azure AD still not support Nested Groups? You provide the ability to add a group within a group but you cannot use them. This is incredibly frustrating that I must create groups and directly populate them with users and it must be even more frustrating for organisations which sync their onsite AD with AAD only to find that the groups can't be used but must be flattened.
Please can you provide a timeline of when you will support Nested Groups both for licensing and SaaS applications.
David PattieAnonymous supported this idea ·