About this article: This article is reviewed against the cited sources. This is source research, not lab validation. Check the stated versions and your own requirements before making changes.
When a licence assigned to a group fails to reach some of its members, nothing complains at the moment you assign it. Microsoft's page explains that group-based licensing "records the failure on the user object and surfaces it later in the admin portal". Open Billing > Licenses in the Microsoft 365 admin center, select the product, and read the Errors & issues tab. Select a user to inspect what type of error they encountered. Microsoft's problem table names the causes, such as not enough licences, conflicting service plans or other products depending on a licence. Fix that cause, then reprocess.
Do not remove a user from the group that licenses them before the destination group has licensed them. The page says that doing so leaves the user unlicensed until processing finishes.
What the error means
Group-based licensing applies licences to every member of a security group, mail-enabled group or Microsoft 365 group. The licensing service tries to apply each product assigned to the group to each member. When it cannot, for one of the reasons below, the user stays without that licence and the reason is recorded.
Some facts on Microsoft's page shape what you can expect:
- You must be at least a Groups Administrator, License Administrator or User Administrator to assign licences.
- Group-based licensing "doesn't currently support nested groups (groups that contain other groups)". If you assign a licence to a nested group, only users in the first-level group are assigned licences.
- A user needs a usage location before a licence can be assigned. For group-based licensing, users without a specific location inherit the location of the tenant.
- When you assign or modify licences for a large group, such as 100,000 users, processing can take a long time under load.
- In the admin center you can assign licences to a maximum of 20 groups at a time. Reprocess handles a maximum of 20 users at a time. Lists of users who were or were not assigned licences show 999 at a time.
Likely causes
| Cause | What you see | How to confirm |
|---|---|---|
| Not enough licenses | One of the products assigned to the group has too few available | Errors & issues tab names the product; compare licences bought with licences assigned |
| Conflicting service plans | A service plan in one product conflicts with one already assigned through another, such as Exchange Online Plan 1 and Plan 2 | The user's licences: a direct Office 365 E1 plus a group E3 |
| Other products depend on this license | A licence cannot be removed because another product depends on it | The user has a dependent product, such as Audio Conferencing, directly assigned |
| Usage location isn't allowed | The user's location is missing or unsupported | The Usage location property on the user |
| Duplicate proxy addresses | Exchange Online licensing fails when two users share a proxy address | The proxyAddresses values on the two users |
| Mail and ProxyAddresses attribute changes | A licence assignment triggers recalculation of mail and proxyAddresses | Changes to those attributes after assignment. Fix, per the page: check how proxy addresses are populated and correct the underlying source of the change |
| LicenseAssignmentAttributeConcurrencyException in audit logs | Several groups tried to assign the same licence at once | The audit log entry; the page says no action is needed because processing retries |
| More than one product assigned to a group | One product fails and the others in the group may not be assigned either | Inspect the affected users to find the product that failed |
| Licensed group deleted | Dependency or proxy address problems during cleanup | Whether a user holds a direct licence that depends on a plan the group provided |
| Product that needs a prerequisite or add-on | An add-on assigned alone, such as Workplace Analytics without Exchange Online Plan 1 or 2 | The group's products: prerequisite and add-on must be in the same group |
Prove the cause before changing anything
All of these only read.
- In the Microsoft 365 admin center, go to Billing > Licenses and select the product. Select the Errors & issues tab, which lists users with problems, and select a user to inspect the error type.
- To find groups with errors, go to Billing > Licenses > Overview in the Microsoft Entra admin center. If any groups have licensing errors, an information box appears. Select it, then open each group for details.
- To find affected users in one group, go to Groups in the Entra admin center, select the group and select the notification that lists users in an error state.
- Check the user's Usage location and licences, including any assigned directly.
- Read the number of available licences for the product against the number of users in the group.
Example (illustrative): Contoso (contoso.com.au) holds 48 Office 365 E3 licences and 45 are in use. The group Staff-E3 has the E3 licence. Six new starters are added to the group. Only three licences are left, because 48 minus 45 is 3, so three of the six show Not enough licenses on the Errors & issues tab. Contoso buys more licences or frees unused ones, then reprocesses the three users.
Fix
Match the fix to the cause the tab names.
- Not enough licences: Save first: record how many licences exist and who holds them. Risk: buying licences commits spending, and removing licences from others removes their access. Confirm with whoever owns the subscription. Buy more licences, remove unused direct assignments, or free licences from other groups or users. To undo a removal: assign the licence back.
- Conflicting service plans: Save first: write down the user's current licences and the on/off state of each service in the product (Assign licenses > Turn apps and services on or off). Disruptive step: each option below changes what someone can use. Disable one conflicting plan, remove the redundant direct licence, or adjust the group's assignment. To undo it: turn the plan back on, or assign the direct licence again.
- Other products depend on this licence: Save first: record the user's licences. Disruptive step: removing the dependent product removes that service from the user. Remove or reassign the dependent product before removing the prerequisite. To undo it: assign the dependent product again.
- Usage location: Save first: record the current usage location value. Risk: changing the location below can affect which services a user may use. Set the correct location on the user, remove users in unsupported locations from the licensed group, and populate location when users are created. To undo it: set the old value.
- Duplicate proxy addresses: Save first: record the
proxyAddressesvalues of both users. Risk: removing an address stops mail to that address. Correct the duplicate on one of the two users, then reprocess. To undo it: put the address back on the user it came from; the duplicate, and the licensing error, then return. - Concurrency exception: no action; the page says processing is retried and resolves the issue automatically.
- Prerequisite and add-on: Save first: record each group's members and assigned products. Risk: moving a product between groups changes who holds it, and uses licences from the pool. Put the prerequisite and the add-on in the same group. The page's example is Office 365 E3 with only Exchange Online Plan 2 enabled together with Microsoft Workplace Analytics. To undo it: move the product back to its original group.
Save first: record the product's available licence count and the selected users' current licences. Risk: Reprocess applies the group's licences to the users you select, which uses licences from the pool. After fixing, reprocess. In Billing > Licenses, select the product, then Errors & issues, correct the underlying issue, select the affected group or user, and choose Reprocess. Reprocess handles at most 20 users at a time, so repeat for larger lists. To undo it: Microsoft's page documents no undo for Reprocess, which only applies licences the group already assigns. To take the licence from one user, remove that user from the licensing group (the page says a user removed from the group is left unlicensed until processing finishes). Do not use Unassign on the group for this: it removes the licence from every member.
Risk: moving a user between licensed groups. Save first: record the user's current licences and their group memberships. Add them to the destination group first, confirm the new licence on the user's Licenses page, then remove them from the original group. If you remove them from the source first, the user is unlicensed until processing finishes. Back-out: add the user back to the original group and remove them from the destination.
Disruptive step: unassigning a licence from a group. Members lose that licence. In Billing > Licenses, select the product, find the group, use the three dots, select Unassign and confirm. Save first: record which groups and products are assigned, and which services were switched off under Turn apps and services on or off for each product. Back-out: assign the licence to the group again with Assign licenses, then switch the recorded services off again.
Disruptive step: a licensed group must not be deleted until you have recorded its state. The page does not give a deletion procedure. Its problem table says that before deleting a group, all licenses assigned to it must be removed, and that where a user's direct licence depends on a plan the group provided, the inherited licence might be converted to a direct assignment. Before any deletion, record the group's members and its assigned products, remove its licences as above (this strips the licence from every member), and check members for direct licences that depend on a plan the group provided. The page gives no way to undo a deletion, so there is no back-out for the group itself.
Confirm the fix
- Reopen the product's Errors & issues tab; the user should no longer appear after reprocessing.
- Open the user's Licenses page and confirm the licence is shown as assigned.
- Ask the user to sign out and in again and check the service they needed, such as mail or Teams.
- If you used the Microsoft Graph PowerShell SDK, the page names the
Set-MgGroupLicensecmdlet for assigning or unassigning licences to groups. Read its documentation before use.
What to watch afterwards
- The licence count for each product, so new group members do not exceed it.
- Groups that contain other groups. Nested membership is not supported for licence assignment.
- Users with both a direct licence and a group licence for overlapping plans.
- The Errors & issues tab after each batch of joiners.
Read next
Related articles you may want next.
- TroubleshootingCan't open a leaver's mailbox after removing their Microsoft 365 licence: the 30-day window and what to do firstMailbox gone after you removed a Microsoft 365 licence? You have 30 days to reassign one. Learn the hold case, shared mailbox and inactive mailbox options.Read article
- HostingLicences and subscriptions that must move when you leave a hostCheck which software licences and subscriptions can move when hosting changes. Record ownership, licensing terms, replacement arrangements and responsibilities before the existing service ends.Read article
- TroubleshootingTeams sign-in error 0xCAA20004, 0xCAA70004 or 0xCAA82EE7: what the code means and what to checkTeams will not sign in with 0xCAA82EE7, 0xCAA20004 or 0xCAA70004? Run the sign-in diagnostic, check network and Conditional Access, then reinstall safely.Read article
Risks and limits
- These commands have not been run or lab-tested.
- The page names
Set-MgGroupLicensebut does not give its parameters, so none are shown. - Processing time varies with tenant size and load, and the page does not give a figure.
- Licence terms, prices and product names change. Check the current Microsoft page and your agreement before buying or removing licences.
Sources
- Assign or unassign licenses to a group in the Microsoft 365 admin center — Microsoft Learn, page dated 2026-10-15, accessed 20 November 2026
This article was originally published on .