Recommended Free Tools
The most dependable way to manage software licenses is to run them as a recurring IT asset management (ITAM) process, not as a one-time inventory project or a scanner report. Assign owners, set approval rules, keep accurate software and entitlement records, reconcile what is installed or consumed against the governing agreement, investigate exceptions, and review renewals on a fixed schedule. Discovery and license tools make inventory and reporting faster, but the contract and the original entitlement records remain the authority whenever a tool’s output disagrees with them.
Why a process works better than a spreadsheet or a scanner
ISO/IEC 19770-1:2017 sets out requirements for an IT asset management system. The ISO/IEC JTC 1/SC 7 committee describes that standard as based on the Plan-Do-Check-Act cycle and organizes ITAM into 15 process areas. The practical implication is that license management needs ongoing ownership and feedback loops. A spreadsheet that is updated once a year, or a scan that runs without anyone acting on its results, will drift out of date and cannot show why a decision was made.
As an Amazon Associate I earn from qualifying purchases.
Two records that must be reconciled
License management depends on comparing two different kinds of evidence. Discovery answers what is actually installed or running. Entitlement records answer what the organization is allowed to do. Neither is enough alone, and the two standards that address them cover different things.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstall| Record | Question it answers | Typical source | Standard reference |
|---|---|---|---|
| Discovered installation or consumption | What software, edition, and version is present, and on which device, server, or cloud account? | Endpoint agents, cloud and service records, inventory tools | ISO/IEC 19770-2:2015 covers software identification tags. It does not define how tags are reconciled with entitlements. |
| Entitlement | What rights were bought, under which metric, term, and restrictions? | Agreements, amendments, orders, invoices, subscription portals | ISO/IEC 19770-3:2016 covers the entitlement schema and common terms. The original licensing documentation governs for legal purposes. |
The method in seven steps
The steps below run in order. Each one produces the inputs the next step needs, so skipping ahead usually creates reconciliation errors that surface during a renewal or vendor audit.
#1 Best Overall
1. Set scope, ownership, and policy
Start by listing what the program covers: business units, geographies, cloud accounts, devices, servers, SaaS subscriptions, and software families. Then name accountable owners. Depending on the organization, this may include ITAM or software asset management (SAM), procurement, finance, security, legal, and system administration. Write down who may request, approve, install, assign, transfer, and retire software. ISO/IEC 19770-1 is an organization-level management-system standard, so adapt its scope to your organization rather than treating it as a fixed deployment recipe.
2. Build a trustworthy inventory
Discover installed applications and relevant infrastructure through endpoint, cloud, and service records. Normalize each record so it can be matched to a contract:
- Publisher and product name, written the same way in every source
- Edition, version, and deployment type
- Device, server, or cloud account identity
- The source of each record and the date it was collected
- Known collection gaps, such as machines that were offline or accounts a scanner could not reach
Software identification tags can help identify products, but they do not tell you how to reconcile the results with what you have purchased.
3. Build entitlement records from authoritative evidence
For every purchase or subscription, keep the evidence that defines the right. Store the following for each entitlement:
- The agreement and all amendments
- Order or invoice records showing what was bought
- Product and edition
- Quantity and license metric
- Term, start date, and renewal date
- Usage rights, restrictions, and any assignment or transfer conditions
A normalized entitlement record is useful for reporting. When a question turns on contract language, check the original vendor documentation before acting on the record.
4. Reconcile using the actual license metric and terms
Compare discovered installations, user assignments, or cloud consumption with the entitlements. The correct unit of measure changes by product and contract, so do not assume every license is counted per user or per device. Some products are counted by processor cores, sockets, or virtual machines; others use named users or consumption. AWS License Manager tracks licenses by vCPU, physical core, socket, or machine in its documented scenarios. Microsoft publishes product-specific requirements in its Licensing Guidance portal, and those rules differ from product to product.
Flag the following for human review rather than resolving them automatically:
- Installations with no matching entitlement evidence
- Deployments that do not match the metric (for example, a virtualized environment where core counts are ambiguous)
- Excess capacity that cannot be confirmed as unused
- Any clause whose interpretation is unclear
5. Control changes that consume rights
Connect license checks to the processes that create consumption: purchasing, access requests, provisioning, cloud launches, and changes to infrastructure. Limit operations that consume licenses to authorized users. Automated rules are helpful only when they accurately reflect the agreement. AWS describes hard and soft limits for supported License Manager scenarios, but those controls do not interpret every external contract on their own, so a rule that is stricter or looser than the agreement creates a new problem rather than solving one.
6. Review use, exceptions, renewals, and evidence
Set a review cadence based on the organization’s risk and how often its software changes. Each review should cover:
- Stale installations that no longer have an owner or business purpose
- Recent assignment and transfer changes
- Low or unused capacity, but only where reliable usage evidence exists
- Upcoming renewals and any auto-renewal dates
- Open exceptions and unresolved contract questions
Keep the reports and approvals that supported each decision, so the reasoning can be reconstructed later. Savings and audit outcomes depend on the organization’s own data, so measure them from your own records rather than assuming a percentage.
7. Improve the system over time
ISO/IEC JTC 1/SC 7 recommends building in three tiers, in order: Trustworthy Data, Lifecycle Integration, and Optimization. Data quality and clear process ownership come first, because lifecycle integration and optimization are only as reliable as the records beneath them. Once records are trustworthy, connect them to purchasing and change processes, and only then use them to make decisions about consolidation, reallocation, or renewal terms.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Choosing an approach
There are three common approaches. The right one depends on how many software products, contracts, and deployment environments you must track.
Rank #4
| Approach | Useful when | Compare on |
|---|---|---|
| Controlled spreadsheet or registry | The software estate and contract set are small enough that named owners can keep them current | Data ownership, change history, review cadence, evidence links, access control, and error risk |
| Dedicated SAM or license management platform | Discovery spans many endpoints, teams, cloud accounts, license metrics, or vendors | Product normalization, inventory sources, entitlement workflow, contract-specific rules, integrations, audit trails, reporting, security, and total operating effort |
| Specialist-supported program | Agreements, virtualization, cloud deployment, or vendor-specific metrics require expertise the team does not have in-house | Independence, experience with the relevant vendors and deployment types, scope, evidence handling, conflict disclosures, and engagement terms |
These are criteria for evaluating an approach, not a ranking of products. The ISO documents describe a management framework, and the AWS documentation describes AWS’s own services. Neither is an independent comparison of commercial SAM products.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.AWS License Manager and AWS Audit Manager: what they do and do not do
Cloud-native tools can automate parts of the method, especially for AWS environments, but their scope is narrower than a full ITAM program.
AWS License Manager
AWS License Manager provides consolidated visibility and reporting for licenses across AWS regions and accounts. In its documented scenarios it tracks licenses by vCPU, physical core, socket, or machine. It can discover certain applications on premises through AWS Systems Manager Inventory and apply licensing rules to tracked resources. Before relying on it, confirm the setup requirements, the supported discovery sources, which products it covers, and how it treats your specific agreement. Its boundaries are between AWS-managed resources and on-premises systems, so environments that fall outside those boundaries need separate tracking.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minuteAWS Audit Manager
AWS Audit Manager offers a prebuilt framework that helps prepare for audits using licensing rules you define. AWS states that the framework’s controls are not intended to verify that systems comply with license rules. Treat it as preparation support, not as a compliance certification or legal assurance.
Best Value
What AWS names as prerequisites
AWS’s description of effective license management lists three prerequisites that apply regardless of tool:
- Expert understanding of the language in enterprise licensing agreements
- Appropriately restricted access to operations that consume licenses
- Accurate tracking of license inventory
Standards and their current status
Standards are revised over time, so check the current edition on ISO’s website before citing one in a policy. As of the ISO listings reviewed for this article:
- ISO/IEC 19770-1:2017, IT asset management systems: Requirements. ISO states that this edition applies to IT asset types and organizations of all sizes. ISO’s listing says it was reviewed and confirmed in 2024, and it lists Amendment 1:2024.
- ISO/IEC 19770-2:2015, Software identification tag. This standard specifies software identification tags. It does not prescribe the ITAM processes needed to reconcile tags with entitlements.
- ISO/IEC 19770-3:2016, Entitlement schema. This standard describes common terms and a format for software entitlement information. It states that the original licensing documentation takes precedence for legal purposes.
Where the method usually breaks
When a license position looks wrong, the cause is usually in one of the records rather than the method itself. Check these failure points first:
- Purchase evidence is missing. Locate the original order, invoice, and agreement amendments. Do not rebuild an entitlement from a tool’s guess about what was bought.
- Discovered editions do not match entitlement editions. Verify the edition against the product’s own metadata and the agreement before counting it as compliant or excess.
- Cloud or virtualized workloads are missing from discovery. Confirm that every account, region, and host class is in scope, and record any boundary the tool cannot cross.
- A tool rule is stricter or looser than the contract. Compare the rule with the agreement clause it is meant to reflect, and correct the rule rather than the contract.
- A renewal date was missed. Add renewal dates and notice periods to the review calendar as soon as an agreement is recorded, so they are reviewed before they pass.
Where a question cannot be answered from these records, escalate it to the owner named in step 1, and record the decision and its evidence.
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.
