Changing a Group License
Changes sync automatically across both portals.
Common Licensing Error States
| Problem | Cause | Resolution | PowerShell Code/Message |
|---|---|---|---|
| Not enough licenses | Insufficient available licenses. | Purchase or free up licenses. | CountViolation |
| Conflicting service plans | Incompatible licenses (e.g., E1 + E3). | Disable overlapping plans. | MutuallyExclusiveViolation |
| Dependency violation | Removing a license that another depends on. | Reassign prerequisite plan. | DependencyViolation |
| Usage location not allowed | Unsupported country/service. | Update user’s Usage Location property. | ProhibitedInUsageLocationViolation |
| Duplicate proxy addresses | Two users share the same Exchange proxy. | Correct duplicate addresses, reprocess. | — |
Force License Processing
Migrating to Group-Based Licensing
Goal: Replace per-user license scripts with Entra’s automated group licensing.
Migration Steps:
Example: Contoso migrates 1,000 users from PowerShell-based E3 assignments to Entra group-based licensing using a single All Users group.