Review Microsoft 365 licenses by comparing what the business buys, what is assigned, what is used and what each person actually needs. Those are four different counts. An inactive-looking account is a reason to investigate, not an automatic instruction to remove a license.
Before making changes, identify the subscription, purchasing channel, renewal terms and business owner. Removing a user’s assignment and reducing the number of purchased seats are separate actions.
Use a four-column reconciliation
| Column | Source to inspect | Question it answers |
|---|---|---|
| Purchased | Subscription and billing records, including reseller records where applicable. | What quantity is the business paying for under this agreement? |
| Assigned | User and group-based license assignments for the product. | Which accounts currently receive the entitlement? |
| Observed use | The relevant service usage reports and their date range. | What activity did the available report actually measure? |
| Confirmed need | Manager, application owner and records requirements. | What services must remain available for this account or business process? |
Keep products distinct. Two plans can overlap in some capabilities without being interchangeable for every user. Record the required features before proposing a downgrade, and check the current product terms rather than inferring eligibility from the product’s name.
Do not turn missing activity into a savings claim
Microsoft’s usage reports cover defined reporting windows and can lag behind activity. Different service reports measure different actions. Read the report definition and refresh date before drawing conclusions about a person’s work. Microsoft: activity reports.
Consider an illustrative subscription with 25 purchased seats, 22 assigned seats and 19 accounts showing activity in the selected report. That does not establish that six seats can be removed. Three purchased seats are unassigned, while three assigned accounts need investigation. A seasonal worker, a person on leave or a business dependency may explain an apparent gap. The report alone does not answer those questions.
Record a proposed action for each exception: keep with a reason, remove after the relevant handover, change plan after feature validation, or investigate further. Name the approver and the date. Keep personal activity information restricted to people who need it for this review.
Check consequences before unassigning
A license can enable several services. Microsoft’s assignment guidance explains how administrators manage those entitlements; the business still needs to understand the affected user’s data and service dependencies before changing them. Microsoft: assigning licenses.
For a departing employee, complete the applicable account, mailbox and file handover first. For an active employee, confirm the replacement plan supports their required applications and workflows. Check whether a group assigns the license so that a one-off change does not conflict with the intended group policy.
Ask the records owner about retention and access requirements. Do not assume that removing a license is a suitable method of archiving business records, or that a data-retention behavior applies equally across every service and subscription.
Reconcile billing after the account decision
Microsoft documents different seat-change procedures and restrictions depending on the billing agreement and purchasing channel. Prepaid arrangements and reseller purchases may require different handling. Verify the actual subscription’s available reduction date and terms. Unassigning a user does not by itself establish a lower purchased quantity or a reduced invoice. Microsoft: buying and removing licenses.
- Capture the starting purchased and assigned quantities.
- Approve the specific account changes and complete required data handovers.
- Apply the authorized changes through the relevant administration process.
- Request or apply the permitted subscription quantity change through the correct seller.
- Verify the resulting entitlement count, effective date and billing record.
Report confirmed savings only after the contractual and billing effect is established. Separate a future renewal opportunity from a reduction already reflected in billing.
This review can follow a Microsoft 365 migration or a change in staffing. Bring the four-column reconciliation and subscription terms to a Microsoft 365 support review so proposed changes preserve the services the business needs.
By mjunaid for TX Computing. Sources checked November 7, 2026. The cover is a generated conceptual illustration, not a customer installation.