Group-based licensing is the Entra ID capability that assigns Microsoft 365 licenses to a group rather than to individual users. Every direct user member inherits the license automatically, and losing membership removes it. Nested groups are not supported: per Microsoft documentation, members of groups nested inside the licensed group do not receive the license.
How it behaves#
An assignment on a group names a SKU and, optionally, disabled service plans within it. Entra ID processes membership changes asynchronously, assigning and removing licenses as users enter and leave the group's direct membership.
When several groups assign the same SKU to one user, the user consumes a single seat and the enabled service plans are merged: a plan is on if any assignment enables it.
The blind spots#
The mechanism is sound; the visibility around it is not.
- The nesting trap: nesting a group under a licensed parent looks like it licenses those members, and per Microsoft rules it does not, so the population stays silently unlicensed.
- Overlaps hide dependencies: removing one granting group may change nothing, or everything.
- Errors are per user: assignment failures sit on user objects, easy to miss at group level.
- Nesting decisions have licensing consequences nobody sees at the moment of nesting.
VisualizerEngine
Group licensing in VisualizerEngine
License analytics follow the hierarchy: inheritance mapping shows each license's exact path, cost analysis shows spend by SKU and by group, conflicts and duplicates are tracked per user, and removal impact analysis previews any unassignment before it happens.