T The Triage ManualTechnical Guides for IT Emergencies
P3 · Microsoft 365 & Collaboration

Microsoft 365 Licence Assignment and Service Plan Enablement Failures — Conflicts, Dependencies, and Provisioning Errors

Microsoft 365 licence assignment failures occur when licences cannot be assigned to users or when specific service plans within a licence fail to provision correctly. Common causes include conflicting licence assignments, missing UsageLocation attributes, exhausted licence pools, service plan dependencies not met, or group-based licensing conflicts. Resolution involves auditing licence state via the M365 Admin Centre or PowerShell, removing conflicting assignments, ensuring prerequisites are met, and reassigning with correct service plan configuration.

Indicators

Likely causes

Diagnostic steps

  1. Check the user's current licence assignment state in the Microsoft 365 Admin Centre: Users > Active Users > select user > Licences and Apps tab. Identify which licences are assigned and which service plans show as disabled or in error state.
    Identifies which licences are assigned, which service plans are enabled or disabled, and whether any plans show an error provisioning state.
  2. Verify available licence counts: Navigate to Billing > Licences in the Microsoft 365 Admin Centre and check the target SKU has unassigned units remaining.
    Rules out licence exhaustion as the cause of assignment failure.
  3. Verify the user's UsageLocation attribute: In the Admin Centre go to Users > Active Users > select user > Account tab > Settings > Usage location. Alternatively, run: Get-MgUser -UserId user@domain.com -Property UsageLocation | Select UsageLocation
    A missing UsageLocation prevents licence assignment entirely; this must be set to the appropriate country code before proceeding.
  4. Check for group-based licensing errors: Navigate to Azure Active Directory / Entra ID > Groups > select the relevant group > Licences, and review the list of users with assignment errors.
    Identifies whether the failure is driven by group-based licensing conflicts rather than direct assignment issues, and surfaces which users are affected.
  5. Review specific error details in Entra ID: Users > select user > Licences, noting the exact error message or conflict description shown for the problematic licence entry.
    Pinpoints the exact service plan or SKU causing the conflict, enabling targeted remediation rather than blanket reassignment.
  6. Query licence state via PowerShell for detailed diagnostics: Get-MgUserLicenseDetail -UserId user@domain.com | Select-Object -ExpandProperty ServicePlans | Where-Object {$_.ProvisioningStatus -ne 'Success'}
    Programmatically identifies all service plans not in 'Success' state for scripted bulk analysis.

Resolution path

Prevention

Tools

References

Microsoft 365licensingservice enablementAzure ADEntra IDgroup-based licensingExchange OnlineTeamsSharePointuser provisioningSaaSUsageLocationlicence conflict