By Product

The By Product report page provides a high-level overview with visuals that summarize the cloud software spend by product.

Reading the report

The following values and key performance indicator (KPI) visuals are available.

Note:All spend data is based on the date range selected from the date filters. You can also filter data by cloud vendor and cost center, as well as choose the currency for displaying spend and savings values. For more information, see Viewing the Software Insights and Spend Optimization Report.

 

Value or KPI Visual

Description

Software and Compute Spend by Date

An area chart that shows the historical data of cloud software and compute spend on this software product by date.

Note:Products without software spend are not included.

Software Spend by Product

A pie chart that shows the PAYG software spend broken down by software product.

Operating Systems

The following information is displayed for each operating system product:

Total Software & Compute Spend
The broken-down spend in each supported cloud provider
Software Spend
Last 30 Days Potential Savings

Databases

The following information is displayed for each database product:

Total Software & Compute Spend
The broken-down spend in each supported cloud provider
Software Spend
Last 30 Days Potential Savings

You can right-click on a product tile and select Drill through > Product Details to drill into to the product details and view the following additional tabs and details.

Tab

Description

Overview

This tab provides spend and savings data about the software product.

Software and Compute—The total cloud spend on this product.
Software Spend—The PAYG software spend on this product.
Compute Spend—The compute spend on this product.
Last 30 Days Potential Savings—The potential savings over the last 30 days on this PAYG software product if it had been replaced with BYOL software, based on your IT Asset Management license entitlements.
Realized Savings—The actual savings over the last 30 days on this product.
Product in AWS—The broken-down spend and savings of this product in AWS.
Product in Azure—The broken-down spend and savings of this product in Azure.

Note:Currently, the Realized Savings calculation for Windows Server is only available for Windows Server in Azure. Support for Windows Server in AWS will be introduced in future releases.

Licenses

This tab provides the following information that is integrated from IT Asset Management for both Standard and Enterprise editions:

Total Available— The total number of purchased entitlements for SQL Server for the respective edition, that the organization owns or has rights to use in the public cloud. This is the baseline entitlement pool, before any allocation or consumption.
Entitlements consumed by On-Prem—The number of licenses that are currently deployed and are actively being used within the organization’s on-premises infrastructure.
Entitlements Available—The calculated remaining pool of unused licenses which are available for new deployments either in the cloud, or on-premises.
BYOL Used in AWS—The number of Bring-Your-Own-License licenses that are currently being used in AWS.
BYOL Used in Azure—The number of Bring-Your-Own-License licenses that are currently being used in Azure.
Subtotal—The total number of consumed licenses across all environments, including on-premises, AWS, Azure, and any other allocations.
Transferred from Enterprise/to cover Standard—Only available for SQL Server deployments, for the Standard edition this field tracks the transfer of Enterprise edition entitlements to Standard edition with a 1:4 conversion ratio, whereas for the Enterprise edition, the field tracks the conversion of Standard edition entitlements to Enterprise edition with a 4:1 conversion ratio. For customers, this reduces the need to purchase additional licenses by maximizing existing entitlements and ensures that all workloads can continue running with no interruption due to licensing constraints.
Balance—The final number of licenses after all allocations and transfers.

In addition, the Licenses tab also shows:

AWS PAYG Eligible for BYOL—The number of AWS PAYG entitlements that are available for conversion to BYOL.
Azure PAYG Eligible for BYOL—The number of Azure PAYG entitlements that are available for conversion to BYOL.

By right clicking on AWS or Azure, you can select Drill through, and click Product Details to see a historical view of eligibility and usage of BYOL by date range, cloud provider and cost center. This will show two charts:

Standard License Usage & Eligibility—Entitlement information for the Standard edition, displaying Azure and AWS BYOL entitlements, as well as Azure and AWS PAYG entitlements available for BYOL.
Enterprise License Usage & Eligibility—Entitlement information for the Enterprise edition, displaying Azure and AWS BYOL entitlements, as well as Azure and AWS PAYG entitlements available for BYOL.

For more information about license status, see License Status.

Resources

This tab provides a full resources list of resources with detailed information at the instance level. For example, Resource ID, Resource Name, Instance Type, License Model, License Status, Cloud Vendor, PAYG Price, Usage Hours, Realized Savings, and so on.

These details provide a clear correlation between Instance Type and Realized Savings.

You can sort and export the data on this tab.

Recommendations

This tab helps customers reduce licensing costs for Windows Server and SQL Server by providing instance- and group-level suggestions. These are generated using rule-based logic or AI/ML forecasting and highlight opportunities to switch between PAYG and BYOL models, consolidate resources, or adjust license purchases.

The following insights are available:

BYOL -> PAYG Potential Savings—Potential savings for licenses that are worth more than the PAYG cost their usage amount would incur.
PAYG -> BYOL Potential Savings—Potential savings if BYOL licenses were used instead of PAYG.
Underutilized BYOL Entitlements—BYOL licenses that aren’t being used to their full potential and are covering fewer vCPUs than they could.
Active BYOL Instances—BYOL instances that are currently in use.
Active PAYG Instances—PAYG instances that are currently in use.

In addition, the Recommendations tab provides a detailed breakdown of instances that can be converted from BYOL to PAYG, and vice versa, from PAYG to BYOL, as well as a table that details underutilized BYOL entitlements.

For more information about the recommendation tab, see Understanding License Recommendations.