Unused SaaS licenses: how to find and reclaim them
To find unused SaaS licenses, compare the seats you pay for with the people who actually signed in, over a fixed window such as 90 days. List the seats with no activity, ask each owner whether the seat is still needed, then remove or downgrade the ones that are not. Do the check before each renewal so the numbers can inform what you buy next.
How common are unused SaaS licenses?
Nobody knows your exact number until you measure it, but the published figures suggest it is worth checking. In a January 2022 release, the SaaS management vendor Zylo said the average organization was using only 60% of its provisioned SaaS licenses, which it described as leaving 40% unused. More recently, a Zylo article updated in April 2026 says nearly 46% of SaaS licenses go unused in any 30-day period.
Two cautions. Zylo sells software that tackles this problem, so treat the figures as a signal, not a benchmark for your company. And “unused in 30 days” is a strict test. Some people use a tool only once a quarter, and they still need it.
What counts as an unused license?
Pick a definition before you pull any data. Write it down so everyone applies the same one.
- Assigned but never used. The person has a seat and has never signed in.
- Inactive for a set window. No sign-in or activity in, say, 90 days. Microsoft’s guidance on inactive accounts notes that a reasonable window in many organizations is between 90 and 180 days, because people go on vacation or leave for other legitimate reasons.
- Belongs to someone who left. The account still exists, though the person no longer works for you.
- Wrong tier. The person uses the tool, but only needs a cheaper plan.
The window is your choice. A longer one is safer. A shorter one finds more seats and makes more mistakes.
Where do you get usage data?
Start with what you already have:
- The vendor’s admin console. Many tools show a last active date for each user, or let you export one.
- Your identity provider. If your company uses Microsoft Entra ID, the admin center can show a last sign-in column, and Microsoft Graph exposes a signInActivity property. Microsoft says reading it through Graph requires an Entra ID P1 or P2 license. Sign-in data shows access to the app, not how valuable the work was.
- Built-in usage reports. For Microsoft 365, the Active users report shows trends over the last 7, 30, 90 or 180 days and a per-user table with the last active date for each service. It can be exported to a .csv file. Microsoft says usernames are hidden by default, so an admin has to change that setting to see them.
- HR records. A list of people who left in the past year, matched against each tool’s user list, finds the easiest seats to remove.
Expect gaps. Tools with their own logins may not show up in your identity provider, and some tools report no per-user activity at all.
How do you review the list with owners?
A data pull gives you candidates, not decisions. Follow a simple routine:
- Name an owner for each tool. The owner is the person who can say whether a seat matters.
- Send a short list. Include the person, the seat, the last activity date and a deadline for a reply.
- Decide what silence means. Some teams reclaim the seat after notice. Some keep it until an owner answers. Choose one rule up front. Zylo’s article describes both options: notify users before removing access, or reclaim automatically.
- Keep an exception list. Auditors, seasonal staff, on-call engineers and executives may use a tool rarely and still need it.
- Record every change. Note the date, the seat, the reason and who approved it.
Also check whether the account holds data or admin rights. Before you delete anything, make sure the vendor lets you restore it and transfer the files to someone else.
What does a license review look like? (Illustrative example)
The numbers below are made up to show the arithmetic. They are not real data.
| Tool (fictional) | Seats paid | Price per seat per year | Active in 90 days | Seats to review |
|---|---|---|---|---|
| Design app | 40 | $180 | 31 | 9 |
| Analytics add-on | 25 | $600 | 12 | 13 |
| Contract tool | 15 | $300 | 14 | 1 |
The “seats to review” column is a list of questions. It is not a saving. A vendor may require a minimum seat count, a smaller plan may carry a different price per seat, and some of those people will turn out to need the tool.
Can you cut seats right away?
Not always. Your contract decides. Read the order form for the term, the minimum number of seats, whether you can reduce seats mid-term and the notice period for a change. Many agreements only allow seat reductions at renewal, and the notice date can pass months before the renewal date. If you cannot cut now, you can still reassign the seat to a new hire instead of buying another one, and you can bring the usage data to the next renewal conversation. Our guide to SaaS renewal management covers notice dates and calendars, and the SaaS spend management guide covers building the inventory first.
Take the results to the vendor with care. Usage data supports a request for fewer seats or a different plan. It does not guarantee the vendor will agree, and no one can promise a particular saving in advance.
How often should you repeat it?
Zylo’s article advises a continuous process, because companies add new apps all the time. An example rhythm for a small finance or operations team is:
- Once a quarter for your biggest tools.
- Once before every renewal, at least 90 days ahead of the notice deadline, which gives you time to act.
- Each time someone leaves, as part of offboarding.
Where Renewlark fits
Renewlark is being built to review your vendors, contracts and renewal dates, flag seats and spend worth a closer look, and keep a person in charge of approving every important action. Join the waitlist.
This article is general information about business software management, not legal, financial or tax advice. Check your own contracts and talk to a qualified professional about your situation.