Microsoft 365 features that help users manage their subscriptions, account settings, and billing information.
The most likely cause is that the existing group still has unresolved licensing state for some members, even if the tenant appears to have enough licenses overall.
Check the existing group assignment from the Microsoft 365 admin center:
- Go to Billing > Licenses.
- Select the affected product.
- Open the Errors & issues tab.
- Select an affected user to see the exact failure.
Common supported causes for group-based licensing failures include:
- No available licenses for the selected product
- Conflicting services or license plans
- Invalid usage location
- Missing dependencies
- Proxy address issues
Specific things to verify in this scenario:
- Usage location Group-based licensing requires a valid user location. Users without a specific location can inherit the tenant location, but if users are in multiple locations, each user should have the correct location set.
- License availability for that exact product The Licenses page can show totals aggregated across subscriptions with the same product name. That can differ from what appears on Your products. Verify that the exact subscription used by the group assignment still has capacity.
- Existing assignment errors on the group If some users in the group could not be assigned licenses, open their details from Errors & issues, resolve the underlying problem, and then select Reprocess. Reprocessing can handle up to 20 users at a time.
- Group structure Group-based licensing does not support nested groups. Only users in the first-level group receive licenses.
- Large-group processing delay If the group is very large, license changes can take longer to process.
The fact that a new group with one user works suggests the product and tenant licensing are generally functional, and the problem is more likely tied to the existing group’s members or assignment state rather than a tenant-wide licensing failure.
References: