6.1 Managing & Monitoring Microsoft 365 Licenses

Managing & Monitoring Microsoft 365 Licenses

Quick Answer: A Microsoft 365 license SKU is a bundle of individual service plans. You assign SKUs to users (directly) or to groups (so every member inherits them). License assignment states are Assigned, Pending, or Error; errors are caused by conflicts or insufficient licenses. A user must have a usage location before any license can be assigned.

Microsoft 365 licensing is the gatekeeper for every workload an administrator provisions. Get it wrong and users lose mailboxes, Teams, or compliance features the day they are needed. The MS-102 exam tests the mechanics of license acquisition, assignment, group-based inheritance, and error remediation.

License Acquisition & the Billing Surface

Licenses are acquired by purchasing subscriptions (product SKUs) through the Microsoft 365 admin center under Billing → Your products and Billing → License (also labeled Billing → Licenses in newer admin center builds). Each subscription carries a quantity of license units. When you buy more licenses, the available count on the SKU increases; when you reduce seats, the available count decreases at the next billing cycle.

A subscription is the billing object; a license is the assignable unit that belongs to that subscription. One subscription of Microsoft 365 E3 with 100 seats gives you 100 individually assignable E3 licenses. The admin center also surfaces trial subscriptions here, which can be converted to paid subscriptions before they expire.

SKUs, Service Plans & Per-User Disablement

A license SKU (for example Microsoft 365 E3 or Microsoft 365 Business Premium) is a bundle of service plans. Each service plan maps to a workload — Exchange Online, SharePoint Online, Microsoft Teams, Microsoft Copilot, Defender for Office 365, and so on. The SKU's product name is what you buy; the service plans are what the user actually gets enabled for.

Administrators can disable individual service plans per user while keeping the SKU assigned. This is common when an organization licenses everyone for E3 but wants to withhold Microsoft Bookings or Yammer from a subset of users. In the admin center this is done under the user's Licenses and apps pane by toggling individual apps off. With Microsoft Graph PowerShell the same outcome is achieved by posting an assignedLicenses payload that lists the SKU to keep and the disabledPlans array of service plan IDs to turn off.

Assigning Licenses to Users

Before a license can be assigned, the user object must have a usage location set (a two-letter country code such as US or GB). Without a usage location the assignment fails with a usage-location validation error — this is one of the most common new-admin mistakes and a frequent exam point. Set usage location in the user properties pane or via PowerShell before assigning.

Direct assignment happens on the user's Licenses and apps pane: pick one or more SKUs, optionally disable service plans, and save. Bulk direct assignment is available from the Active users list by selecting multiple users and choosing Assign licenses in the bulk actions bar.

Group-Based Licensing

Group-based licensing is the recommended pattern for any tenant larger than a handful of users. You assign one or more SKUs to a security group or a Microsoft 365 Group, and every member inherits the license automatically. When a user joins the group, Entra ID provisions the license; when they leave, the license is reclaimed. This eliminates per-user assignment work and keeps group membership as the single source of truth for entitlement.

A user can receive licenses from multiple groups, and Entra ID processes all group-based assignments together. When service plans from different SKUs conflict (two SKUs enabling the same workload in incompatible ways), or when a user's direct assignment plus group assignment produce duplicate service plans, Entra ID records a license error rather than silently picking a winner. Microsoft has raised the legacy limits on group-based assignments several times; the safe exam answer is that multiple group-based assignments are supported and that conflicts surface as errors to be remediated, not that there is a fixed small cap.

License Assignment States & Resolving Errors

Each user's license record shows an assignment state:

Common error causes and their fixes:

• Duplicate service plans across SKUs — two assigned SKUs both enable the same plan in a conflicting way. Remove one SKU or disable the conflicting plan on one of them.
• Insufficient licenses — the SKU has zero available seats. Purchase more seats or reclaim licenses from inactive users.
• Missing usage location — set the user's usage location, then retry the assignment.
• Conflicting service plans — for example, two plans that cannot coexist on the same user. Disable one of the conflicting plans on the user or move the user to a different group.

The admin center surfaces errors on the affected user's Licenses and apps pane and in the group-based licensing error view; Microsoft Graph exposes the same data via the user's licenseAssignmentStates.

Monitoring Licenses & Subscriptions

Monitoring lives in Billing → Licenses and Billing → Your products. Key views:

• License usage per SKU — assigned vs. available vs. expired counts; spot SKUs running low before users fail to get licensed.
• Expiring subscriptions — subscriptions nearing renewal or expiry, including trials about to lapse.
• Trial-to-paid conversion — a trial subscription can be converted to a paid subscription from the subscription's details page; converting preserves the tenant's data and configuration rather than letting the trial expire and removing services.
• Bill notifications — configure billing notification contacts so the right people are alerted before a subscription auto-renews or lapses.