Azure Media Services REST API v2 is retiring on 29 Feb 2024

[azure-deprecation-automation]

Azure Media Services REST API v2 is retiring on 29 Feb 2024

Deadline: Feb 29, 2024 Impacted Services:

• Azure Media Services

More information:

• https://azure.microsoft.com/en-au/updates/update-your-azure-media-services-rest-api-and-sdks-to-v3-by-29-february-2024/
• https://docs.microsoft.com/en-us/azure/media-services/latest/migrate-v-2-v-3-migration-introduction

Notice

Here's the official report from Microsoft:

Because version 3 of Azure Media Services REST API and client SDKs for .NET and Java offers more capabilities than version 2, we’re retiring version 2 of the Azure Media Services REST API and client SDKs for .NET and Java. We encourage you to make the switch sooner to gain the richer benefits of version 3 of Azure Media Services REST API and client SDKs for .NET and Java. Version 3 provides:

• 24x7 live event support.
• ARM REST APIs, client SDKs for .NET core, Node.js, Python, Java, Go and Ruby.
• Customer managed keys, trusted storage integration, private link support, and more.

Timeline

Phase	Date	Description
Announcement	Feb 23, 2021	Deprecation was announced
Deprecation	Feb 29, 2024	API endpoint will no longer be accepting traffic

Impact

Azure Media Services REST API v2 is retiring on 29 Feb 2024.

Required Action

Here's the official report from Microsoft:

To minimize disruption to your workloads, review the migration guide to transition your code from the version 2 to version 3 API and SDK before 29 February 2024.

After 29 February 2024, Azure Media Services will no longer accept traffic on the version 2 REST API, the ARM account management API version 2015-10-01, or from the version 2 .NET client SDKs. This includes any 3rd party open-source client SDKS that may call the version 2 API.

Contact

You can get in touch through the following options:

• Get answers from Microsoft Q&A (link).
• Contact Azure support (link).

[azure-deprecation-automation]

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