License utilization

The License Utilization report provides a detailed analysis of how effectively licenses are being used across different features. It focuses on actual consumption patterns by showing the relationship between the number of licenses in use and their corresponding utilization percentage. This report helps identify underutilized or overutilized licenses, enabling better monitoring and optimization of license usage.

License Utilization

License Utilization report showing required versus purchased licenses to ensure service quality and optimize license procurement.

Visualizations

• License Utilization Chart: A combination chart. The Max of Usage Percent line plots the share of time spent at each concurrency level, and the Quality of Service column marks the concurrency level that satisfies the target you set. Where your QoS percentage crosses the usage line is the value reported as Required Licenses for QoS.

Values displayed:

• Number of Used Licenses: X-axis - the concurrency level, from 0 up to the size of the pool.

• Max of Usage Percent: The share of the period spent at that concurrency level or higher, so the line starts at 100% and falls away as concurrency rises.

• Quality of Service: The column marking the concurrency level that satisfies the target you set.

• Total Licenses: A KPI card with the count of licenses owned across the features that match the current filter selection.

• Quality of Service %: A control, not a read-out. Type a target percentage or drag the slider - it defaults to 95 - and the QoS column and the Required Licenses for QoS card recalculate against it. QoS is the proportion of time the sized pool should be able to serve all concurrent demand, so a 95% target sizes the pool for everything except the busiest 5% of the period.

• Required Licenses for QoS: A KPI card with the number of concurrent licenses needed to hold the service level you set. The value comes from the inverse-usage calculation, which caps it at the historical peak concurrent usage, so the recommendation never exceeds a concurrency level the period reached. Compare it with Total Licenses to see how many seats you can release, or how many you are short.

• Utilization Details Table: A day-by-day ledger behind the curve.

Values displayed:

• Feature Name: The licensed feature.
• Total Licenses Available: Size of the pool on that date.
• Licenses in Use: Concurrency observed on that date.
• Usage %: Utilization for that row.
• Usage Date: The day the row describes.
• Additional Key: Any extra licensing or configuration key associated with the feature. Rows with none read Not Available.
• License Type: The licensing model for the feature, for example Floating.

A Total row closes the table with the sum of Licenses in Use across every row in the current filter selection.

• Filters:

• Date: A relative date filter. It defaults to Last 14 days and prints the resolved range underneath (for example, 2026/07/11 to 2026/07/24). Select another preset, or a custom start and end date, to change the reporting period.

• Feature Name: Users can select any feature name from this filter.

• Software Name: Select a catalogued product from the SAM Catalog. The catalog normalizes publisher and product names, so filtering here groups license records that carry inconsistent raw license strings.

• Additional Key: Users can select any additional key from this filter.

• License Type: Users can select any license type from this filter.

• Server Name: Users can select any server name from this filter.

• Vendor: Users can select any vendor from this filter.

tip

Filter down to a single feature before reading the curve. With Feature Name set to All the X-axis mixes pools of different sizes and the utilization curve is not meaningful.

Interpreting this report

• This report answers the renewal question directly: how many licenses were enough? Read the curve from the highest used-license count back toward zero - the point where Usage % collapses toward zero is the concurrency level your organization genuinely reached. The Version 25 guidance for this chart applies unchanged (Version 25 reference).
• Total Licenses − Required Licenses for QoS = redundant seats at your chosen service level. With QoS at 95%, the Required KPI is the pool size that satisfies 95% of the observed demand; every seat beyond it bought availability you did not use. Move the QoS slider to price different risk appetites before a renewal.
• A long flat tail on the curve is not noise - investigate it. Usage that never drops to zero at high license counts points at forgotten sessions or offline borrows holding seats; the legacy documentation called these "blips". Check Currently consumed licenses and Borrowed licenses for the culprits.
• Long date ranges make this curve statistically meaningful. A 2-week window measures an incident, not a demand profile.