Content reviewed: 12 October 2026

Start with the assignment source, exact SKU and processing status. A licence inherited from a group is managed through that group. Removing the user’s direct assignment may therefore have no effect. The Microsoft 365 admin centre documentation explains the portal workflow.

Direct and inherited assignments

A user can receive the same product directly and through one or more groups. Before removing a licence, identify every source that supplies it.

Removing a direct assignment leaves group assignments in place. Leaving one group may also have no visible effect if another group supplies the same product. A licence that remains available is not, by itself, evidence of a processing fault.

Record the relationship between the user, groups, products and enabled services. A group’s name may describe an old configuration rather than its current licences.

The exact SKU takes precedence over the group name

A group named M365-E5 may contain an older SKU or a different product. A capacity error can refer to that product rather than the subscription the administrator has checked.

If direct assignment succeeds while group assignment fails, compare the same user, SKU and enabled services. Different products or configurations do not form a comparable test. Successful direct assignment alone does not explain the group error.

Record the SKU ID alongside its readable name. E3 or E5 alone does not identify the product precisely enough.

A practical diagnosis

Common symptoms and checks
SymptomFirst checkNext evidence
Licence returns after removalAnother group or synchronisationMembership source and direct assignments
Available seats, but a capacity errorThe SKU named in the errorProducts actually assigned to the group
Cannot remove the user’s licenceAn inherited assignmentThe group supplying that product
Required service unavailableService plan configurationDependencies and conflicts
New member without a licenceAssignment statusUsage location, capacity and errors
Membership change has no effectAuthoritative source and change timeSynchronisation and licence processing

Use the table to narrow the investigation. Confirm the resulting user state; an estimated processing time is not a completion guarantee.

Read assignment states by source

Microsoft Graph exposes each assignment through licenseAssignmentStates. assignedByGroup contains the group ID; null identifies a direct assignment. skuId identifies the product and disabledPlans lists plans disabled in that assignment. One source’s configuration is not the user’s combined entitlement.

Microsoft Graph assignment states
StateWhat to check
`Active`Verify the SKU and source, then test the required service.
`ActiveWithError`The assignment also reports an error. Record it and check the affected services.
`Disabled`Establish why the assignment is inactive before adding a direct licence as a workaround.
`Error`Read `error` and compare it with the product and group configuration.

For successful assignments, the reference specifies error: null. Another source may supply the same SKU and keep the service available despite an error in the group under investigation. Successful sign-in does not prove that the new group assignment works.

Use the error code to choose the next check

Documented error values and diagnostic questions
CodeWhat to check before changing anything
`CountViolation`Does the exact SKU named in the error have available licences?
`MutuallyExclusiveViolation`Do assigned products contain conflicting services?
`DependencyViolation`Is the required plan dependency satisfied after the proposed change?
`ProhibitedInUsageLocationViolation`Is the service available for the user’s actual usage location?
`UniquenessViolation`Which collision does the detailed error identify? Check that attribute and the affected objects.
`Other`Record the exact state, context and time. This code alone does not identify the cause.

These are investigation questions, not universal repair commands. The admin centre documentation also names proxy address conflicts as a possible problem. UniquenessViolation alone does not identify which object or address to change. Acting without the detailed error could affect another account.

Portal limits: 20 groups, 20 users, 999 rows

In the Microsoft 365 admin centre, open Billing → Licenses → the product → Errors & issues, then inspect the user. You can assign licences to up to 20 groups at once. Reprocess attempts up to 20 users at once. Lists of successful and unsuccessful assignments display 999 users per loaded page; scroll to the bottom to load more.

The number 999 is therefore not a tenant-wide limit on licensed users. During a larger incident, the first visible list may not cover every affected account. Record the accounts before the fix and verify that all intended batches have been reprocessed afterwards.

Use Reprocess after correcting the confirmed cause. Retrying does not add licence capacity or repair nested membership. Compare the resulting assignments with the earlier evidence, rather than treating completion of the button action as proof of recovery.

