API access differences between Azure Media Services V2 to v3 API

---

Important

It is no longer necessary to migrate from Azure Media Service v2 to v3 as deprecation of V2 API will align with the retirement of Azure Media Services. Please see the Azure Media Services retirement guide for more information.

This article describes the API access differences between Azure Media Services V2 to V3.

API Access

All Media Services accounts will have access to the V3 API. However, we strongly recommend migration development on a fresh account before applying updated code to an existing V2 account. This is because V3 entities aren't backwards compatible with V2. Some V2 entities like Assets are forward compatible with V3. You can continue to use existing accounts if you don’t mix the V2 and V3 APIs and then try to go back to V2, but this is discouraged.

Access to the V2 API will be available until it is retired in 2024.

Create a V3 account

While you are migrating, you can create a V3 account that still has access to V2. Creating the account can be done with:

• The REST API and older version
• Selecting the checkbox in the portal.

All the .NET, CLI, and other SDKs will be targeting the latest 2020-05-01 API, so find or configure the older API versions.

Note

New accounts created with the 2020-05-01 (or later) API cannot use V2 APIs.

Get help and support

You can contact Media Services with questions or follow our updates by one of the following methods:

• Q & A
• Stack Overflow. Tag questions with azure-media-services.
• @MSFTAzureMedia or use @AzureSupport to request support.
• Open a support ticket through the Azure portal.