Micro Focus ALA versus OpenText EULA scope

A single audit can touch products governed by two entirely different contractual regimes, and confusing them is one of the easiest ways for a finding to apply the wrong terms. Micro Focus ALA versus OpenText EULA scope is the question of which document governs which product, and the answer shapes every metric, condition, and remedy that follows. Before any count is accepted, a buyer should know which regime the product actually sits under.

This field note explains the two regimes, which products fall under each, and why the distinction changes how a finding must be read. It pairs with our ALA and entitlement review track.

Two regimes under one vendor

OpenText today governs products through more than one contractual framework. Its own enterprise content management line, including Documentum, Extended ECM, Content Suite, eDOCS, and InfoArchive, predates the Micro Focus acquisition and is governed by the OpenText end user license agreement. The products that arrived with the Micro Focus acquisition are, for the most part, governed by Additional License Authorizations, the definitional documents that explain each metric. One vendor, two regimes, and a finding that ignores the boundary risks applying the wrong terms to the wrong product.

What the OpenText EULA controls

The OpenText end user license agreement governs the content management estate and carries the structural terms a buyer must reckon with in any audit: the seven days notice before an audit and the right to copy relevant records, the statement that compliance is the sole responsibility of the licensee, and the remedy that on noncompliance the licensee is deemed to have acquired licenses at then current list price, with back maintenance, first year maintenance on the new licenses, and reimbursement of the costs of the audit. These are the terms that frame an ECM finding, and they sit in the EULA rather than in an authorization.

What the Micro Focus ALAs control

For the acquired catalogue, which spans security products such as Fortify and ArcSight, DevOps tools such as ALM and LoadRunner, and COBOL products such as Visual COBOL and Enterprise Server, the Additional License Authorizations carry the metric definitions. The authorization is where a unit such as a developer seat, an events per second figure, or a core count is given its precise meaning. A finding on one of these products must be read against the governing authorization, not against the EULA terms that govern the ECM line. Reading the authorization correctly is the subject of how to read a Micro Focus Additional License Authorization.

Why the acquisition created the divide

The Micro Focus acquisition closed in early 2023 and added a very wide catalogue across security, DevOps, COBOL, IT operations, and analytics. Because these products carried their own licensing documents into OpenText, they did not simply fold into the existing EULA. The result is an estate where the governing regime depends on the product's origin. A buyer with both an ECM deployment and an acquired Micro Focus product holds entitlements under both regimes at once, and an audit that crosses both must apply each regime to its own products.

Where findings cross the boundary

The expensive error is applying one regime's logic to the other regime's product. An auditor who reads an ECM product as though an authorization metric governed it, or who reads an acquired product as though the EULA alone defined its unit, produces a count the actual governing document does not support. The defense identifies which regime governs each product and requires that the finding be read against the correct one. Because the two regimes define units and conditions differently, correcting a misattributed product can move a finding line substantially.

How we sort the estate

The defense begins by separating the estate by governing regime: ECM products to the EULA, acquired Micro Focus products to their authorizations. We then reconstruct the entitlement for each product against the document that actually governs it, the Reconstruct step in our method. This sorting is foundational, because a count built on the wrong regime cannot be corrected by adjusting figures; it has to be rebuilt on the right document. In a recent engagement, separating a mixed estate by regime before examining any count clarified which terms applied to which product and removed a category of inflation that arose purely from misattribution, a correction consistent with the kind of result reflected in our E-01 case file, where a Documentum seat count finding moved from $7.2M to $1.6M, a 78 percent reduction.

The remedy reads the same, the metric does not

A useful clarification for buyers is that the structural remedy, the deemed acquisition at list price with stacked maintenance and audit costs, frames findings across the estate, but the metric that produces the shortfall is regime specific. The EULA frames the ECM remedy; the authorization defines the acquired product's unit. Confusing the two leads buyers to argue the remedy when the real error is in the metric, or the reverse. Keeping the remedy question and the metric question separate, and attaching each to the document that controls it, is what lets a defense correct the right layer rather than the convenient one.

Why the distinction protects the buyer

Knowing which regime governs a product is not a technicality; it is leverage. A buyer who can show that a finding applied authorization logic to an EULA product, or EULA logic to an authorization product, has identified an error of contract rather than an error of degree. That kind of error is correctable on documents the vendor itself relies on, which is far stronger than disputing a judgment. The boundary between the two regimes is therefore one of the first things worth establishing in any mixed estate audit, because everything downstream depends on getting it right.

Closing the regime question forward

When a finding has been corrected to apply each regime to its own products, the forward agreement should record which products sit under which regime and how each metric is defined. Writing the regime boundary into the forward terms removes the ambiguity that let the audit cross it, so the next review begins from a clear allocation rather than a contested one. Resolving the present finding and fixing the regime boundary in the forward agreement are two halves of the same work, and completing both keeps the boundary from becoming a recurring source of dispute.

For the full method, read the complete OpenText audit defense playbook, and for entitlement defense across the Micro Focus estate see our ALA and entitlement review track. If your audit crosses both regimes and you are unsure which governs which product, open a case.