What Oracle GLAS is
Oracle GLAS, which stands for Global Licensing and Advisory Services, is the Oracle organisation responsible for verifying that customers use Oracle programs within their entitlements. It is the function that designs and runs the measurement process, interprets the output against the contract, and produces the compliance findings that become the basis for a settlement or a remediation purchase. When a customer receives a formal audit notification or a request to participate in a licensing review, GLAS is usually the function behind it.
Understanding GLAS matters because the function has a defined role and a defined incentive, and responding well depends on recognising both. GLAS exists to surface licensing gaps and quantify them; its work feeds directly into Oracle's revenue, whether through a compliance purchase, a backdated support charge, or a renewal negotiated from a position of identified exposure. None of this makes GLAS adversarial in tone, its representatives are often courteous and technical, but it does mean the customer should treat a GLAS engagement as the opening of a structured compliance process rather than a neutral conversation.
The mechanics of that process, the scripts, the data requests, the reconciliation, are covered in the LMS audit process guide, which applies directly to GLAS because GLAS is the same function under a newer name. This article focuses on what GLAS is, how it relates to the rest of Oracle, and how a customer should position itself when GLAS makes contact.
GLAS and the legacy of LMS
For most of the period that Oracle has been auditing customers, the compliance function was called License Management Services, or LMS. Over time Oracle reorganised and rebranded this function as Global Licensing and Advisory Services. The change of name introduced an advisory framing, positioning the team as a source of guidance rather than purely an enforcement arm, but the underlying objective, measuring deployments and identifying shortfalls, is continuous across the two eras.
This continuity is practically important. The scripts GLAS uses to measure usage are the descendants of the LMS scripts; the data they collect is the same kind of data; and the way findings are constructed and presented follows the same logic. A customer that has prepared for an LMS audit is prepared for a GLAS review, and the extensive body of practice around LMS audits, including the disciplines in the audit defence pillar, transfers without modification.
The name changed from LMS to GLAS and the framing softened toward advice, but the function still exists to find licensing gaps and convert them into revenue. Read the substance, not the label.
The advisory framing does, however, change the customer's experience at the margin. GLAS may approach as an offer to help the customer optimise or clarify its licensing, which can feel less confrontational than a formal audit letter and can lower a customer's guard. The data gathered in a friendly advisory review is no less capable of producing a finding than the data gathered in a formal audit, which is why the soft engagement deserves the same care, a theme developed in the soft audit guide.
How GLAS differs from sales
GLAS and the Oracle sales account team are distinct functions with distinct roles, and the distinction is useful to the customer. The account team sells licences, cloud, and support and owns the commercial relationship; GLAS measures compliance and produces findings. In practice the two coordinate, and a GLAS finding frequently lands on the account team's desk as leverage in a renewal or expansion negotiation, but they are not the same people and they do not have the same remit.
Recognising the separation helps the customer route conversations correctly. Technical and measurement questions belong with GLAS and should be handled under the audit process; commercial questions about price, bundling, and renewal belong with the account team and should be handled as a negotiation. Letting the two blur, for example allowing a GLAS finding to slide directly into a sales conversation without first being tested as a finding, hands Oracle an advantage, because it converts an unproven measurement into a commercial starting point before the customer has challenged it.
| Dimension | GLAS | Sales account team |
|---|---|---|
| Primary role | Measure compliance and produce findings | Sell licences, cloud, and support |
| Trigger | Audit notification or licensing review | Renewal, expansion, new project |
| Customer counterpart | Response team and SAM under the audit process | Procurement and IT in a negotiation |
| What to control | Data, scope, and the proof of findings | Price, terms, and timing of the deal |
The customer's discipline is to keep these tracks separate and to ensure a finding is fully tested on the GLAS track before it is allowed to influence the commercial track. A finding that survives that test is a real number; a finding that does not should never reach the negotiation as if it were settled.
What a GLAS engagement involves
A GLAS engagement typically opens with contact, formal or advisory, followed by a request for deployment information and, in most cases, a request to run measurement scripts across the in scope estate. GLAS then reconciles the output against the customer's entitlements and produces a draft finding, a statement of where it believes usage exceeds what the customer has licensed. The customer reviews and disputes that draft, and the process moves toward either a clean bill, a remediation purchase, or a negotiated settlement.
Throughout, the data the customer provides is the raw material from which findings are built, which is why data discipline is central. Providing more than the in scope programs require, or running scripts whose output the customer has not first reviewed, hands GLAS information it can use to expand the finding. The principles for controlling this are set out in the data minimisation guide, and they apply whether the engagement is badged as a formal audit or a friendly review.
A GLAS engagement also has a tempo that Oracle prefers to set, and the customer is entitled to a reasonable, contract governed pace instead. The notice and disruption provisions of the audit clause support a measured cadence, and the customer should use that to ensure each step, data provision, measurement, reconciliation, is done carefully rather than rushed to Oracle's schedule. For organisations that want a specialist to manage the GLAS relationship end to end, the Oracle audit defence service handles the engagement from first contact, and the audit defence white paper documents the method.
How should you respond to GLAS?
The first response to GLAS contact is to slow down and route it correctly: acknowledge the contact professionally, convene the response team, and treat the engagement as a compliance process to be managed rather than a conversation to be had casually. Whether GLAS frames its approach as an audit or as advisory help, the substance is the same, and the customer should apply the same discipline to both, controlling scope, controlling data, and insisting that any finding be proven against the contract.
The second response is to build an independent position. GLAS will produce its own measurement, and the only way to test it is to hold a measurement of your own, assembled with independent tooling and interpreted against the contract definitions. Without that, the customer is reduced to accepting or vaguely disputing GLAS's numbers; with it, the customer can challenge specific elements with evidence. This is the readiness posture described across the audit defence cluster, applied at the moment GLAS makes contact.
The third response is to keep the commercial track in check. A GLAS finding will eventually meet the account team, and the customer should ensure it arrives there as a tested, possibly reduced number rather than as Oracle's opening figure. The opening weeks of this whole sequence are covered in the notification response guide, which sets out how to acknowledge, scope, and prepare without conceding anything prematurely.
The buyer side view
GLAS is the engine room of Oracle compliance, the function that measures, reconciles, and produces the findings that drive settlements and renewals. It is the same team that was once called LMS, now wearing an advisory badge, and the change of name should not change how a customer responds. A GLAS engagement, however courteously it opens, is the start of a structured process whose output serves Oracle's revenue, and it deserves to be managed with full audit discipline: controlled scope, controlled data, an independent measurement, and a firm separation between the compliance track and the commercial track.
Treat GLAS as what it is, a capable, well resourced counterpart with a clear incentive, and meet it with preparation rather than trust. Read the process mechanics in the LMS audit process guide, recognise the soft approach in the soft audit guide, and place the whole engagement in context with the audit defence pillar.
They are the same function under different names. License Management Services (LMS) was Oracle's compliance and audit team for years; Oracle rebranded and reorganised it as Global Licensing and Advisory Services (GLAS). The methods, scripts, and objectives are continuous, so guidance written for LMS audits applies to GLAS reviews. Not always. GLAS conducts both formal contractual audits and softer advisory reviews. A formal audit invokes the audit clause; an advisory review is positioned as help. Both gather the same kind of data and can lead to compliance findings, so a customer should manage an advisory review with the same discipline as a formal audit. GLAS sits inside Oracle and its findings serve Oracle's commercial interest, so its analysis should be tested rather than accepted. GLAS can be engaged professionally and its measurements reviewed, but the customer needs its own independent position to compare against, because GLAS is not a neutral adviser to the buyer.Oracle GLAS: frequently asked questions
What is the difference between LMS and GLAS?
Is a GLAS review the same as an audit?
Should you trust GLAS advice on your licensing?