Azure SDK lifecycle and support policy
Azure SDK Lifecycle and support are governed by the latest Microsoft Modern Lifecycle Policy, which will prevail in case of any conflicts with the information below.
Here are the stages of a typical package lifecycle (for major versions)
Beta – A new SDK that is available for early access and feedback purposes and is not recommended for use in production. The beta version support is limited to GitHub issues and response time is not guaranteed. Beta releases live typically for less than 1 year, after which they are either deprecated or released as stable.
Active - The SDKs are generally available and fully supported, will receive new feature updates, as well as bug and security fixes. The major version will remain active for at least 12 months from the release date. Compatible updates for the major release are provided through minor versions, or patch versions. Customers are encouraged to use the latest version as that is the version that will get fixes and updates.
Deprecated - A library no longer conforms to our most up-to-date Azure SDK Guidelines, or has been superseded by a more recent release. In both cases, the current library is deprecated in favor of a newer library. Typically, deprecation occurs at the same time the replacement library is transitioned to Active, after which the releases will only address the most critical bug fixes and security fixes for at least another 12 months.
Community - SDK will no longer receive updates from Microsoft unless otherwise specified in the separate customer agreement. The package will remain available via public package managers and the GitHub repo, which can be maintained by the community.
You can check the lifecycle stage for your package at this page
By default, the Azure libraries are configured to connect to the Global Azure Cloud. Additional cloud target platforms are available, such as Azure Stack, Azure China and Government Cloud. Package lifecycle may vary across different target platforms. Refer to the target platform documentation for more information.
Azure SDK dependencies
The Azure SDK libraries depend on Azure Service REST API, programming language runtime, OS, and third-party libraries.
The Azure SDK libraries will not be guaranteed to work on platforms and with other dependencies that have reached their end of life. Dropping support for such dependencies may be done without increasing the major version of the Azure SDK libraries. We strongly recommend migration to supported platforms and other dependencies to be eligible for technical support.
Below is a list of supported Azure SDK platforms and runtimes for your reference:
- Any supported .NET versions that implement .NET Standard 2.0.
- Java: Java 8 , Java 11
- Node.js: LTS versions of Node.js including not just the ones in Active status, but also the ones in Maintainence status.
- Python 3.7+. Please check the Azure SDK for Python policy planning for more details on future Python versions.
- Go: Latest 2 major Go releases, refer to Go releases for more details.
- C++: Refer to the list of supported platforms and compilers here.
- Embedded C: Refer to the list of supported platforms and compilers here.
Below are the test configurations covering different operating systems and runtimes. You may see some outgoing versions for which we are dropping support or incoming versions that we don’t officially support yet. Please see the details in the previous section for the officially supported set.
- .NET test configuration
- Java test configuration
- Python test configuration
- Go test configuration
- C++ test configuration
Customers with a support plan can open an Azure Support ticket here You can open GitHub issues in the Azure SDK GitHub repositories to track bugs and feature requests. GitHub issues are free, but may take a longer time to process.