How to Find and Reclaim Unused Microsoft 365 Licences

How to find and reclaim unused Microsoft 365 licences

Short answer: build a report that flags possible waste, then have an administrator verify each account, workload, mailbox, group assignment and contract before changing anything. A disabled account or a long gap in sign-in activity is a reason to investigate, not automatic proof that a licence can be removed.

This report-first method helps teams find unused Microsoft 365 licences without disrupting work. It separates observable signals from decisions and keeps removal under human approval. Updated 7 November 2026.

Start with evidence, not an automatic removal

A good licence assignment review starts with a dated inventory of users, account state, assigned products and service plans, assignment source, sign-in indicators, mailbox type and business owner. Microsoft Graph's `licenseDetails` endpoint returns details for licences assigned directly and through licensed-group membership. Its documentation identifies delegated LicenseAssignment.Read.All as the least privileged permission for that operation and says application permissions are not supported. This is a Microsoft API reference, read 7 November 2026; administrators should confirm the current permission model and their approved reporting route before use.

Keep the extract limited to fields needed for the review, store it in an approved location and record when it was generated. A spreadsheet or read-only CSV report is enough to begin. Do not start by removing assignments or by treating a cost estimate as a realized saving.

Four signals worth reviewing

1. Disabled accounts that still have assignments

A disabled account with a paid product assigned is a strong prompt to ask whether the person has left, changed role, or still owns a service, workflow, mailbox or data. Check the account's owner and dependencies, group-based assignment rules, retention needs and any handover period. If the account is an emergency, service or shared workload identity, use the organization's specific policy instead of an employee rule.

2. Long gaps since sign-in

Microsoft 365 sign-in activity is one signal to review. Microsoft Entra's inactive-account guidance explains how sign-in activity can help investigate inactive accounts. It also stresses that an inactivity window depends on context. The documented lastSignInDateTime records an interactive sign-in attempt, which is not the same as proof of successful use. The page notes that displayed activity can take time to update; access to lastSuccessfulSignInDateTime has separate licensing and permission prerequisites. Read 7 November 2026.

Use a gap as a review threshold that your organization chooses. Check leave, seasonal patterns, non-interactive workloads and recent successful activity with the service owner. If the evidence is stale or missing, mark the candidate as uncertain rather than inactive.

3. Shared mailboxes

A shared mailbox licence needs its own review category. Microsoft's shared-mailbox guidance says a separate licence is not required in some situations, but lists exceptions tied to mailbox size, archiving, holds and advanced features. Read 7 November 2026. Verify the live mailbox configuration and current licensing terms before changing its assignment. A missing interactive sign-in is not a safe removal signal for a shared mailbox.

4. Duplicate or overlapping SKU assignments

Duplicate licence SKUs can look similar while providing different service plans, or the same entitlement can arrive by direct and group assignment. Compare the enabled services with the user's work, confirm the assignment source, and check whether a group rule will restore a removed licence. Label these rows “possible overlap” until an administrator and service owner verify the requirement.

Make the report useful to a reviewer

For each candidate, show the evidence and its date, why it was flagged, what remains unknown, the business or service owner, the next verification step and a status such as review, confirmed needed, approved to change or unresolved. Do not label a row “waste” just because an account is disabled or quiet. Keep the report separate from the action process: no automatic removal, no silent group changes and no unreviewed mailbox changes.

Before anyone acts, check dependent services, retention and legal holds, mailbox features, group membership and subscription commitments. The authorized administrator should make an approved change through the tenant's established process, document the decision and check that the user or service still works afterward. If a reviewer cannot establish the assignment's purpose, leave it in place until the right owner can decide.

Estimate savings carefully

Use the tenant's actual contract price, currency, renewal date and cancellation terms. A public list price may not match a negotiated rate, and a remaining commitment can mean that removing an assignment does not immediately reduce the bill. Keep confirmed changes separate from potential candidates, and state the assumptions behind any estimate.

CoreView's article on automating Microsoft 365 administration presents licence management as one possible automation use case. This is a vendor perspective, published and last updated 3 June 2024, not independent evidence that automated removal is safe for your tenant. A read-only report can surface candidates; a human should decide whether to change a licence.

A practical review checklist

• [ ] Export a minimal, dated view of assignments and account signals.
• [ ] Separate disabled users, long sign-in gaps, shared mailboxes and possible SKU overlap.
• [ ] Confirm the signal with the account or service owner.
• [ ] Check group assignments, enabled service plans, mailbox features and retention.
• [ ] Verify actual contract and renewal terms before estimating savings.
• [ ] Record approval before an authorized administrator changes anything.
• [ ] Recheck the dependent service and assignment rule afterward.

How it works

The licence waste analyzer reviews a selected CSV locally in the browser. The Microsoft 365 licence cost calculator helps organize cost assumptions. Both are review aids: they do not connect to a tenant or remove licences. Use the IT automation priority planner to plan a controlled review, or request a service for help.

Frequently asked questions

Does a disabled account always mean its licence is unused?

No. Confirm its owner, services, group rules, retention requirements and any handover period first.

Does no recent sign-in prove a licence is not needed?

No. Sign-in activity is a signal with timing and interpretation limits. Check with the owner and consider workload patterns.

Should a shared mailbox have its licence removed?

Not without checking the mailbox's current size, archive, hold and feature requirements against Microsoft's current guidance.

Can duplicate products be removed automatically?

This guide recommends human review. Similar names or overlapping assignments do not prove that an entitlement is redundant.

Next: IT automation priority planner · Request a service