How to read a Micro Focus Additional License Authorization

When an OpenText compliance notice references your Micro Focus Additional License Authorization, the document it points to is rarely the one most buyers think they signed. The order form set the commercial terms. The Additional License Authorization, or ALA, set the rules of use. Learning how to read a Micro Focus Additional License Authorization is the single most useful skill a buyer can develop before an audit, because the auditor will read it the way that maximises the finding, and the only counterweight is a buyer who can read it the way the words actually permit.

This field note walks through the structure of an ALA, the clauses that decide the size of a finding, and the order in which to read them when a notice is already on the table. It pairs with our ALA and entitlement review track, where we apply this same reading to live engagements.

Start with the product entry, not the preamble

Every ALA opens with general terms that apply across the catalogue, but the figure in a finding almost always turns on the product specific entry further down. Find the named product first. For each product, the ALA states a license metric, a unit of measurement, and a use scope. Read those three things together before you read anything else, because the auditor will quote them out of sequence to build a number, and sequence is where meaning lives.

The metric tells you what is counted. The unit tells you how a single count is defined. The scope tells you where and how the software may run. A finding that counts the right metric against the wrong unit, or the right unit in the wrong scope, is a finding built on a misreading, and misreadings are reversible.

Pin down the license metric word by word

Micro Focus metrics are precise and they do not travel between products. A named user under one product is not a named user under another. A core based metric on one engine is not the core metric on a different engine. When you read a Micro Focus Additional License Authorization, treat each defined term as a closed definition that applies only where the ALA places it. Auditors gain ground when a buyer assumes a metric means what it means colloquially. The ALA is a dictionary as much as a contract, and the definitions section governs the grant.

Read the use scope as a boundary, not a footnote

Scope language decides whether non production environments, disaster recovery instances, and standby systems count against your entitlement. Many ALAs distinguish development and test use from production use, and many grant standby rights that an auditor will overlook unless the buyer raises them. The scope clause is where decommissioned systems, dormant accounts, and cold environments either inflate a finding or fall out of it. Reading scope carefully is how a buyer recovers entitlement that the opening number ignored.

Trace the grant through versions and time

An ALA grants rights to a product at a defined version and for a defined term. Version entitlement and term entitlement are separate questions, and both shape exposure. A perpetual grant behaves differently from a subscription grant at audit, and an upgrade right can change which version the metric attaches to. When you read the document, mark every date, every version reference, and every renewal clause, because the auditor will assemble these into a timeline and the buyer needs the same timeline to test it.

Compare the ALA against the order form

The ALA states the rules. The order form states the quantities and the commercial commitment. A finding is only credible where both agree. In many engagements the gap between what the order form purchased and how the ALA defines a unit is exactly where the opening number overreaches. Reading the two side by side, line for line, is the foundation of any rebuttal.

Read the conditions that sit outside the metric

A grant is shaped by more than its metric. Territory clauses limit where the software may be deployed, virtualization and partitioning clauses decide how cores and processing units are counted on shared hardware, and disaster recovery and standby clauses determine whether a cold instance draws a license. Buyers who read only the metric line miss the conditions that frequently work in their favour. A standby system that processes nothing, a partition that the ALA counts in place of the host, or a deployment inside a permitted territory can each remove instances an auditor counted as in scope. Read these conditions as actively as the metric, because they are where entitlement is recovered rather than merely defended.

Mark the support and maintenance terms

Support status interacts with the grant in ways an auditor will use. Lapsed maintenance affects the right to updates and assistance, but it does not automatically extinguish the right to run a version already deployed under a valid grant. When you read the ALA, separate the support obligation from the use grant, and record the maintenance coverage in force at each deployment. That record answers a finding that treats expired support as if it removed the underlying license, a conflation that surfaces in many engagements.

Build a working summary as you read

The practical output of reading an ALA is a one page summary per product: the metric, the defined unit, the scope, the version entitlement, the term, and the conditions. With that summary beside the order form and the deployment record, a buyer can test any finding in minutes rather than weeks, and can see immediately where the auditor's number departs from the governing text. This summary is the backbone of an entitlement reconstruction, and it is the document we build first in every engagement.

What a careful reading changes

In a recent engagement we worked through a finding that rested on a single metric definition read in isolation. Once the product entry, the definitions section, and the scope clause were read together against the order form, the basis for roughly two thirds of the claimed shortfall disappeared. The pattern is consistent across our case files: E-01 settled at a 78 percent reduction, E-02 at 80 percent, and E-03 at 70 percent, and in each the first move was a disciplined reading of the governing terms.

For the full method behind this work, see the complete OpenText audit defense playbook, and for how we apply it to Micro Focus products specifically, see our ALA and entitlement review track. If a notice is already on your desk, open a case and we will read the document with you.