Skip to content
This repository has been archived by the owner on Mar 29, 2023. It is now read-only.

Legacy Azure SDK libraries are retiring on March 31st 2023 #217

Open
azure-deprecation-automation opened this issue Mar 30, 2022 · 1 comment
Labels
area:sdk All issues related to notices that are applicable to SDKs cloud:public All issues related to Azure public cloud impact:migration-required All issues where a migration is required services:all All notices related to all Azure services verified All notices that are verified by an official communication
Milestone

Comments

@azure-deprecation-automation
Copy link

azure-deprecation-automation commented Mar 30, 2022

Legacy Azure SDK libraries are retiring on March 31st 2023

Deadline: Mar 31, 2023
Impacted Services:

  • Azure All

More information:

Notice

A full list of deprecated libraries and their replacement libraries can be found in this SDK overview.

Here's the official report from Microsoft:

On 31 March 2023, we will be retiring support for Azure SDK libraries which do not conform to our current Azure SDK guidelines. The new Azure SDK libraries are updated regularly to drive consistent experiences and strengthen your security posture. Please transition to the new Azure SDK libraries to take advantage of the new capabilities and critical security updates before 31 March 2023.

Although the older libraries can still be used beyond 31 March 2023, they will no longer receive official support and updates from Microsoft. If you prefer not to transition to the new Azure SDK libraries, source code for the current Azure SDKs libraries is available on GitHub as open source. You can continue to use the code and apply your own fixes, as required.

To learn more about the retirement and replacement of older Azure SDK libraries, read this blog post. The new Azure SDK libraries improve the developer experience including ease of use, consistency, security, performance, and dependability. For a full list of retired libraries, refer to this page.

Timeline

Phase Date Description
Announcement Mar 17, 2022 Deprecation was announced
Deprecation Mar 31, 2023 Deprecated SDKs will still work, but will no longer be supported nor receive updates

Impact

Legacy Azure SDK libraries are retiring on March 31st 2023 which do not conform to our current Azure SDK guidelines.

Required Action

Here's the official report from Microsoft:

Support for the older libraries is ending. To avoid missing out on security and performance updates to the Azure SDKs, upgrade to the new Azure SDK libraries by 31 March 2023.

Contact

You can get in touch through the following options:

  • Ask the community experts on GitHub (link).
  • Contact Azure support (link).
@azure-deprecation-automation azure-deprecation-automation added area:sdk All issues related to notices that are applicable to SDKs cloud:public All issues related to Azure public cloud impact:migration-required All issues where a migration is required services:all All notices related to all Azure services verified All notices that are verified by an official communication labels Mar 30, 2022
@azure-deprecation-automation azure-deprecation-automation added this to the 2023 milestone Mar 30, 2022
@azure-deprecation-automation
Copy link
Author

This issue is automatically managed and suggest to use GitHub Discussions to discuss this deprecation.

@azure-deprecation azure-deprecation locked and limited conversation to collaborators Mar 30, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area:sdk All issues related to notices that are applicable to SDKs cloud:public All issues related to Azure public cloud impact:migration-required All issues where a migration is required services:all All notices related to all Azure services verified All notices that are verified by an official communication
Development

No branches or pull requests

1 participant