This repository contains official Java libraries for Azure services. For reference documentation go to Azure SDK for Java documentation, and tutorials, samples, quick starts and other documentation, go to Azure for Java Developers.
You can find a complete list of all the packages for these libraries here.
The Azure SDK team is pleased to make available the November 2019 client library General Availability (GA) release. We strongly recommend using the GA libraries in all production environments as these libraries are well tested and officially supported by Microsoft. More details, including installation instructions can be found here here.
To get started with a specific library, see the README.md file located in the library's project folder. You can find service libraries in the /sdk directory.
For tutorials, samples, quick starts and other documentation, visit Azure for Java Developers.
Java 8 or later is required to use the November 2019 client libraries, otherwise Java 7 or later is required.
The master branch has the most recent code with new features and bug fixes. It does not represent latest released GA SDK. See below for latest GA release.
For each package we release there will be a unique git tag created that contains the name and the version of the package to mark the commit of the code that produced the package. This tag will be used for servicing via hotfix branches as well as debugging the code for a particular preview or stable release version.
Format of the release tags are <package-name>_<package-version>. For more information please see
Each service might have a number of libraries available from each of the following categories:
New wave of packages that were released in November 2019 client library as General Availability (GA) and several others that were released in preview. These libraries follow the Azure SDK Design Guidelines for Java and share a number of core features such as HTTP retries, logging, transport protocols, authentication protocols, etc., so that once you learn how to use these features in one client library, you will know how to use them in other client libraries. You can learn about these shared features here.
These libraries can be easily identified by sdk/ folder, package, and namespaces names starting with azure-, e.g. azure-keyvault.
The libraries released in the GA November 2019 release:
- Identity
- Key Vault Keys
- Key Vault Secrets
- Storage Blobs
- Storage Blobs Batch
- Storage Blobs Cryptography
- Storage Queues
The libraries released in the November 2019 preview:
- App Configuration
- Event Hubs
- Event Hubs Checkpoint Store
- Storage File Share
- Key Vault Certificates
- OpenCensus Tracing
NOTE: If you need to ensure your code is ready for production use one of the stable, non-preview libraries.
Last stable versions of packages that have been provided for usage with Azure and are production-ready. These libraries provide similar functionalities to the preview libraries, as they allow you to use and consume existing resources and interact with them, for example: upload a blob. Stable library directories start with microsoft-azure-, e.g. microsoft-azure-keyvault. They might not implement the guidelines or have the same feature set as the Novemeber releases. They do however offer wider coverage of services.
Libraries which enable you to provision specific resources. They are responsible for directly mirroring and consuming Azure service's REST endpoints. Management library directories contain -mgmt-, e.g. azure-mgmt-keyvault.
- For reference documentation visit the Azure SDK for Java documentation.
- For tutorials, samples, quick starts and other documentation, visit Azure for Java Developers.
- For build reports on code quality, test coverage, etc, visit Azure Java SDK.
- File an issue via Github Issues.
- Check previous questions or ask new ones on StackOverflow using
azure-java-sdktag.
For details on contributing to this repository, see the contributing guide.
This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.microsoft.com.
When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repositories using our CLA.
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact [email protected] with any additional questions or comments.
