Understanding Integration with IT Asset Management
Cloud License Management (CLM) supports integration with Flexera One IT Asset Management (ITAM). Users can view their entitlement position and software usage in the cloud all in one spot, making it easy to identify potential savings and compliance risks at a glance.
Supported Microsoft Software Titles
CLM supports ITAM integration for the following Microsoft software titles:
|
•
|
Windows Server Standard |
|
•
|
Windows Server Datacenter |
|
•
|
Microsoft Core Infrastructure Server Suite Standard |
|
•
|
Microsoft Core Infrastructure Server Suite Datacenter |
Data Synchronization
By default, ITAM data is synchronized to CLM after each daily reconciliation run. You can also trigger this process manually to see updated ITAM data in CLM sooner.
Import Process Filters
As part of the import process, CLM filters on the following license properties:
|
•
|
Edition (e.g., “Standard” or “Datacenter” for Windows Server; “Standard” or “Enterprise” for SQL Server.) |
|
•
|
License Type (e.g., “Core Points” or “Processor Points”) |
Note:For Windows Server, licenses are synchronized for both the “Core Points” and “Processor Points” types. For SQL Server, only licenses of the “Core Points” type are synchronized.
|
•
|
Status (e.g., “Active”) |
|
•
|
Purchased (e.g., “1,000”) |
|
•
|
Upgrade Rights (e.g., support specific editions or until a set expiry date) |
|
•
|
Cloud Service Providers (e.g., any cloud service providers or selected cloud service providers) |
|
•
|
Cloud Consumption Settings (e.g., “Azure Hybrid Benefit”) |
Logic and Calculations
After filtering is applied, CLM performs the following logic and calculations.
For Windows Server Licenses
|
•
|
Standard Edition Licenses do not support dual use rights, except for 180 days or for migration purposes. However, CLM currently doesn’t support these exceptions. Therefore, Standard Edition licenses assigned to on-premises resources are deducted from the available quota for a more conservative estimate. |
|
•
|
Datacenter Edition Licenses support dual use rights, except if they are used for dedicated hosts. Therefore, Datacenter Edition licenses assigned to on-premises hosts should be deducted from the available quota. However, CLM currently has a limitation that it does not distinguish between Windows Server Datacenter edition running on a VM on a host and running directly on a host. As a result, dual use rights is applied the same to both types of deployments even though we know that the software running directly on the host does not qualify for dual use rights. As a result, dual-use rights are applied equally to both deployment types, even though software running directly on the host does not qualify for them. This limitation will be addressed in future releases. |
|
•
|
Cloud Service Providers Settings are checked and qualifying licenses are considered available as long as the On-premises checkbox isn’t the only option selected. |
Tip:CLM interprets any combination of Cloud Service Provider settings as an indication that qualifying licenses can be used in the public cloud. Additionally, licenses are considered available if the Azure Hybrid Benefit option is selected, regardless of the Cloud Service Provider settings. Simply put, a license is only considered unavailable when the On-premises checkbox is the sole option selected.
|
•
|
The resource is marked as Eligible if it is running Windows Server and is not in a Dev/Test subscription.
|
|
•
|
The resource is marked as Not Applicable if it is in a Dev/Test subscription or is not running Windows Server. |
|
•
|
CLM KPI Cards such as BYOL Entitlements Available ITAM and BYOL Entitlements Balance ITAM on the CLM Licenses tab (By Product > Windows Server > Licenses) are updated with the latest available information from ITAM. |
For SQL Server Licenses
|
•
|
Standard and Enterprise edition licenses do not support dual use rights, except for 180 days or for migration purposes. However, CLM currently doesn’t support these exceptions. Therefore, both Standard and Enterprise licenses assigned to on-premises resources are deducted from the available quota for a more conservative estimate. |
|
•
|
Cloud Service Provider settings are checked and qualifying licenses are considered available as long as the On-premises checkbox isn’t the only option selected. |
Tip:CLM interprets any combination of Cloud Service Provider settings as an indication that qualifying licenses can be used in the public cloud. Additionally, licenses are considered available if the Azure Hybrid Benefit option is selected, regardless of the Cloud Service Provider settings. Simply put, a license is only considered unavailable when the On-premises checkbox is the sole option selected.
|
•
|
The resource is marked as Eligible if any of the following conditions is met: |
|
•
|
It is a SQL managed instance that is not in a Dev/Test subscription. |
|
•
|
It is a SQL database configured with the vCore purchasing model that is not in a Dev/Test subscription. |
|
•
|
It is a SQL virtual machine that is not configured as a high availability and disaster recovery replica and is not in a Dev/Test subscription. |
|
•
|
The resource is marked as Not Applicable if any of the following conditions is met: |
|
•
|
It is a SQL database configured with the serverless compute tier. |
|
•
|
It is a SQL database configured with the DTU-based purchasing model. |
|
•
|
It is a SQL virtual machine that uses SQL Server Web, Express, or Developer edition. |
|
•
|
It is a SQL virtual machine configured as a high availability and disaster recovery replica, resulting in no license charges from the cloud provider. |
Note:Discovery for BYOL SQL Server on EC2 and RDS is currently not supported but will be available in future releases.
|
•
|
CLM KPI Cards such as BYOL Entitlements Available ITAM and BYOL Entitlements Balance ITAM on the CLM Licenses tab (By Product > SQL Server > Licenses) are updated with the latest available information from ITAM. |
Daily Reconciliation
By default, ITAM reconciles all changes made to licensing information daily. Therefore, expect approximately a 24-hour delay between updates made in ITAM and the entitlement position you see in CLM.