Subscription and Maintenance Entitlements

Ursula Smith
Tera Contributor

3 weeks ago

My client is currently unable to enter device or user allocations for their Maintenance entitlements. (Confirmed this as well in ServiceNow Documentation). To by pass this limitation, we are considering changing these license types to subscription within ServiceNow. After reviewing the links attached, there are a few questions we have:

1.) Will changing the license type from Maintenance to Subscription cause any underlying technical issues or calculation errors within the ServiceNow SAM?

2.) How will this change impact standard client compliance reporting and dashboards?

3.) Are there better practices for handling user/device allocations for maintenance contracts without changing the entitlement type?

 

Create maintenance entitlements in workspace • Zurich IT Asset Management • Docs | ServiceNow

 

Any insights or other documentation links on how the system processes these two types differently would be greatly appreciated!

0 Helpfuls
  • 634 Views
1 REPLY 1

ayushraj7012933
Mega Guru

3 weeks ago

Hi @Ursula Smith ,

I would not recommend changing Maintenance entitlements to Subscription entitlements just to enable user or device allocations.

Recommended Approach

Keep the entitlement type as Maintenance and manage the maintenance agreement according to its contractual purpose (support and upgrade rights for perpetual licenses). Changing the entitlement type may lead to inaccurate compliance calculations and reporting because Subscription and Maintenance entitlements are evaluated differently by SAM.

Regarding Your Questions

1. Technical Impact

Yes, changing the entitlement type can affect how ServiceNow calculates license positions and entitlement consumption. The entitlement should always reflect the actual contract type purchased from the software publisher.

2. Compliance Reporting Impact

Compliance dashboards and reconciliation results may become inaccurate because the system will treat the entitlement as a subscription license rather than maintenance coverage. This can create discrepancies during audits and renewals.

3. Best Practice for User/Device Tracking

If user or device visibility is required:

  • Keep the entitlement as Maintenance.
  • Track associated users/devices through related software installations, assets, or custom reporting.
  • Use software models, contracts, and asset relationships to identify covered devices.
  • If the requirement cannot be met through OOTB functionality, consider a lightweight customization rather than changing the entitlement type.

Maintain the entitlement as Maintenance and avoid reclassifying it as Subscription. If user/device allocation for maintenance rights is a business requirement, I would recommend raising an enhancement request with ServiceNow or opening a support case to discuss supported alternatives.

Hope this helps.

Regards,
Ayush Raj

0 Helpfuls