Migrate your Azure Media Services to OCI

As businesses seek more cost-effective and competitive solutions, the migration from one cloud media service to another has become a common endeavor. One migration that has gained significant traction is the transition from Azure Media Services to Oracle Cloud Infrastructure (OCI) Media Flow and Media Streams.

In this blog post, we explore the process of migrating from Azure Media Services to OCI Media Flow and Media Streams. We focus on two primary methods for achieving this migration, each with its own merits and use cases.

Automated transcoding with OCI Media Flow and ingesting to OCI Media Streams

The first method offers an automated approach to handle the migration process. With OCI Media Flow’s transcoding capabilities and competitive pricing, you can seamlessly clone your video files from Azure blob storage to OCI Object Storage with rclone. When the videos are securely stored in OCI Object Storage, you can easily trigger the transcoding job, converting the files into a HLS format with ease. OCI Media Flow also integrates seamlessly with OCI AI Speech and OCI AI Vision, allowing you to utilize advanced AI capabilities within your media workflows.

For a more hands-on experience with OCI Media Services, we recommend checking out the self-paced OCI LiveLabs session, providing an in-depth walk-through of the services’ functionalities using various programming languages and tools. For customers looking to replicate their Azure media content effortlessly, we also provide a helpful repository utilizing the rclone tool to clone videos from Azure to OCI. However, only undertake this process if you have the appropriate authorization because unauthorized duplication is considered an act of piracy.

Manual extraction of the HLS playlist and ingestion to OCI Media Streams

While the automated approach is suitable for most migration cases, a few files might require a manual touch. The second method entails manually running the migration process on inpidual files, which you can accomplish with the aid of a Python environment and OCI CLI access. You might prefer this method for handling specific files that don’t seamlessly migrate through the automated process. For more details, contact us.

Conclusion

We recommend using the automated approach with OCI Media Flow as much as possible. You can transcode most of your files with ease, generating complete OCI-specific files in a single fmp4 format. If any files prove challenging to migrate through automation, only then should you consider the manual option.

Migrating from Azure Media Services to OCI Media Services can be a seamless and efficient process with the right approach. So, let’s embark on this migration journey and unlock the full potential of Oracle Cloud Infrastructure Media Services for your media workflows.

For more information, see the following resources:

• OCI Media Flow

• OCI Media Streams

• Azure Retiring its Media Services