Micro Focus bundling and the ALA license trap

Bundling sells software efficiently and audits it badly. When a buyer purchases a suite, the commercial paperwork shows one line and one price, but the underlying Micro Focus bundling hides several distinct grants, each governed by its own Additional License Authorization terms. The gap between the single purchased line and the many governed components is the ALA license trap, and it is where a finding inflates without anyone deciding to inflate it.

This field note explains how bundles obscure entitlement, the two opposite ways an auditor exploits a bundle, and how to reconstruct the true grant. It connects to our ALA and entitlement review track.

What a bundle actually grants

A bundle is a commercial wrapper around component products. Each component carries a metric, a unit, and a use scope under the ALA, and those terms do not vanish because the products were sold together. The wrapper sets the price and the quantity; the ALA sets what each component permits. A buyer who reads only the wrapper sees a single entitlement. An auditor who wants a larger number can read the components either too generously for the vendor or too narrowly for the buyer, depending on which serves the finding.

Trap one: the bundle treated as unlimited

The first trap reads the bundle as if every component carried full, independent use rights at the bundle quantity. A buyer who deployed one component heavily may be told the heavy use is uncovered because the bundle entitlement applied to a different metric than the one being measured. The defense is to return to the component ALA terms and show what each part actually granted, rather than accepting a blended reading that no single clause supports.

Trap two: the component treated as outside the grant

The opposite trap treats a deployed component as if it were never licensed, because it does not appear on the order form as a separate line. Bundles routinely include components that are entitled through the suite even though they carry no standalone line. An auditor who counts such a component as wholly unlicensed produces a shortfall out of an entitlement the buyer already holds. The defense is to map every component back to the bundle definition and the ALA.

Reconstructing the true entitlement

Unwinding a bundle is an entitlement reconstruction exercise. We list every component the suite contains, attach the governing ALA terms to each, and reconcile that against deployment and against the order form quantity. The result is a defensible map of what was purchased, what it permits, and where actual use sits inside or outside that grant. That map replaces the auditor's blended assertion with a clause backed position.

Why bundles age badly at audit

Bundles are sold for a moment in time, but they are audited years later, often after the vendor has begun selling the same components separately. When a component that once travelled inside a suite is later offered as a standalone product, an auditor may price the buyer's deployment as if it had always been standalone, ignoring the suite grant that actually covers it. The passage of time and the evolution of the price list do not narrow a grant that was made at purchase. The buyer's protection is the original bundle definition, which fixes what the suite included regardless of how the catalogue later changed.

Mixed metrics inside one suite

A single bundle can contain components measured by different metrics: one by named user, another by capacity, a third by volume. An auditor who applies one component's metric across the suite, or who measures a component on a metric the bundle never assigned to it, produces a finding that no clause supports. Reconstructing a bundle means attaching the correct metric to each component and measuring each on its own terms. The discipline is unglamorous, but it is where blended findings come apart.

The order form is the anchor

However a bundle is read, the order form anchors the entitlement. It records what was purchased and at what quantity, and the ALA records what each purchased component permits. A finding that cannot be reconciled to both documents is asserting an obligation the buyer never accepted. We treat the order form and the component ALA terms as the two fixed points of any bundle defense, and we map every disputed component back to them before conceding a single unit.

What the reconstruction recovers

In a recent engagement involving a security and DevOps suite, a finding rested on the assumption that one heavily used component sat outside the bundle. The component level ALA showed it was entitled through the suite, and a substantial portion of the claimed shortfall fell away. The case files in our practice tell the same story: findings that looked solid at the bundle level dissolved once each component was read on its own terms, with reductions of 70 percent and more.

Bundles and forward conversion

A bundle finding is also an opportunity to fix the underlying ambiguity for good. When a dispute is resolved, the forward agreement can name each component explicitly, state the metric that governs it, and record the entitlement that travels with the suite, so the next review cannot replay the same blended reading. Converting a contested bundle into a clean, component level entitlement on the buyer's terms is the durable outcome, because it removes the very obscurity that produced the finding. Resolving the present claim and closing the gap that created it are the same piece of work.

Inventory before the vendor measures

The strongest bundle defense begins before any notice arrives, with an inventory that maps every deployed component to the suite that entitles it. A buyer who can produce that map on demand does not have to accept the auditor's reconstruction; it can present its own. Where the inventory predates the audit, it carries additional weight, because it reflects how the estate was actually understood and administered rather than a position assembled under pressure. Building that inventory is among the highest value preparations a buyer can make.

Treat every bundle line as a question

The practical habit that protects a buyer is to treat every bundle line on an order form as an open question rather than a settled fact. What components does it contain, what metric governs each, what scope applies, and how does the deployment map onto those terms? A buyer who can answer those four questions for each suite holds the entire bundle defense in advance, and never has to accept an auditor's blended reconstruction at face value. The questions are simple; the discipline of asking them before a notice arrives is what turns a vulnerable estate into a defensible one.

For the full approach, see the complete OpenText audit defense playbook, and for product specific defense see our ALA and entitlement review track. If a bundle sits at the centre of your finding, open a case.