SAM Pro and Compliant status in the License usage
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-23-2024 05:14 AM
Dear SAM Community,
Is there a way to get the Compliant flag aligned with the reality of the usage? The below example returns a no compliant flag despite the fact the product is compliant.
Publisher: Microsoft / Product: any, for the example Office 365 / Enterprise E1
License owned = 100, License required = 90, remaining = 10 --> expected to have a Compliant flag set to green in place of Not Compliant red one. There are several Installs requiring action which should not have any impacts on the Compliant calculation based on the Microsoft EA, so why the flag is red?
And is the best-practice to report to C-Level a Compliance report since it seems that it cannot be done directly in the tool? Is the Software License Compliance position report is the recommended way to share a status after exporting the data and recalculate the delta between licenses owned and required?
- Labels:
-
sam_ric
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-23-2024 01:07 PM
Hi @Lionel Falk,
"Works a designed" - it is required to solve all "Installs requiring action" items to change the status to "Compliant". Please check the mentioned reasons and solve them based on the description/best practices given by ServiceNow (open each reason to get details about it).
Could you please add the following columns to your report and see if the outcome (delta) is a expected (all columns with "Rights ..."
Best, Dennis
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-26-2024 11:54 PM
Hi @dreinhardt
Thank you for having confirmed this is "working as designed".
The colons have been added, and for staying on O365 E1 example, the report shows 2 lines (below), both "Not Compliant". Will it be correct in term of compliance standpoint to change (in the report exported) the "Software model status" from "Not Compliant" to "Compliant" when "Rights needed" = 0. And will it be aslo applicable for other Microsoft SaaS products?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-27-2024 01:08 PM
Hi @Lionel Falk
could you please check the following note about the license position report about the line results based on the license metric - this should answer your question. Software license compliance position (servicenow.com). For O365 E1, I would expect one line item, as the common license metric is subscription based ... from what I've seen in my projects.
Two license metric results are generated if a software model has two entitlements, one with a perpetual SA license type and the other with a subscription license type. One license metric result where active maintenance is true and the other where the active maintenance is false. In such a scenario, two license position reports are generated, one with active maintenance true and the other one with active maintenance false.
A single license position report is generated if there are any unlicensed installations. A single license position report is also generated if there are any unlicensed subscriptions. If both are present, two license position reports are generated.
Will it be correct in term of compliance standpoint to change (in the report exported) the "Software model status" from "Not Compliant" to "Compliant" when "Rights needed" = 0. And will it be aslo applicable for other Microsoft SaaS products?
As a temporary workaround, yes this could be a "solution". As mentioned in my previous posting, I would recommend to solve all actions identified by SAM Pro. You second line item looks like a software model without a linked entitlement or not yet fully normalized discovery models (20k is close to your O365 18k).
Best, Dennis