How to migrate from Azure Media Services to api.video

With the upcoming retirement of Azure Media Services in mid-2024, you may be wondering about what to do next. But worry not, because we have a better and a far more affordable option for you! In this article, we will discuss seamless migration options from Azure to api.video, give you reasons as to why you should be doing it, and also explain to you a simplified process to execute the migration.

Let’s get started.

Why should I migrate from Azure Media Services to api.video?

First things first, why should you think about migrating to api.video? What is the benefit? How is it better?

Well, let me answer all these questions with some solid facts.

1. *api.video charges you zero cost for adaptive bitrate encoding

Let’s understand this with an example where we compare the encoding of 10,000 minutes at 4K resolution.

Azure takes $600 to encode a video of 10,000 minutes at a 4K resolution as you can see in the image below (source: Azure Pricing Calculator).

On the other hand, api.video takes ZERO cost to encode your videos. Yes, encoding is completely free with api.video, whether it is 10,000 minutes of video or 20,000; 480p resolution or 4K – it is absolutely free.

Check our pricing calculator to learn more about our [pricing].(https://api.video/pricing/)

2. Ingestion speed with api.video is way better than that with Azure.

Let’s understand this by uploading and transcoding the same 18.7Mb file to Azure and api.video.

When you transcode a video with Azure, the time it takes to do the job is 1 minutes and 13 seconds. Note that this is just time taken for transcoding, and I have not yet included the upload time here.

When you upload and transcode the same video with api.video, the time it takes to do the job is JUST 30 seconds.

3. Ease of use of api.video surpasses that of Azure

The process to upload, encode and transcode videos at Azure is complex and often tedious to execute. api.video, on the other hand, has built an interface and documentation that is easy to understand and quick to execute. To validate what we claim, do give the below mentioned links a read and know it for yourself. 🙂

• api.video: Upload and encode a video with api.video
• Azure: Upload and encode a video with Azure Media Services

Sounds good? If yes, then let’s move to the actual migration steps.

Migration steps to move from Azure to api.video

If you’ve made up your mind to make the shift, let’s understand the migration steps involved in it to move all your data from Azure Media Services to api.video.

You can also migrate your videos directly through our api.video import tool.

To start with the migration steps, let us look at a ready script in Node.js for you to follow. Before you start the script, make sure you clone the Azure Media Serivce to api.video migration script from Github. Once you do that, you can follow the guide below.

Let’s understand what the script is doing.

1. The script will check for all assets in your Azure Media Service Instance
2. It will get the Storage containers and list the blobs for these storage containers
3. Because of the way Azure is encoding their videos, the script will take the file with the highest resolution (in order not to duplicate the files)
4. Once it gets the list, it will create a video object with the name same as the blob and set the source to the Azure storage URL
5. The file will then be uploaded and encoded with api.video

You can also navigate to api.video documentation to get more information about how each endpoint works. You can also check the api.video api reference or the api.video guides for more details.

Note that the script does not automatically delete the files from your Azure Storage or Azure Media Services, you will have to do that manually. If you wish to keep the sources on Azure Account Storage as backup, you are also welcome to do so.

Using the migration script

Here are the steps to use the script to migrate from Azure to api.video.

1. First, import the modules that are needed, such as:

• @api.video/nodejs-client - api.video node.js client, in order to create the video object, upload and encode the video
• @azure/identity - access Azure services
• @azure/arm-mediaservices - client to access Azure media services

2. Next, pass in credentials that you get from Azure Media Services to the client and the api.video client

3. Note that in the previous step, you will also need to update the .env file and grab the parameters from Azure. In order to do that, navigate to your Azure Media Service, and select the directory that you would like to migrate.

4. Select API keys and copy over the parameters presented in the .ENV pane (you can select either User Authentication or Service principal authentication)

5. Next, to get access to the storage, navigate to the Azure Storage Account → Shared access signature:

6. Allow the following:

7. Make sure that you generate the Shared access signature and once you have the links, copy the Blob service SAS URL link to the .env file. The parameter you are looking for is REMOTESTORAGEACCOUNTSAS

8. Add the api.video API key to the .env file by navigating to the api.video dashboard and copy the API key value

9. Now, run npm install in the terminal in order to install all of the node modules
10. Run npm run build
11. Run npm run start in order to start the migration script
12. Sit back and relax 🙂

Conclusion

Well, that was it! Yes, it was that simple.

We hope that you choose wisely as you weigh the strengths of Azure and api.video. However, if you consider factors like scalability, customization options, pricing, and developer friendly API, api.video comes out to be a clear winner.

If you still have any questions regarding the migration, book a call with us — we are here to help you. You can also go to our homepage for more information or sign-up for a free sandbox account to test us out for free.

So, are you ready to make your life easier with this painless migration process?