Editorial photograph of an enterprise IT team running a Microsoft 365 license reclamation workshop with admin reports
Guide · Microsoft · M365 Reclamation

Microsoft 365 license reclamation. The pre renewal playbook.

Three types of M365 waste, the reclamation process, and how to reduce committed seat count before the next EA renewal.

Read the Framework Microsoft Practice
8 to 22%Typical reclamation recovery
a leading industry analyst firmRecognized
Industry Recognized
500+ Enterprise Clients
$2B+ Under Advisory
11 Vendor Practices
100% Buyer Side Independent

Microsoft 365 license reclamation is the systematic recovery of seats and add ons that no longer match the underlying workforce. Three types of waste drive the reclamation work. Inactive seats, oversized plans, and unused add ons. A typical M365 estate carries 8 to 22 percent waste before reclamation.

The reclamation work runs against the EA renewal calendar. A right sized estate becomes the renewal anchor and unlocks a further 6 to 12 percent discount uplift. Read the related Microsoft practice, the M365 cost per user article, the license optimizer, and the EA renewal guide.

Key Takeaways

What an IT licensing manager needs to know in 90 seconds

  • Typical M365 waste runs 8 to 22 percent. Across inactive, oversized, and unused add ons.
  • Inactive seats are 4 to 10 percent. Departures, role changes, project end.
  • Plan oversizing is 6 to 14 percent. E3 and E5 users who should sit on lower tiers.
  • Add on waste is 3 to 8 percent. Defender, Entra ID P2, Power BI, Visio.
  • The reclamation work runs in three phases. Identify, validate, reassign.
  • Reclamation is the renewal anchor. The right sized estate enters the next EA cycle.
  • Reclamation is repeatable. Annual cadence inside Vendor Shield style programs.

Three types of M365 waste

The three categories of M365 waste each carry their own detection signal and their own reclamation pattern. The framework below is the buyer side reference.

M365 waste typology

Waste typeTypical shareDetection signalReclamation action
Inactive seat4 to 10%No active sign in in last 90 daysReclaim or reassign
Plan oversizing6 to 14%User pattern matches a lower tierDowngrade to F1, F3, or Business
Add on waste3 to 8%Add on never invokedDrop add on at renewal

Inactive seat reclamation

Inactive seat reclamation is the simplest reclamation pattern. The detection signal is no active sign in in the last 90 days. The reclamation action is to reassign or reclaim the seat.

Common sources of inactive seats

  • Departures. Users who left and were not deprovisioned promptly.
  • Role changes. Users who moved to a role that does not need M365.
  • Project end. Contractors and project staff whose engagement ended.
  • Test accounts. Service accounts and test users that accumulate seats.
  • M&A overhang. Acquired company seats that were never reconciled.
  • Vacation parking. Long leave with no reassignment.

Inactive seat is the first reclamation move

The inactive seat reclamation is the first move because it produces the cleanest, lowest friction recovery. The seat is not in use. No user impact. The reclaimed entitlement either reduces commit at renewal or covers new headcount without an order.

Plan downgrade reclamation

Plan downgrade reclamation moves users from E3 or E5 to a lower tier when the usage pattern supports the downgrade. The most common downgrade targets are F1, F3, and Business Standard.

Common downgrade patterns

  • E3 to F1 for kiosk workers. Shared device, identity only.
  • E3 to F3 for frontline workers. Mobile, mailbox, light Office.
  • E3 to Business Standard for SMB units. Acquired subsidiaries.
  • E5 to E3 for non security users. Pull back the E5 premium.
  • E5 to E3 plus Defender for selective users. Targeted add on.

Downgrade saving math

DowngradeList price saving per user per monthAnnual saving per user
E3 to F1$33.75$405.00
E3 to F3$28.00$336.00
E3 to Business Standard$21.00$252.00
E5 to E3$21.00$252.00
E5 plus Copilot to E5$30.00$360.00

Add on rationalization

Add on rationalization removes paid add ons that have never been used. The Microsoft tenant carries unique add on telemetry, which makes the reclamation work data driven.

Common add on rationalization targets

  • Defender for Office 365. Plan 1 vs Plan 2 use evidence.
  • Entra ID P2. PIM, identity protection, access reviews invocation.
  • Power BI Pro. Workspace activity, report views.
  • Visio Plan 2. File open and edit telemetry.
  • Audio Conferencing. PSTN dial in usage.
  • Teams Phone Standard. Active phone number assignment.
  • Project Plan 3. Project use telemetry.

The reclamation process

The reclamation process runs in three phases. Identify, validate, reassign. The process repeats on an annual cycle ahead of the EA true up or the EA renewal.

Three phase process

  1. Identify. Pull the M365 admin center activity report. Cross reference with HR and provisioning data.
  2. Validate. Confirm inactivity with the line manager. Confirm role with HR. Confirm device assignment with IT.
  3. Reassign. Reclaim seats, downgrade tiers, drop add ons. Document each change in the license register.

Required data sources

  • M365 admin center usage report. Per user activity per service per 90 day window.
  • Entra ID sign in logs. Active sign in cadence.
  • HR active employee list. Joiners, movers, leavers.
  • Provisioning system. Service account and test account inventory.
  • Add on telemetry. Defender events, P2 invocations, Power BI workspace activity.
  • License register. Current entitlement, contract, amendment history.

Reclamation and the renewal anchor

Reclamation completed ahead of the EA renewal cycle resets the renewal anchor to the right sized estate. The right sized estate is the buyer side baseline in the renewal conversation.

Renewal timing

