Migrating to Azure Media Services V3 API

Question

We are in the process of migrating to Azure media services API V3. As part of the migration we have created a new V3 account for development and tested creation of assets, encoding etc.

Based on the documentation here (https://learn.microsoft.com/en-us/azure/media-services/latest/migrate-v-2-v-3-differences-api-access#create-a-v3-account), we need to apply some changes to the existing V2 account to allow access to both the existing assets (created using V2 account and V2 API) and create/encode new assets using V3 API.

I am looking for some guidance or documentation on what code/config changes we need to apply to V2 account to allow seamless access to old and new assets created using V3 API.

Answer 1

Rahul, Apologies for the delay from over the weekend.

Typically, you need to create a new Azure AD application and service principal for your V3 account, and then grant it access to your V2 account. You may follow the steps outlined in the docs (below) to create the new Azure AD application and service principal, and then grant it access to your V2 account.

Once you have done this, you can use the new Azure AD application and service principal to authenticate your requests to both the V2 and V3 APIs. You will need to update your code to use the new Azure AD application and service principal, and make sure that you are using the correct API version for each request.

Here are the high-level steps you need to follow:

1. Create a new Azure AD application and service principal for your V3 account.
2. Grant the new Azure AD application and service principal access to your V2 account.
3. Update your code to use the new Azure AD application and service principal for authentication.
4. Make sure that you are using the correct API version for each request.

For more detailed information on how to perform these steps, you may refer to the following docs:

Migrate from Media Services v2 to v3 introduction ( How to use this guide with 1, 2, 3, 4 steps)

API access differences between Azure Media Services V2 to v3 API

Step 3 - Set up to migrate to the V3 REST API or client SDK

Also, as mentioned in the doc note:

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.