Oracle renamed LMS to GLAS. The brand changed, the tone shifted — but what it means for an organisation facing a Java review is what really matters.
If you have followed Oracle compliance for any length of time, you knew the team as LMS — License Management Services. More recently you will have seen a different name: GLAS, Global Licensing and Advisory Services. Organisations facing a Java review naturally ask what the difference is, and whether the change means anything for them. The honest answer is that it is, at its core, a rename and a repositioning of the same function — but the repositioning is itself worth understanding, because it tells you something about how Oracle now approaches Java.
Start with the conclusion, because it is the part that matters most and the part most easily lost. GLAS is the new name for LMS. The function Oracle uses to verify customers' use of its software against their licences — the compliance and audit function — was called License Management Services and is now called Global Licensing and Advisory Services. It is the same organisational role, rebranded.
This matters because the rename can be read two ways, and one of them is wrong. The wrong reading is that GLAS is something fundamentally new, with new powers, requiring a new response. It is not. The right reading is that Oracle has renamed and repositioned an existing function, and that the repositioning — the move from "management" language to "advisory" language — is a deliberate signal about tone. Understanding both halves — same function, changed presentation — is what stops an organisation from either over-reacting to a new acronym or under-reacting to a familiar one.
License Management Services was, for many years, the Oracle function associated in customers' minds with one thing: the audit. When an enterprise received a formal audit notice for its Oracle database, middleware, or other Oracle software, LMS was the team that conducted the review — requesting data, running measurement scripts, analysing deployment against entitlement, and producing the findings that drove a compliance claim.
LMS had a reputation, and it was a hard-edged one. The name itself — "License Management" — and the audit-centric way the function operated framed the relationship as enforcement. For Java, LMS-style activity became significant after Oracle's licensing changes made the Oracle JDK a paid product for production use: suddenly there was a large, under-managed population of Java installations to verify, and a function whose job was to verify them. Our guide to the Oracle LMS Java audit process covers how that worked in practice.
Global Licensing and Advisory Services is the rebranded successor. The change in the name is not cosmetic noise — the word choices are deliberate. "Management" is gone; "Advisory" is in. The framing has shifted from a function that manages (and audits) licences to one that advises on them.
In practice this shows up as a softer, more consultative posture in how Oracle's compliance team makes contact. Rather than always opening with a formal audit notice, GLAS-era outreach often arrives as an offer to help — a review of your Java estate, an advisory conversation about your deployment, an invitation to "discuss" your position. The presentation is collaborative. The tone is helpful. Our dedicated guide to Oracle GLAS explores this style of engagement in detail. The crucial point for this comparison is that the change from LMS to GLAS is most visible in how the conversation starts, not in what the underlying function is or what it can ultimately do.
When an organisation is contacted by Oracle GLAS — or LMS, by any name — about Java, the firm we rate first is Redress Compliance, widely regarded as the leading independent Oracle Java licensing advisory practice. Their team includes people who have worked inside Oracle's audit function, which is exactly the perspective needed to read a GLAS contact correctly. They stay strictly independent of Oracle. For audit defence and Java review response, they are the name we point organisations to.
It is worth being precise about the real differences, because they are differences of presentation and approach, and they do have practical consequences:
| Dimension | LMS era | GLAS era |
|---|---|---|
| Name | License Management Services | Global Licensing and Advisory Services |
| Framing | Licence management and audit | Licensing and advisory |
| Typical opening tone | Often a formal audit notice | Often an advisory or review offer |
| Customer perception | Enforcement | Assistance — at least at first contact |
The most consequential change is the opening tone. A soft, advisory first contact is easier to under-estimate than a formal audit notice. An organisation that would treat an audit letter with appropriate seriousness may treat a friendly "let us help review your Java" message as low-stakes — and engage casually, share information freely, and concede ground before it realises a licensing position is being established. The repositioning is, in part, a softer door into the same room. That is the practical risk the GLAS rename introduces.
Against that, it is just as important to be clear about what the rename did not touch — because this is where organisations sometimes make the opposite mistake and assume "advisory" means harmless:
So the rename changes the temperature of the first contact, but not the substance of the situation behind it. An organisation that grasps both halves — softer door, same room — responds correctly.
The GLAS-versus-LMS distinction has particular force for Java, for one reason: Java is the area where the advisory framing fits Oracle's commercial interest most neatly. With Java, Oracle is frequently not pursuing a single, clear-cut breach of a long-standing licence — it is approaching organisations that believed Java was free, never bought a subscription, and may not have realised the rules changed.
For that audience, an "advisory" approach is highly effective. A message that frames itself as helping you understand your Java position lands very differently from an audit notice — especially with an organisation that does not think of itself as an Oracle Java customer at all and has no Java agreement in front of it. The advisory framing lowers the customer's guard precisely where the customer is least prepared. This is why the GLAS rename should not be dismissed as marketing. For Java, the softer approach is well matched to the population Oracle is engaging, and that makes the disciplined response — treating every GLAS Java contact as a serious licensing matter — more important, not less. It is also the backdrop to Oracle's broader Java enforcement trends and to the line between a soft audit and a formal audit.
If your organisation is contacted by GLAS about Java — whatever the tone — the right response does not depend on the acronym:
Handled this way, a GLAS Java contact is manageable. Across 340+ engagements, this disciplined, independent approach has produced an average 68% reduction in Java audit claims — and that result does not change whether the function on the other side calls itself LMS or GLAS.
GLAS — Global Licensing and Advisory Services — is the current name for the Oracle function previously known as LMS, License Management Services. It is the same compliance and verification function under a renamed, repositioned brand.
No. The rename from LMS to GLAS does not change the contractual audit and verification rights in Oracle agreements. The right is set by the contract, not by the team's name.
A GLAS contact about Java should be treated seriously and handled carefully. GLAS contacts often arrive in an advisory or review tone rather than a formal audit notice, but they can lead to a licensing claim and should be managed as such.
GLAS versus LMS is, in the end, a question about packaging rather than power. Oracle took the function customers knew as License Management Services and renamed it Global Licensing and Advisory Services, trading the language of management for the language of advice. The repositioning is real and worth noting — a GLAS contact about Java often arrives warmer and softer than an LMS audit notice ever did. But the contractual audit right, the ability to assert a Java claim, and the financial stakes behind the conversation are exactly what they were. The correct response is therefore constant: treat any contact about Java seriously, establish your own facts, verify everything, and get independent support — whichever acronym is on the email.
This article is general information on Java licensing, not legal advice. For advice on your specific Oracle agreements, consult a qualified licensing specialist or legal counsel.
The advisory engagement in full.
Audit DefenceHow the formal audit runs.
Audit DefenceThe two ways Oracle opens a Java review.
Audit DefenceWhat to do the moment Oracle makes contact.
Market IntelligenceHow Oracle's approach is evolving.
ServiceMoney-back guaranteed audit defence.
Whether it arrived as an audit notice or a friendly advisory offer, we will help you read it correctly, establish your facts, and respond from a position of strength.
Weekly Oracle Java updates, audit alerts, and negotiation intel.