OBLYTECH Logo
OBLYTECH Logo

Publisher License Reconciliation: Microsoft, IBM and Oracle

Publisher license reconciliation compares the software installed in your estate with the rights your contracts grant, using the counting rules each vendor sets. In ServiceNow Software Asset Management, that means activating the right publisher pack, mapping each product to its license metric, and feeding in usage data so a reconciliation run shows where a position falls out of line.

Why publisher rules change the reconciliation result

Reconciliation sets installed software against entitlements. It runs weekly by default and can also be started on demand for one publisher, one group or one subgroup. Groups and subgroups can follow country, department, company, region or cost center, so a run can show a single business unit’s position without mixing it with the rest.

Each product in the output receives a compliance status and remediation options: creating or removing allocations, removing installs that have no allocation, and removing installs that have no license. Where rights fall short, the same results can drive a purchase order for new licenses.

The engine is shared, but the counting is not. Microsoft products are counted by users, devices, cores, processors and subscriptions. IBM products are counted by processor value units and peak usage. Oracle products are counted by named users, physical devices and physical hosts. For the audit and true-up side of a compliance position, see the license compliance guide.

Activating the publisher pack for each vendor

Publisher packs are plugins that you request from ServiceNow personnel for activation. Each one adds the license metrics for its publisher, and a publisher’s compliance results appear on the publisher dashboards once that pack is active. The Software Asset Management Professional guides cover the wider product set that these packs extend.

Publisher Plugin identifier What the pack adds
Microsoft com.snc.samp.microsoft Microsoft license metrics, including Microsoft SQL Server, and Microsoft 365 subscription tracking
IBM com.sn_samp_ibm PVU and RVU metrics, plus Red Hat Enterprise Linux Server and Red Hat Enterprise Linux for Virtual Datacenters
Oracle com.snc.samp.oracle Reconciliation for Oracle Database and other Oracle software

Activating the Microsoft pack means activating the Software Asset Management Professional for Microsoft plugin (com.snc.samp.microsoft).

Microsoft: matching metrics to how products are licensed

A right is one unit of a license metric that you own, and reconciliation consumes rights against installations. Microsoft’s metrics differ in what they count, so the metric chosen on an entitlement decides the result.

Users, devices and subscriptions

Per User and Per Device are two of the metrics that take a Maximum installs per right attribute on the software model, which sets how many installations one right covers. The metric chosen on the entitlement decides which installations are counted against it.

Allocations are a separate question from installs. Allocated rights that no installation uses appear as Allocated not in use, because the user or device they were allocated to does not have the software installed. When the allocation count looks higher than the install count, check the allocations before questioning the install data.

Cores, processors and client access

Per core metrics count every processor core running SQL Server, Windows Server or one of their components, and each such core must be licensed. The count depends on the core factor table and on whether the server is physical or virtual. Licensing by virtual machine is available only with Software Assurance or a subscription license. Without either, the number of virtual machines you can run equals the number of core licenses assigned to the physical server. The Minimum cores per processor attribute sets a floor on the rights consumed.

Per core (with CAL) metrics must be paired with device or user CAL entitlements created separately. User CAL counts the users in the client access records for the software model, and device CAL counts the devices. Server (per instance) counts installations in each operating system environment, while server (per server) counts unique physical servers. Per processor counts processors that have an installation.

Microsoft 365 usage and reclamation

Microsoft 365 subscriptions are also evaluated for usage, and that usage data drives the optimization recommendations covered below. Microsoft Graph APIs supply desktop, web and mobile activity for Outlook, Word, PowerPoint, Excel, OneNote, Teams, Exchange Online, SharePoint Online and Power BI. SCCM or ACC-V cover desktop usage of Microsoft 365 apps for Enterprise, and Jamf covers macOS devices. Usage for Copilot, Visio Online, Planner and Project can be exported from the Microsoft 365 admin center and uploaded manually.

