Resource Consumption

[williamhans]

We have an entitlement that we have marked Resource consumption as we do a manual calculation.   But the model has usage coming in against it and I believe that is causing it to show non compliant in the License Usage views.  It shows installs requiring action, which I believe should be ignored as we again are using Resource Consumption and have applied a Resource value?

Is there any way to rectifiy?

[fknell]

Hi @williamhans,

You’re hitting a known issue in SAM: when an entitlement is marked resource consumption but usage‑based installs are still being calculated against it, the License Usage view can show non‑compliance and “installs requiring action”, even though you intend to ignore those installs in favor of your manual resource‑based calculation.

There are a few options to fix this, depending on your policy:

Stop using the entitlement for install‑based licensing

- In Software Asset Workspace > License operations > Products with installs, open the product and check which entitlements are being used to license the installs.

- If this entitlement is being used there, remove or replace it with another entitlement that is intended for install‑based licensing.

Once the entitlement is no longer used for installs, the installs requiring action for that entitlement should drop or be reassigned elsewhere.

Ignore the installs that should not be licensed by this entitlement

- For installs that should not be licensed by this entitlement, you can:

   - Mark them as Ignored in the License usage view.

   - Or adjust the consumption rule so that those installs are not mapped to this entitlement.

This keeps the entitlement focused on resource‑based consumption and removes the noise from the install‑based view.

Use a separate entitlement for resource‑only usage

- Create a dedicated entitlement for resource consumption and:

   - Do not link it to any consumption rules that map to installs.

   - Use it only for manual resource‑based usage.

- Keep your install‑based entitlements separate and aligned with actual install‑based licensing models.

This is the cleanest long‑term pattern and avoids mixing resource and install models on the same entitlement.

Hope this helps!