The reclamation work should complete 90 to 180 days ahead of the EA renewal window. The timing gives Microsoft account team time to absorb the right sized baseline and gives the buyer team time to set the renewal posture against the new anchor.

Reclamation is worth 6 to 12 percent on renewal

The reclamation work captures the per user and add on saving directly. The right sized baseline also unlocks a further 6 to 12 percent renewal discount uplift because Microsoft account teams discount more aggressively against documented right sized estates than against drift estates.

What to do next

The eight step checklist below moves an M365 estate from drift to a right sized reclaimed baseline ready for the EA renewal.

  1. Pull the M365 admin center usage report. Last 90 days.
  2. Pull the Entra ID sign in logs. Active cadence.
  3. Cross reference with HR joiners movers leavers. Full employee list.
  4. Identify inactive seats. Validate with line managers.
  5. Identify oversizing candidates. Map roles to tiers.
  6. Identify unused add ons. Telemetry per add on.
  7. Run the reassignment. Reclaim, downgrade, drop.
  8. Set the renewal anchor. Right sized baseline enters EA cycle.

Frequently asked questions

How much can a typical enterprise reclaim from its M365 estate?

The typical M365 estate carries 8 to 22 percent waste before reclamation. Inactive seats account for 4 to 10 percent. Plan oversizing accounts for 6 to 14 percent. Add on waste accounts for 3 to 8 percent. The categories overlap in practice. The realized reclamation typically lands between 10 and 18 percent of total M365 spend.

When is the right time to run reclamation?

The right time is 90 to 180 days ahead of the EA renewal window. The timing gives Microsoft account team time to absorb the right sized baseline and gives the buyer team time to set the renewal posture against the new anchor. Reclamation can also run on annual cycles inside Vendor Shield style programs.

Does Microsoft penalize aggressive reclamation?

No. Microsoft account teams negotiate against the right sized baseline. The buyer side benefits from running the reclamation work transparently and documenting the right sized estate in writing before the renewal opens. Aggressive reclamation that is well documented strengthens the renewal posture rather than weakening it.

What is the most common reclamation mistake?

Running reclamation only at renewal time rather than on an annual cycle. The annual cadence keeps drift contained, makes each year of reclamation lighter, and produces a continuous right sized estate. A program that runs only at renewal time captures less than half of the available recovery.

How does Copilot affect the reclamation conversation?

Copilot adds a $30 per user per month premium on top of E3 or E5. The Copilot population must be sized against adoption telemetry rather than against the E3 or E5 base. Many enterprises assign Copilot broadly and then reclaim 30 to 50 percent of the Copilot licenses inside the first 12 months when adoption data lands.

Can reclamation work be automated?

Yes for the detection step. The validation and reassignment steps require human review because the data alone cannot confirm role intent, vacation status, or strategic exception. Most mature programs automate the detection phase and run the validation and reassignment phases on a quarterly cadence with named owners.

How Redress engages on M365 reclamation

Redress runs the M365 reclamation workstream against the EA renewal cycle. The engagement pulls the admin center usage report, cross references with HR and Entra ID data, identifies the three waste categories, validates with line managers, and runs the reassignment ahead of the renewal anchor.

The engagement is independent. Buyer side. Industry Recognized. Five hundred plus enterprise software engagements. Two billion plus in client spend under advisory. Read the related Vendor Shield, the Renewal Program, the Benchmark Program, the Software Spend Assessment, the Benchmarking framework, the about us page, the management team page, the locations page, and the contact page.

Score your M365 reclamation potential against the buyer side benchmark in under five minutes.
Open the M365 License Optimizer →
White Paper · Microsoft

Download the Microsoft EA Renewal Playbook.

A buyer side framework for the Microsoft EA renewal cycle. Reclamation playbook, right sizing math, add on rationalization, and the renewal posture template.

Used across more than five hundred enterprise software engagements. Independent. Buyer side. Built for Microsoft customers running the next renewal cycle.

Microsoft EA Renewal Playbook

Open the white paper in your browser. Corporate email only.

Open the Paper →
8 to 22%
Typical M365 waste
10 to 18%
Reclamation recovery
6 to 12%
Renewal anchor uplift
500+
Enterprise clients
100%
Buyer side

We pulled the M365 admin center usage report, cross referenced Entra ID sign in logs, validated with line managers, and ran the reclamation across inactive seats, oversized plans, and unused add ons. The right sized estate landed 16 percent below the prior commit and unlocked an additional 9 percent renewal discount uplift at the next EA cycle.

Enterprise IT Licensing Lead
Global energy group
More Reading

More from this practice.

Microsoft Practice →
M365 Cost Per User 2026
Microsoft · Article
M365 Cost Per User 2026
The per user benchmark.
20 min read
M365 EA Renewal Guide
Microsoft · Guide
M365 EA Renewal Guide
The EA renewal playbook.
22 min read
Microsoft EA vs MCA-E
Microsoft · Article
Microsoft EA vs MCA-E
Channel choice decoded.
16 min read
M365 Copilot Licensing
Microsoft · Article
M365 Copilot Licensing
Copilot enterprise framework.
18 min read
Microsoft Services Practice
Microsoft · Practice
Microsoft Services Practice
The Microsoft services practice.
12 min read
Editorial photograph of enterprise contract negotiation strategy

Your reclaimed estate is your renewal anchor.

We have run 500+ enterprise clients across 11 publishers. Every engagement starts with one conversation.

Microsoft licensing intelligence, monthly.

EA renewal signals, reclamation patterns, Copilot adoption signals, and the wider Microsoft commercial leverage signals across every renewal cycle.