Results land in two tables. Software Usages (samp_sw_usage) holds total usage and last activity from each collection source. Microsoft 365 Apps Usage Reports (samp_m365_apps_usage_report) holds a per-user true or false flag taken from the APIs, plus a last activity date that helps pick reclamation candidates for Outlook, Word, Excel, PowerPoint and OneNote. A daily job collects the usage, and a weekly job generates the removal candidates.

Four recommendation types come out of this data:

  • Overlapping: two active subscriptions cover the same services, such as Microsoft 365 E3 alongside Office 365 E3. The Office 365 subscription is the one to reclaim.
  • Low usage: a single service, such as Teams or SharePoint, or a whole suite has licensed services that go unused.
  • Consolidation: separate subscriptions merge into one plan, such as Office 365 Enterprise E5, Windows and EMS replaced by a single Microsoft 365 Enterprise E5 subscription.
  • Downgrade: a move to a lower tier when a feature goes unused. No Power BI usage points to E5 to E3, and no desktop usage points to E3 to F3 or E1. The E3 to F3 check also reads mailbox and OneDrive size, and a recommendation follows when both are under two gigabytes.

The reclamation thresholds and exceptions guide covers how the inactivity period that marks a candidate is set.

Entitlements that carry Microsoft 365 changes

A From SA or Add-on entitlement moves an existing Microsoft product away from Software Assurance, or adds rights to it. Set its software model to a Microsoft 365 model and its license type to From SA or Add-on, then publish it. Assign it on the Related Entitlements tab to a target that uses the Per User or Per Device metric, has no other assignment and carries no active allocations. From SA rights must equal the total purchased on the target, while Add-on rights can be any number up to the add-on total.

A reserve entitlement adds licenses to an existing Microsoft 365 subscription. Its monthly unit cost is the source unit cost divided by its duration in months, and that figure feeds true-up cost and reclamation savings. The reserve cost appears in the true-up report after reconciliation. At its end date, the subscription maintenance job creates a replacement entitlement and retires the reserve. The entitlement guide explains the fields these steps depend on, and the software model guide covers the model that these entitlements reference.

IBM: peak usage and the 90-day high-water mark

An IBM License Metric Tool or BigFix Inventory integration imports installation and peak usage data from IBM servers. IBM has deprecated version 1 of those integration APIs. The platform still supports existing version 1 connections, but a first-time setup should use version 2. Connection health checks help resolve problems such as slow response times and invalid hardware serial numbers.

Daily aggregated peak usage shows, for each IBM product, the highest daily sub-capacity and full capacity usage in processor value units, resource value units and virtual processor cores. The view is grouped by edition, license metric and region. Reconciliation then takes the peak over a 90-day period, the high-water mark, and uses it to determine whether the IBM license is in compliance. The high-water mark can also be determined per region, for the Americas, EMEA and APAC. An IBM Cloud Pak is reconciled as one unit, so the programs inside it are not reconciled one by one.

Oracle: which installations count

Oracle reconciliation works out Rights Used By and Rights Needed By figures for named users, physical devices and physical hosts that run Oracle products. Records in the Oracle Options table count when their Considered for licensing field is Yes, and the database option must run on a physical server, a virtual server linked to one, or an end user device such as a computer.

Placement matters. An allocation on a physical host is valid and appears as allocated in use. An allocation on a virtual machine is invalid and appears as allocated not in use. For Oracle database and WebLogic licensing on VMware, one property selects the aggregation level, and another accounts for VM-host affinity rules at the vCenter level. Domain separation lets those properties differ between domains.

Frequently asked questions

How often does publisher reconciliation run?

Reconciliation is a scheduled job, and its default frequency is weekly. It can also be started on demand for chosen publishers, groups or subgroups.

Why does an Oracle allocation show as not in use?

It sits on a virtual host, such as a virtual machine, which the reconciliation treats as invalid. Allocations on a physical host are treated as valid and show as allocated in use.

Which IBM integration version should a new connection use?

Version 2. IBM has deprecated version 1 of the ILMT and BigFix Inventory integration APIs, although existing version 1 connections continue to be supported.

What happens to a reserve entitlement at its end date?

The subscription maintenance job creates a replacement entitlement, and the reserve entitlement is retired. Its cost then leaves the true-up figure.