IBM is making important changes to its sub-capacity licensing eligibility rules in 2026. From 31 December 2026, Windows Server 2016 and Red Hat Virtualisation will no longer appear on IBM’s list of eligible technologies.
For organisations running IBM software in these environments, the changes could have significant implications for software licensing, compliance and infrastructure costs.
IT Asset Management (ITAM), Software Asset Management (SAM) and procurement teams should understand how the changes could affect their licensing position and what action they need to take before the deadline.
Taking action now can help organisations avoid unexpected IBM licensing costs, maintain compliance and make informed infrastructure decisions.
What Are the IBM Sub-Capacity Licensing Changes in 2026?
Sub-capacity licensing allows you to license eligible software at virtual capacity. This means that you license the virtual cores that run the software within each virtual machine, rather than all of the physical cores of the servers hosting the VMs. Think of IBM software licensing like buying a cake. With full-capacity licensing, you could be paying for the entire cake, even if you only want one slice. With sub-capacity licensing, you only pay for the slice you actually need. IBM is removing Windows Server 2016 and Red Hat Virtualisation from its list of technologies that IBM currently accepts for sub-capacity licensing on 31 December. Sub-capacity licensing allows organisations to license eligible IBM software according to the processor capacity available to the virtual machine or partition running the software, rather than automatically licensing the full physical capacity of the underlying server.
This can provide significant licensing efficiencies in virtualised environments. However, those benefits depend on meeting IBM’s eligibility, licensing and reporting requirements.
For organisations currently relying on either technology, the December deadline is an important opportunity to review their IBM licensing position and determine whether infrastructure changes or an approved migration plan will be required.
IBM publishes a list of operating systems and virtualisation technologies that organisations must use to qualify for sub-capacity licensing. IBM places responsibility for maintaining sub-capacity licensing compliance on the customer. When a technology reaches the end of its vendor’s standard support, IBM can announce plans to remove that technology from its eligibility list.
The two technologies affected by the December deadline are:
- Windows Server 2016: IBM has scheduled its removal from the sub-capacity eligible technologies list for 31 December. This is separate from Microsoft’s product support timeline, with extended support for Windows Server 2016 ending on 12 January 2027.
- Red Hat Virtualisation: This reached the end of standard support on 31 August.
The removal means that these technologies will no longer qualify as standard eligible environments for IBM sub-capacity reporting after the deadline.
Which IBM software environments could be affected by these changes?
Organisations could face licensing implications if they run eligible IBM software on Windows Server 2016 or Red Hat Virtualisation.
The level of exposure will depend on the software deployed, the underlying infrastructure and whether the organisation currently relies on sub-capacity licensing.
It is important to look beyond the software inventory and assess how IBM deployments connect to the wider IT environment.
Organisations should identify:
- IBM software installations running within Windows Server 2016 operating systems.
- IBM workloads running on Red Hat Virtualisation
- Virtual machines and partitions where IBM software is deployed.
- Physical servers hosting affected virtualised workloads.
- Existing IBM sub-capacity licensing arrangements and associated reporting.
Products using IBM licensing metrics such as Processor Value Unit (PVU), Resource Value Unit (RVU MAPC) and Virtual Processor Core (VPC) may be eligible for sub-capacity licensing, subject to the relevant product and environment requirements.
A comprehensive IBM software inventory, supported by accurate infrastructure and licensing data, is therefore essential.
One challenge for larger organisations is that IBM software deployments may be spread across multiple business units, data centres and infrastructure teams. With large estates like these, affected environments can easily be overlooked.
Bringing together software discovery, infrastructure information and license entitlement records can help ITAM teams establish where the risks sit and prioritise the necessary reviews.
What Happens If You Continue Using Windows Server 2016 or Red Hat Virtualisation?
If an organisation continues using either technology after 31 December 2026, it may no longer qualify for IBM sub-capacity licensing in the affected environment.
Where an organisation cannot meet IBM’s sub-capacity eligibility requirements, it will have to license the software based on the full physical processor capacity of the server rather than the virtual capacity allocated to the IBM software.
This could significantly increase licensing costs, particularly when organisations run IBM software in lightly virtualised environments.
For example, an organisation running IBM software within a virtual machine allocated a relatively small number of processor cores may currently benefit from sub-capacity licensing. If the environment becomes ineligible and no approved migration arrangement applies, the licensing calculation will instead be based on the full capacity of the physical server.
The financial implications could include:
- Increased IBM processor licensing requirements.
- Additional license expenditure.
- Unbudgeted compliance costs.
- Greater exposure during an IBM licensing audit.
- Pressure to accelerate infrastructure migration plans.
However, organisations should be aware that IBM provides a specific migration process for customers who want to continue using sub-capacity licensing while moving away from an ineligible technology. Under the relevant Passport Advantage1 terms, customers must submit a migration plan and obtain IBM’s approval. During an approved migration, organisations must maintain the appropriate version of ILMT and continue generating reports. IBM must also provide prior written consent before organisations use any permitted manual tracking arrangements.
Organisations should not assume IBM automatically grants a grace period. They need to understand and follow the relevant approval requirements rather than assume that their existing licensing arrangements will continue unchanged.
How to Maintain IBM Sub-Capacity Licensing Compliance
Organisations should assess their IBM licensing and infrastructure before the December deadline to identify affected deployments, check reporting arrangements and establish whether they need to migrate.
There are five important areas to consider.
1. Review your IBM software estate
Identify all IBM software deployments and establish which are running on Windows Server 2016 or Red Hat Virtualization. Confirm whether these installations currently rely on sub-capacity licensing.
2. Review ILMT reporting
IBM License Metric Tool (ILMT), or an approved alternative, is a mandatory requirement for most sub-capacity licensing arrangements.
Ensure the tool captures relevant software deployments and processor capacity, and generates accurate reports.
Review reporting gaps, unsupported environments and inconsistencies that could affect your licensing position.
3. Assess your infrastructure options
Determine which affected environments your organisation can migrate to eligible operating systems or virtualisation technologies.
Consider the technical, operational and financial implications of each option, including the time required to plan and complete migrations.
4. Review your IBM license entitlements
Compare your current IBM software usage and sub-capacity reporting against your existing license entitlements.
Understand the potential licensing impact if affected environments move to full-capacity licensing. This will help establish whether additional licenses may be required and allow finance and procurement teams to plan accordingly.
5. Establish a migration and compliance plan
Agree responsibilities across ITAM, infrastructure, procurement and finance teams. Set clear deadlines for reviewing affected environments, obtaining any necessary IBM approvals and completing planned migrations.
How can organisations prepare for the December deadline and avoid unexpected IBM licensing costs?
IBM’s sub-capacity licensing changes highlight the importance of keeping software licensing and infrastructure decisions aligned. Organisations that fail to review their environments before the December 2026 deadline could face increased licensing costs and additional compliance risks.
Reviewing your IBM software estate, checking ILMT reporting and understanding your migration options now can help you avoid unnecessary expenditure and maintain control of your licensing position.
Organisations should also involve the right stakeholders early. ITAM and software licensing teams need to work alongside infrastructure, procurement, finance and technology leadership to ensure that decisions are made with both technical and commercial considerations in mind.
For organisations that cannot complete migration before the deadline, understanding IBM’s migration approval process is particularly important.
Ultimately, the changes are a reminder that infrastructure decisions can have direct consequences for software licensing. A change to an operating system or virtualisation platform can affect an organisation’s ability to benefit from sub-capacity licensing and potentially increase its IBM software costs.
Taking a proactive approach will help organisations maintain visibility of their IBM software estate, reduce compliance risks and avoid unnecessary expenditure.
At bedigital, we help organisations improve software visibility, optimise licensing and strengthen technology cost management. If you’re looking at your IBM License management, understanding what you have, what you’re using and what you’re paying for is a good place to start.
- effective 1st February 2027, Passport Advantage terms for sub-capacity licensing will become the Attachment for Virtulisation Licensing to the IBM Customer Relationship Agreement ↩︎


