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 groupsMichael commented
I am strongly against this. Org trees are for hierarchy, groups are for roles. The minor convenience gained with this change would not in my opinion be worth the additional complexity of querying membership. For janky setups, dynamic groups provide a workaround.