Licensing IBM software in managed service provider environments.

Who actually holds the entitlement.

The first question in any MSP audit is whose entitlement covers the deployment. In some arrangements the customer brings their own licenses and the provider supplies only the hardware. In others the MSP licenses on the customer's behalf under its own agreement. The two models carry very different obligations, and confusion between them is a frequent source of double counting, where neither party can produce a clean entitlement record for the period under review.

Shared hosts magnify the capacity question.

MSPs run dense, multi-tenant infrastructure. If your IBM workload sits on a shared cluster and sub-capacity cannot be proven, the full-capacity default applies to capacity you do not control and may not even be able to see. Worse, the provider's other tenants can inflate the apparent reachable capacity. The cluster capacity logic that governs VMware and containers applies here too, except the environment is operated by a third party whose reporting discipline you have to rely on.

• Confirm which party is contractually responsible for ILMT deployment and reporting
• Establish whether sub-capacity eligibility was maintained on the shared hosts
• Map your workload's reachable capacity, separate from other tenants
• Check that quarterly reports for your scope were retained for two years

The contract decides the exposure.

What protects you in an MSP audit is the language in the hosting agreement: who must maintain the licensing tool, who keeps the quarterly reports, who indemnifies whom if a finding lands. Where the contract is silent, IBM will pursue the party named on the entitlement, which is usually the customer. The defense often turns on producing the provider's reporting records and reading the responsibility split precisely, rather than on the licensing metric itself.

What this means under audit.

An MSP audit is a containment problem before it is a calculation problem, which places it at the front of Contain, Reconcile, Challenge, Settle. Containing means controlling what the provider hands to IBM on your behalf and confirming the contractual responsibility split before any data moves. Reconciling means rebuilding your scope out of a shared environment you do not operate. Done properly, the claim narrows to the capacity that was genuinely yours, on the periods the evidence actually supports.