I am current getting this banner when i create Entitlement, has anyone been getting this? and do you know how too fix it?. You are creating an entitlement for a subscription product that has no integration profile defined. You will not be able to tra

[Abby Hamdan]

I am current getting this banner when i create Entitlement, has anyone been getting this? and do you know how too fix it?. You are creating an entitlement for a subscription product that has no integration profile defined. You will not be able to track usage activity or reclaim stale subscriptions.

[Community Alums]

Hi Abby!

In order to be able to manage your compliance, you need 2 pieces of information for the calculation:

1) What you own (what/how many entitlements have you purchased) and

2) What is being used

You are currently populating the "What you Own" portion of the calculation, and are entering this entitlement with a License type of Subscription. This means that in order for you to have the second half of the compliance calculation ("What is being used") you need to be able to pull in the subscription usage information from somewhere. The message from ServiceNow is advising that no such integration for the subscription usage has been set up yet. Until the time where you have that integration and are pulling in the subscription usage data, this will show as compliant, and is solely based on whatever manual allocations you are adding to the entitlement.

Hope that helps!

[Aaron Munoz · Accepted solution]

That message will show up every time you select a software model in your entitlement if two conditions apply:

1) The software model you selected has a product where the field "Subscription Software" is set to true:

2) There are no records related to that software model in table Software Subscriptions [samp_sw_subscription]:

The recommended way to populate that table is to leverage an out-of-box connection if available from the SAM Pro publisher packs. For example, pulling data for Microsoft subscriptions can be imported directly with an Azure integration which is documented in the Docs site.

[Abby Hamdan]

Thank you! this seems to have fixed the issue.