Frequently asked questions

  1. For how long will you support each release of the Microsoft Build of OpenJDK?
    • See the Support page for details.
  2. Will you release other versions of OpenJDK?
    • We plan to release OpenJDK binaries for versions where there is mutual LTS consensus across OpenJDK contributors and vendors.
  3. Will you release binaries of OpenJDK 8?
    • On Azure-managed services that offer Java 8 as a target runtime option, Microsoft may rely on third party binaries such as Eclipse Adoptium. For all other Azure services, customers can bring their JDK of choice for Java 8 from 3rd-party vendors. However, Microsoft recommends that customers move to Java 17 and later versions to benefit from several enhancements that can be translated into cost savings in cloud deployments and accelerated developer productivity. We believe the process is worth the effort and have provided guidance to help streamline this transition.
    • For more information on JDK versions supported across Azure services, see Java Support on Azure and Azure Stack.
  4. How are these binaries licensed?
    • General Public License 2.0 with Classpath Exception (GPLv2+CE).
  5. How long will it take to get binaries after OpenJDK has declared the GA tag?
    • Microsoft Build of OpenJDK is put through a rigorous suite of tests from the Eclipse Adoptium AQAvit project as well as the compliance tests from the Java Technology Compatibility Kit. This process typically takes 24-48 hours to complete but can take longer.
  6. Will Microsoft release out-of-band fixes due to critical or security vulnerabilities?
    • Only in extreme circumstances where other vendors also produce out-of-band patches for global scale security vulnerabilities. The likelihood of this happening is extremely low. Security vulnerabilities are often treated in secrecy, even for an open source project like OpenJDK. For more information, see OpenJDK Vulnerabilities Group.
  7. What happens if I find a bug in Microsoft Build of OpenJDK?
    • If an Azure customer identifies a problem first-hand with the Microsoft Build of OpenJDK, but it's not a security flaw that imposes risk, we'll prioritize the fixing of this issue and release it for the next quarterly update. We'll upstream the fix as soon as possible so it can also be addressed in other versions of Java that may be impacted, and be available in other OpenJDK distributions.
    • If you're not an Azure customer, report the issue to our GitHub repository at microsoft/openjdk.
    • If it's a security issue, we'll work to validate it, and then report it to the OpenJDK Vulnerability Group.

Provide feedback on the Microsoft Build of OpenJDK

Send us your comments, thoughts, and ideas to help us improve the Microsoft Build of OpenJDK. Visit our OpenJDK discussions page on GitHub to send us your feedback.

Java and OpenJDK are trademarks or registered trademarks of Oracle and/or its affiliates.