Media reserved units

  • Article
  • 2 minutes de lecture

media services logo

Warning

Update your Azure Media Services REST API and SDKs to v3 by 29 February 2024. 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.

Action Required: To minimize disruption to your workloads, review the migration guide to transition your code from the version 2 API and SDKs to version 3 API and SDK before February 29th, 2024. After February 29th, 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. Learn about the latest version, starting with the Media Services v3 Overview.

Media Reserved Units (MRUs) were previously used to control encoding concurrency and performance. MRUs are only being used for the following legacy media processors that are to be deprecated soon. See Azure Media Services legacy components for retirement info for these legacy processors:

  • Media Encoder Premium Workflow
  • Media Indexer V1 and V2

For all other media processors, you no longer need to manage MRUs or request quota increases for any media services account as the system will automatically scale up and down based on load. You will also see performance that is equal to or improved in comparison to using MRUs.

Billing

While there were previously charges for Media Reserved Units, as of April 17, 2021 there are no longer any charges for accounts that have configuration for Media Reserved Units.

Scaling MRUs

For compatibility purposes, you can continue to use the Azure portal or the following APIs to manage and scale MRUs:

.NET Portal REST Java PHP

However, by default none of the MRU configuration that you set will be used to control encoding concurrency or performance. The only exception to this configuration is if you are encoding with one of the following legacy media processors: Media Encoder Premium Workflow or Media Indexer V1.