What is an Additional License Authorization

If you run Micro Focus software now owned by OpenText, the document that governs how you may use it is probably not the one you remember signing. What is an Additional License Authorization? It is the instrument that sets the use rules for most Micro Focus products: the metric that is counted, the unit that defines a single count, and the scope in which the software may run. The order form set the price and quantity. The Additional License Authorization, or ALA, sets the rights, and at audit it is the document that matters most.

This field note explains what an ALA is, why it governs so much of the OpenText estate, and how it shapes audit exposure. It introduces the territory our ALA and entitlement review track defends.

Where ALAs come from

Most Micro Focus products are governed by Additional License Authorizations, and OpenText's portfolio absorbed those products through the Micro Focus acquisition, a $6B transaction that closed on January 31, 2023. That acquisition added security products such as Fortify, ArcSight, Voltage, NetIQ and Sentinel, DevOps products such as ALM, Quality Center, Octane, LoadRunner, UFT, Dimensions and AccuRev, COBOL products including Visual COBOL and Enterprise Server, ITOM products, and analytics. The ALA framework carried those products' use rules into the combined estate.

What an ALA actually contains

An ALA defines the license metric for each product, the unit of measurement, the use scope across production and non production, and the conditions attached to the grant such as territory, virtualization, and standby use. It is part contract and part dictionary, because the capitalised terms it defines control how the grant is read. A finding is only as strong as its fit with these definitions.

Why the ALA decides the finding

Auditors build a finding by measuring deployment and comparing it to entitlement. Both halves of that comparison are defined by the ALA. If the metric is read more broadly than its definition, or the scope is read to capture environments the grant excludes, the comparison produces a shortfall that the contract does not actually support. Because most Micro Focus products sit under ALAs, the ALA is the key trap area in an OpenText audit, and it is where buyer side reading recovers the most ground.

How an ALA based finding goes wrong

The common failures are familiar to anyone who reads these documents for a living: a unit definition stretched past its words, non production environments counted as production, bundled components mismapped, and version entitlement ignored. Each is an interpretive move, and each is reversible by returning to the governing language and the order form.

How the ALA differs from a EULA

Buyers familiar with the OpenText EULA sometimes assume the same terms govern their Micro Focus products. They do not. The EULA governs OpenText's own ECM line, while the Additional License Authorizations govern the acquired Micro Focus catalogue, and the two differ in how metrics are defined, how scope is described, and how remedies are framed. A finding that applies EULA reasoning to an ALA product, or the reverse, is reasoning from the wrong document. Identifying the governing instrument for each product is not a formality; it determines which definitions, which scope language, and which conditions apply to the count.

The conditions buyers most often overlook

Beyond the metric, an ALA carries conditions that frequently favour the buyer: standby and disaster recovery allowances, development and test distinctions that exclude non production use from the production count, and virtualization rules that count assigned capacity rather than whole hosts. Because these conditions reduce exposure, they are easy to forget and easy for a finding to ignore. A complete reading surfaces them, and surfacing them often removes instances the opening number counted in full.

Why reading it first changes everything

The buyer who reconstructs entitlement from the ALA before the vendor runs a measurement script sets the terms of the discussion. Rather than reacting to a finished number, the buyer presents an independent license position that the vendor must then dispute. That reversal of initiative is the single most valuable thing an ALA reading provides, because it moves the burden onto the party asserting the larger figure and keeps the buyer from negotiating against a number it had no part in building.

Reading the ALA before the vendor does

In a recent engagement, simply establishing which regime governed each product, ALA or EULA, removed a layer of the finding that had been built on the wrong rulebook entirely. Our case files show reductions from 70 to 80 percent once the governing terms were read correctly. The lesson repeats across the practice: the document decides the number, so the buyer who knows the document controls the outcome.

What an ALA does not do

It is as useful to know what an Additional License Authorization does not grant as what it does. An ALA does not, on its own, set the quantity purchased; that is the order form. It does not promise unlimited deployment of any product; it bounds use by the stated metric. And it does not silently expand to cover deployment models it never addressed. Reading the ALA for its limits as well as its grants keeps a buyer from conceding obligations the document never imposed, and it keeps an auditor from importing terms the contract does not contain.

Keeping an ALA register

Because the OpenText estate mixes ALA governed and EULA governed products, a buyer benefits from a simple register that records, for each product, which instrument governs it, the metric, the unit, the scope, and the order form quantity. Maintained over time, that register turns an audit from a scramble into a lookup. It also surfaces the products most exposed to a metric or scope dispute, so attention can be directed before a notice ever arrives. The register is the practical embodiment of knowing what an ALA is and where it applies.

The ALA is the buyer's document too

It is easy to think of an Additional License Authorization as the vendor's instrument, but it binds both parties, and its definitions protect the buyer exactly as much as they constrain it. Every limit the ALA places on a metric, every carve out for non production use, and every standby allowance is a right the buyer can assert. The document that the vendor uses to build a finding is the same document the buyer uses to take it apart. Reading it as your own, rather than as something done to you, is the shift in posture that turns an ALA from a source of anxiety into the foundation of a defense.

For the full framework, read the complete OpenText audit defense playbook, and for ALA specific defense see our ALA and entitlement review track. If you are unsure which rules govern your products, open a case.