Copyright (c) 2026 MindMesh Academy. All rights reserved. This content is proprietary and may not be reproduced or distributed without permission.

2.1.1.5. Manage Licenses in Microsoft Entra ID

2.1.1.5. Manage Licenses in Microsoft Entra ID

💡 First Principle: A license is an entitlement attached to a user object, not to a mailbox or a device. Because the entitlement lives on the identity, the scalable way to manage it is the same way you manage access: attach it to a group and let membership decide who holds it.

Scenario: Your company is onboarding 300 sales staff across the United States and Canada. Each needs Microsoft 365 E3, but the sales team must not receive Microsoft Bookings. New hires join every week, and leavers must stop consuming a license without anyone remembering to remove it.

What It Is: Users can't use Microsoft 365 services until their account has a license from a licensing plan (a SKU, such as SPE_E3). Each SKU bundles several service plans (Exchange Online, SharePoint, Bookings and so on) that you can turn on or off individually. You assign a license in one of two ways:

  • Direct assignment: the license is applied to one user. Errors (for example, no licenses left) appear immediately. See Assign or unassign licenses for users.
  • Group-based licensing: the license is applied to a security group, mail-enabled group or Microsoft 365 group. Users who join the group are assigned the license automatically, and when they leave the group Microsoft Entra ID removes the assignment (users, groups and licensing). Combined with a dynamic membership rule such as department -eq "Sales", licensing follows HR data with no manual step.

Where You Do It: Microsoft now manages user and group license assignment in the Microsoft 365 admin center (Billing > Licenses, select a product, Assign licenses), and the Microsoft Entra licensing page points there. The Microsoft Entra admin center still surfaces problems: Billing > Licenses > Overview lists groups with licensing errors, and a licensed group shows a notification when members are in an error state. You need at least the License Administrator, User Administrator or (for groups) Groups Administrator role.

The Usage Location Requirement: Some Microsoft services aren't available in every country or region, so a license can only be assigned to a user whose UsageLocation is set to a valid ISO 3166-1 alpha-2 code (US, CA, FR). The two assignment paths behave differently when it's missing:

SituationDirect assignmentGroup-based assignment
UsageLocation emptyAssignment fails until you set itUser inherits the tenant's location
Location where a service isn't offeredReported as an invalid usage location"Usage location isn't allowed" error on the user

Accounts synchronized from on-premises AD DS don't have a location by default, so set it as part of your provisioning flow rather than relying on the tenant default.

Common Group-Based Licensing Errors: Group-based licensing processes in the background, records failures on the user object and surfaces them later (error reference):

  • Not enough licenses: buy more, or free licenses from unused direct assignments.
  • Conflicting service plans: for example a user holds Office 365 E1 directly and receives Office 365 E3 from a group, and Exchange Online Plan 1 conflicts with Plan 2. Disable one plan or remove the redundant direct license.
  • Other products depend on this license: a dependent add-on blocks removal of its prerequisite.
  • Usage location isn't allowed and duplicate proxy addresses (Exchange Online). After you fix the cause, select Reprocess on the product's Errors & issues tab.
Behaviour Worth Remembering:
  • Group-based licensing doesn't support nested groups. If you license a group that contains another group, only users in the first-level group are licensed.
  • To move a user between two licensed groups without losing service, add them to the destination group first, confirm the license, then remove them from the source group.
  • Service plans are toggled per assignment (Turn apps and services on or off), so the Sales group can carry E3 with Bookings disabled while another group carries full E3.
Practical Implementation: Licensing with Microsoft Graph PowerShell
Connect-MgGraph -Scopes User.ReadWrite.All, Organization.Read.All, LicenseAssignment.ReadWrite.All

# Usage location must be set before a direct assignment
Update-MgUser -UserId "dana@contoso.com" -UsageLocation CA

# Find the SKU and the service plan to switch off
$e3Sku = Get-MgSubscribedSku -All | Where SkuPartNumber -eq 'SPE_E3'
$disabledPlans = $e3Sku.ServicePlans |
    Where ServicePlanName -in ("MICROSOFTBOOKINGS") |
    Select -ExpandProperty ServicePlanId

# Direct assignment to one user
Set-MgUserLicense -UserId "dana@contoso.com" -AddLicenses @{SkuId = $e3Sku.SkuId; DisabledPlans = $disabledPlans} -RemoveLicenses @()

# Group-based assignment (requires LicenseAssignment.ReadWrite.All or Group.ReadWrite.All)
Set-MgGroupLicense -GroupId $salesGroupId -AddLicenses @{SkuId = $e3Sku.SkuId; DisabledPlans = $disabledPlans} -RemoveLicenses @()
Visual: Direct vs. Group-Based License Flow

⚠️ Common Pitfall: Licensing a parent group and expecting members of its nested child groups to be licensed. Group-based licensing applies only to first-level members, so those users silently stay unlicensed.

⚠️ Exam Trap: Usage location is the property that blocks a direct assignment. Candidates confuse it with Office location or Country, which are contact attributes with no effect on licensing. Also remember that a group assignment doesn't fail on a missing usage location; it falls back to the tenant's location, which may be the wrong country for that user.

Key Trade-Offs:
  • Direct vs. Group-Based: Direct assignment gives instant, visible results for a one-off user. Group-based assignment removes the joiner/leaver toil but moves errors into a background queue you must monitor.
  • One SKU, Many Groups vs. Many Disabled Plans: Per-group service-plan settings give fine control, but every variation is another group whose configuration you must keep correct.

Reflection Question: If a user holds the same product directly and through a group, which assignment would you remove first when migrating to group-based licensing, and how would you check that no service plan conflicts remain afterwards?

See how it connects
Alvin Varughese
Written byAlvin Varughese
Founder•22 professional certifications earned