If I were still running the Oracle LMS audit team, I would literally audit every single Azul Java customer. Why not? There is almost no cost to Oracle when they audit a Java customer. It’s very easy to find Java non-compliance. These audits generate a lot of money for Oracle. Companies using Azul Java could easily be out of compliance with Oracle Java. To top it all off, if Oracle audits an Azul customer, and finds a problem, that customer has a choice: they could pay both Oracle and Azul (not likely); or they could drop Azul and just pay Oracle (more likely). Not only does Oracle increase their Java revenue, but they also hit a competitor’s revenue. It’s a win-win for Oracle.
Why are Azul customers at risk?
First, Java by its nature is ubiquitous. Everyone is using Java, and even after certain versions are removed, they can come back. Companies download it from Oracle. Java is included in many non-Oracle applications. Developers love Java and they will find a way to use it. They will often use Oracle’s Java, despite a corporate mandate. Even after you standardize on Azul, Oracle Java comes back into your environment.
Second, companies using Azul Java can have a false sense of security when it comes to Oracle Java licensing. They simply let their guard down. I’ve heard the following more than once, “We don’t have an Oracle Java problem because we use Azul.” Guess what? You always have an Oracle Java problem. Just like I would never go to Oracle and ask “am I out of compliance?” I would never go to Azul, or an Azul partner, and ask “am I out of compliance with Oracle Java?” Those firms have an inherent conflict when giving Oracle licensing advice because they want to sell you more Azul licenses. They do not want you to be worried about Oracle in a way that might have you reconsider your position with Azul.
Third, and this is new, Oracle is in fact auditing companies who use Azul Java. We’ve seen the audits, and we are defending these companies. These companies were surprised by Oracle’s decision to audit them because they thought the issue went away with their adoption of Azul Java. Oracle simply did what Oracle does. Don’t forget the frog and the scorpion! I can guess Oracle’s position was that the audit target was out of compliance, and because they thought they were safe, would over-share information with Oracle.
What can Azul’s customers do to protect themselves from Oracle?
Let me start by telling you what you should not do. Don’t let your guard down. Remember, Oracle Java is almost certainly running in your environment, even if you have an enterprise license with Azul. Second, don’t rely on anyone with a conflict to give you an Oracle Java licensing position. This includes Oracle, Oracle partners, Azul, and Azul partners. If you do rely on them, then you get what you get and don’t get upset!
Once you avoid the mistakes, then it’s time to be ready for Oracle. Make sure your SAM team knows this is an issue. Educate your IT teams on how to avoid Oracle Java and the risks of using it. Finally, find an expert in the field who is independent of both Oracle and Azul.
Ask us to help you get ready for Oracle
Of course I think that Palisade Compliance is the right advisor to help you. We have completed hundreds of Java scans uncovering Oracle, OpenJDK, Azul, Red Hat, and other forms of Java. We provide the most accurate licensing reports, have the most experienced Oracle advisors (average 20 years of Oracle licensing experience), the best customer references, and we will actually defend you if you are audited by Oracle.
Palisade Compliance has no conflict of interest and only works to make sure you stay in compliance and pay the lowest fees for Java – whether that’s to Oracle or Azul, or helping you to the free OpenJDK option.
Palisade Compliance has not always been independent in the Java space, however. There was a time when we were an active partner of Azul, attending meetings and doing joint marketing. Nothing against Azul – they have good products and services. We just thought it would be better for our clients if we reverted to our independent status. This position also allows us to help our customers who are negotiating license agreements with Azul. We can help get that price down, too.
Want to know how big your Oracle Java risk is?
Go to our Java calculator and find out.
