Group-based Licensing for Nested Groups
Nested groups have been around for a VERY long time. It is ridiculous that group-based licensing doesn't support nested groups. Please add support for nested groups ASAP!
This function is still not available and would allow easier dynamic license assignment. Add some loop statements in your backend code to exclude users that show up in multiple groups. This function would speed up license activation and usage.
Yes, this would make things easier.
Yes that would be great.
This would be very useful. I am perplexed why this is not yet implemented.
This is a long overdue option.
Cliff Davis commented
Please implement this very mature technology.
Ensuring all our users are covered with licenses for Intune App Protection, is proving challenging, without being able to use nested groups.
Bavo Bostoen commented
What is the status for this request.
As others mentioned, i find it is (more than) needed.
Robert Rasmussen commented
I can totally respect you "trying to decide the best approach to meet diverse business needs," but how long must we all wait for you to make a decision and enact a solution? As someone else has mentioned, we too have implemented role-based access control within our AD structure. Without the ability to support nested groups, I would think group-based licensing currently is of limited benefit for most organizations. It's impractical to manage licensing on a per-user level. Correcting this limitation should be made a priority.
I work for IT in a large University, and when my current configuration wasn't working, I went to google, and stumbled across this.
I cannot believe this is not already a supported feature.
The utter dismay I felt, when I became away that this was not possible...
Our entire AD heirachy functions on nested groups for dynamic flow-on updates as Staff/Students come and go.
It seemed perfectly reasonable to expect when a new student enrols into a class, they could get a license based on their new membership into the group.
I cannot believe we have to add users into these licensing groups manually, and also remove them manually when licenses need to be reassigned. (or come up with some work-around scripts to manipulate the process)
This absolutely needs to be a priority.
We are aware of this feature request. Though we don't have a timeline yet, as processing transitive memberships has latency challenges and this will also add to the complexity to understand who has access to which license through which group, we are trying to decide the best approach to meet diverse business needs.
Yes, we need this. We are hybrid and want to add licenses based on roles. We have roles for finance, hr, front line in our AD. Each subscription we own -- ranging from Office E1 to Microsoft E5 -- has a default set of service plans activated/deactivated. So we basically have access security groups for the single subscription (A-LIC_OfficeE1, A-LIC_OfficeE3, A-LIC_MicrosoftE5) and role security groups (R_Finance, R_HR, R_FLW). The role groups should members of the license groups and it should work. -- The reason we do NOT want to add the group-licensing to the role groups is that we lack a lot of flexibility. If you must add e.g. an E1 license to a single user account that does not belong to a defined role, you must to this individually instead of simply adding him to the A-LIC_OfficeE1 group. And if you add the users to the license access group, then you must manage two security groups, which is double the work.
please as we are having to automate this feature for ourselves.
Chris Parr commented
Really need this!
this would be very nice to have!
Need this too!
Hugues Vandenbroucke commented
Any news about this? This is quite critical for many organizations as managing users through direct group assignment is not compatible with RBAC and role-based assignments. Nested groups are really needed for companies of more than 10 people, which are a HUGE majority.
Cerise, Tracy commented
In a multi-departmental entity such as a major University, keeping track of who purchased and should be granted a one-off license, such as Visio or Project Online Professional, becomes outright impossible. Having the abillity to use nested groups would allow for a parent group, say for Visio, to contain separate departmental groups that can be managed separately for each department's individual for provisioning and deprovisioning Visio licenses. This makes it easier to know what department purchased which licenses, especially at renewal time.It is not a perfect solution, but it does allow a way to keep better track of these licenses. Group expansion from nested groups would be extremely helpful for this situation