Quotas and Limitations
This article describes quotas and limitations associated with Microsoft Azure Media Services.
For resources that aren't fixed, open a support ticket to ask for an increase in the quotas. Don't create additional Azure Media Services accounts in an attempt to obtain higher limits.
|Azure Media Services accounts in a single subscription||25 (fixed)|
|Media reserved units per Media Services account||25 (S1)
10 (S2, S3)1
|Jobs per Media Services account||50,0002|
|Chained tasks per job||30 (fixed)|
|Assets per Media Services account||1,000,000|
|Assets per task||50|
|Assets per job||100|
|Unique locators associated with an asset at one time||54|
|Live channels per Media Services account||5|
|Programs in stopped state per channel||50|
|Programs in running state per channel||3|
|Streaming endpoints that are stopped or running per Media Services account||2|
|Streaming units per streaming endpoint||10|
|Storage accounts||1,0005 (fixed)|
|File size||In some scenarios, there's a limit on the maximum file size supported for processing in Media Services.7|
1If you change the type, for example, from S2 to S1, the maximum reserved unit limits are reset.
2This number includes queued, finished, active, and canceled jobs. It doesn't include deleted jobs. You can delete old jobs by using IJob.Delete or the DELETE HTTP request.
As of April 1, 2017, any job record in your account older than 90 days is automatically deleted, along with its associated task records. Automatic deletion occurs even if the total number of records is below the maximum quota. To archive the job and task information, use the code described in Manage assets with the Media Services .NET SDK.
3When you make a request to list job entities, a maximum of 1,000 jobs is returned per request. To keep track of all submitted jobs, use the top or skip queries as described in OData system query options.
4Locators aren't designed for managing per-user access control. To give different access rights to individual users, use digital rights management (DRM) solutions. For more information, see Protect your content with Azure Media Services.
5The storage accounts must be from the same Azure subscription.
6There's a limit of 1,000,000 policies for different Media Services policies. An example is for the Locator policy or ContentKeyAuthorizationPolicy.
If you always use the same days and access permissions, use the same policy ID. For information and an example, see Manage assets with the Media Services .NET SDK.
7If you upload content to an asset in Media Services to process it with one of the media processors in the service, note the maximum file sizes that are supported. Assets include encoders like Media Encoder Standard and Media Encoder Premium Workflow or analysis engines like Face Detector.
The maximum size that's supported for a single blob is currently up to 5 TB in Azure Blob Storage. Additional limits apply in Media Services based on the VM sizes that are used by the service. The following table shows the limits on the media reserved units S1, S2, and S3. If your source file is larger than the limits defined in the table, your encoding job fails. If you encode 4K resolution sources of long duration, you're required to use S3 media reserved units to achieve the performance needed. If you have 4K content that's larger than the 260-GB limit on the S3 media reserved units, contact us at email@example.com for potential mitigations to support your scenario.
|Media reserved unit type||Maximum input size (GB)|
Open a Support Ticket to request changes to the default quotas
To request changes to the default quotas provided, you can open a support ticket. Please include detailed information in the request on the desired quota changes, use-case scenarios, and regions required.
How to open a support ticket
In the Azure portal, go to Help + support. If you are not logged in to Azure, you will be prompted to enter your credentials.
Media Services learning paths
Media Services v3 (latest)
Check out the latest version of Azure Media Services!
Media Services v2 (legacy)
Use the User Voice forum to provide feedback and make suggestions on how to improve Azure Media Services. You also can go directly to one of the following categories:
Send feedback about: