Reduce SaaS sprawl by building a reliable application inventory, checking real usage with business owners, and matching any license changes to the contract and renewal terms. Low activity is a reason to investigate—not proof that a tool or seat is unnecessary—and removing a license does not always lower the bill.
How do you find all the SaaS tools your company is paying for?
No single record is likely to show every app, user, seat, and charge. Combine financial, identity, vendor, and business-owner evidence, then keep the resulting inventory current. The FinOps Foundation identifies stakeholder interviews, financial records, and SSO or CASB platforms as discovery methods; usage and cost data may need to be reconciled because they can come from different sources.
As an Amazon Associate I earn from qualifying purchases.
Build an inventory from multiple sources
- Finance and procurement: Review invoices, payment-card records, purchase orders, contracts, and renewal notices.
- Identity and security: Check SSO and CASB records, identity directories, and connected-app inventories. Microsoft Defender for Cloud Apps describes an inventory view for SaaS and connected OAuth applications that includes permission and consent details: Microsoft Defender for Cloud Apps app governance.
- Vendor consoles: Inspect subscriptions, assigned users, purchased seats, activity reports, and billing details in each service.
- Stakeholders: Ask department leads, application owners, and employees what tools they use, including tools purchased outside standard procurement.
For each application, record its business owner, purpose, department, users and seats, contract and renewal dates, data sensitivity, and the evidence source. Treat this as an operating record rather than a one-time spreadsheet.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →How do you know which licenses are unused?
Start with the strongest activity evidence each vendor provides, then compare it with account and seat records. The FinOps Foundation cautions that SaaS license and consumption data can be less granular than cloud billing data and may not include associated cost details; reconciling usage and spend may require separate sources.
Calculate useful baseline measures
- License utilization: assigned licenses divided by purchased licenses.
- Active-to-provisioned user ratio: active users divided by provisioned users.
These are operational measures to calculate from your own records, not industry benchmarks or promised savings. Where available, also check feature use, last activity, and whether the account is a normal user, service account, integration, or shared operational identity.
Use inactivity as a review signal
Microsoft Learn gives 90–180 days as an example range many organizations may use to define inactive accounts. It is not a universal license-removal threshold: the right window depends on the organization, and legitimate absences such as vacation matter. Seasonal work, audit retention, business continuity, periodic campaigns, and infrequent app use can make a quiet account necessary.
Microsoft Entra’s recommendation for investigating certain unused applications uses activity of over 90 days. The recommendation is labeled preview in Microsoft’s guidance, and administrators are told to decide whether an app is still needed before removing it: Microsoft Entra recommendation to remove unused apps. This is a product-specific prompt, not a general SaaS rule.
Free tools Windows power users keep installed
One-click scans. No signup required.
How should you review dormant or overlapping tools?
Group candidates by the kind of decision they require: unused seats, inactive accounts, overlapping applications, downgrade opportunities, or subscriptions approaching renewal. For each one, ask the business owner whether the apparent lack of activity reflects non-use or a legitimate exception.
- Does the application support seasonal or infrequent work?
- Is it needed for business continuity, an audit, or data retention?
- Does it support an integration, service account, or recurring campaign?
- Is another application genuinely replacing it, or do the tools serve different teams or workflows?
- Would a lower tier meet the need, or would removing a feature disrupt users?
Microsoft’s account guidance likewise says the inactivity period should fit the organization and recognizes vacation as a reason for legitimate inactivity: Microsoft guidance for removing a former employee.
How do you remove an unused license without disrupting work?
Confirm the owner’s decision, follow your access-removal process, and preserve or transfer data and ownership before unassigning a seat. License unassignment and account deletion are different actions; the exact workflow and effects depend on the vendor.
Rank #3
For Microsoft 365
- Confirm with the manager or application owner that the person no longer needs the service, and identify any files, mailbox content, or ownership that must be retained or transferred.
- Use an authorized role in the Microsoft 365 admin center to unassign the license, or use Microsoft’s documented PowerShell approach. Follow the current Microsoft workflow for the account type and product.
- Check whether the released license will be reassigned. Microsoft says that if an unused license will not be reassigned, administrators should consider removing it from the subscription so the organization does not keep paying for more licenses than needed: Assign or unassign Microsoft 365 licenses.
In Microsoft’s former-employee guidance, data is held for 30 days after license removal; after that, most Microsoft 365 content is described as permanently deleted, with SharePoint documents excepted. Verify the current product-specific rules, mailbox behavior, account status, preservation obligations, and transfer steps before acting: Microsoft guidance for removing a former employee. Do not apply this Microsoft 365 period to other SaaS providers.
Recommended Free Tools
Will removing a license lower the bill?
Not necessarily. Unassigning a seat may free it for another user without reducing the number of licenses purchased. Whether a change lowers costs depends on the contract, billing arrangement, timing, and whether the seat is actually removed from the subscription or commitment.
Before making a change, check the contract and renewal terms with procurement or the vendor:
- Are mid-term seat reductions permitted, or only changes at renewal?
- How do true-downs work, and when do they take effect?
- Are minimum seat quantities, bundles, volume discounts, or tier thresholds involved?
- Could usage-based charges remain even after a user’s seat is removed?
- What notice period, exit terms, or renewal deadline applies?
Use the usage baseline early enough to inform renewal decisions. The FinOps Foundation recommends reviewing pricing structures, renewals, and contractual constraints before changing licenses: FinOps Foundation SaaS cost optimization.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.How do you stop SaaS sprawl from returning?
Make ownership, purchasing, access changes, and renewal review part of normal operations. The FinOps Foundation recommends clear SaaS ownership, procurement and renewal workflows, centralized discovery, cost allocation, and identifying unused, underutilized, or duplicate subscriptions.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
- Assign a business owner and cost owner to every application.
- Route purchases and renewals through an approval process that updates the inventory.
- Include SaaS access in joiner, mover, and leaver workflows.
- Schedule recurring usage and seat reviews with owners, using a window suited to the app’s work cycle.
- Keep evidence, decisions, contract constraints, and renewal dates with the application record.
As the FinOps Foundation puts it: “For usage based SaaS, it’s critical to ensure that user management exists (adding and removing people when they join/leave, but also maintaining a view on how a user is (or isn’t) using the SaaS application and looking to revoke licenses that aren’t used to reduce costs where allowed under the contract.”
When is a SaaS management platform worth considering?
A platform can help centralize discovery and visibility, but it is not the only way to manage a smaller portfolio. A team may begin by reconciling finance, identity, vendor, and owner records. If evaluating a platform, compare the capabilities that affect your actual discovery and governance needs:
- Discovery inputs: integrations with SSO, finance, browser or network signals, vendor APIs, and application inventories.
- Coverage and freshness: recognizable SaaS services and how often the service-recognition library is updated.
- Usage and license detail: seat assignments, active usage, feature-level evidence, billing, and licensing-model support.
- Workflow fit: procurement approval, renewals, joiner/mover/leaver operations, owner assignment, and audit reporting.
- Security and scale: permissions, data handling, extensibility, integration burden, and fit for the size of your portfolio.
The FinOps Foundation lists these types of factors, including discovery methods, recognized-service coverage, update frequency, licensing models, scalability, security, and extensibility: FinOps Foundation SaaS management and governance.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