For a tenant-wide inventory, use the Graph and PowerShell group licensing audit. It separates assignment sources in a report. Bulk licence removal is not a diagnostic step.

Check usage location

Some services have regional restrictions. For group licensing, users without a specific usage location inherit the tenant location. In a multinational organisation, set the user’s location during account creation.

Do not select a random country merely to make the assignment succeed. Usage location should reflect actual use and the organisation’s process. Onboarding needs an identified source for this information; the language of an email address is not a substitute.

If HR already holds this location, transfer it to the account under a defined rule and record changes. Check it again when an employee moves between countries.

Nested groups do not pass on licences

Group-based licensing does not support nested groups. Licences are assigned to users in the first level of the licensing group. Membership only in a nested group is insufficient.

Map the department group, licensing group and affected user. Distinguish direct membership from membership reached through another group. This checks the design before anyone changes licences.

If a temporary direct assignment is needed, record its owner and removal condition. An undocumented permanent workaround leaves onboarding and the actual licence state out of sync.

Service plans may have dependencies

A product contains several service plans, some of which may depend on another plan. For a dependency error, compare the exact plan IDs and configuration across every assignment source. Re-enabling a similarly named service is not a reliable diagnosis.

Two groups may enable different services or assign different products. Checking the product name alone will miss these differences.

After correcting the assignment, test the service the employee needs. An assigned licence does not establish that a mailbox is usable or an application has finished activation.

Change synchronised groups at their source

For a group synchronised from an on-premises environment, identify the authoritative membership source. A change on the wrong side may be rejected or overwritten.

Separate synchronisation from licence processing. Record when on-premises membership changed, when that membership appeared in the cloud and when the licence state changed.

After the fix, check the same account and assignment again. Those timestamps show which stage changed the result. Repeatedly adding and removing membership while processing is underway makes the evidence harder to interpret.

Moving between licensed groups

Add the user to the destination group and confirm the new assignment first. Then remove the user’s membership from the original group. Do not delete the original group: it supplies licences to other members too.

Check that the destination product covers the required applications, capacity and security features. Overlapping products during a pilot may conceal missing rights that only become visible after the old source is removed.

If services are incompatible, do not assume that overlapping assignments will work. Plan for the specific configuration and test the affected work. See the detailed guide to moving from E3 to Business Premium.

A new employee receives access to business systems

Model example: joining the finance team

In this hypothetical example, an employee joins Finance but does not receive the expected product. IT finds that Finance is nested inside the licensing group; the employee is not a first-level member of that licensing group.

The administrator corrects the membership design, checks capacity for the exact SKU and verifies the required services. The employee then tests email, documents and the accounting integration with their own account.

Closing the incident includes correcting onboarding. Manually adding one licence would leave the next new starter exposed to the same fault.

Frequently asked questions

Why does a licence remain after removal?

Another group or direct assignment may still supply the same SKU. Check every source. For a synchronised group, also check where membership is managed.

Do nested groups work?

No. Group licensing assigns licences to first-level users in the licensing group. Membership only in a nested group does not pass through for this purpose.

When should I use Reprocess?

After correcting the confirmed cause. The portal attempts up to 20 users at once. Check each intended assignment; a completed batch is not a service functionality test.

Does the same SKU from two groups consume two licences?

No. The number of sources supplying one product to a user is not the number of licences consumed. Assess different SKUs separately. To remove a product, identify every source that still supplies it.

Does Active mean everything works?

No. It describes the licence assignment. Also verify enabled services, actual availability and any overlap with another product.

Is 999 users a group licensing limit?

No. It is the size of a loaded list page in the portal. Scroll to the bottom to load further users.

Keep an incident record

Keep the user, group and SKU IDs, assignment state and error before and after the fix, membership source, change timestamps and service test results. If the fault persists, add the affected account count and exact observation time for escalation. A successful retry without an identified cause does not repair onboarding.