This is in our backlog, but votes and comments about how you would expect this to work are very helpful to our planning/designing the feature so please keep them coming.
Also, for some scenarios in this space Access Reviews (https://docs.microsoft.com/en-us/azure/active-directory/governance/manage-guest-access-with-access-reviews) can be a good way of removing users who no longer need access, including those who don’t have accounts anymore. (Thanks Shawn for pointing that out for everyone!)
An error occurred while saving the commentShawn Reagan commented
You could setup Access Reviews https://docs.microsoft.com/en-us/azure/active-directory/governance/manage-guest-access-with-access-reviews to poll the users periodically to see if they are still using an app\group. If the user has been removed in the 3rd party they won't get the email and can't respond. The policy would assume opt-out until the user responds otherwise. This would allow you to remove them and reclaim licenses for users no longer using your Azure AD.
Please add more comments to let us know what scenarios you’d complete using this feature, and upvote to help us understand its priority for you.
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