Quotas and Limitations

This article describes quotas and limitations associated with Microsoft Azure Media Services.


For resources that are not fixed, you may ask for the quotas to be raised, by opening a support ticket. Do not create additional Azure Media Services accounts in an attempt to obtain higher limits.

Resource Default Limit
Azure Media Services (AMS) accounts in a single subscription 25 (fixed)
Media Reserved Units (RUs) per AMS account 25 (S1)
10 (S2, S3) (1)
Jobs per AMS account 50,000(2)
Chained tasks per job 30 (fixed)
Assets per AMS account 1,000,000
Assets per task 50
Assets per job 100
Unique locators associated with an asset at one time 5(4)
Live channels per AMS account 5
Programs in stopped state per channel 50
Programs in running state per channel 3
Streaming endpoints in running state per AMS account 2
Streaming units per streaming endpoint 10
Storage accounts 1,000(5) (fixed)
Policies 1,000,000(6)
File size In some scenarios, there is a limit on the maximum file size supported for processing in Media Services. 7

1 If you change the type (for example, from S2 to S1,) the max RU limits are reset.

2 This number includes queued, finished, active, and canceled jobs. It does not include deleted jobs. You can delete the old jobs using IJob.Delete or the DELETE HTTP request.

As of April 1, 2017, any Job record in your account older than 90 days will be automatically deleted, along with its associated Task records, even if the total number of records is below the maximum quota. If you need to archive the job/task information, you can use the code described here.

3 When making a request to list Job entities, a maximum of 1,000 jobs is returned per request. If you need to keep track of all submitted Jobs, you can use top/skip as described in OData system query options.

4 Locators are not 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 this section.

5 The storage accounts must be from the same Azure subscription.

6 There is a limit of 1,000,000 policies for different AMS policies (for example, for Locator policy or ContentKeyAuthorizationPolicy).


You should use the same policy ID if you are always using the same days / access permissions / etc. For information and an example, see this section.

7If you are uploading content to an Asset in Azure Media Services to process it with one of the media processors in the service (that is, encoders like Media Encoder Standard and Media Encoder Premium Workflow, or analysis engines like Face Detector), then you should be aware of the constraints on the maximum file sizes supported.

The maximum size supported for a single blob is currently up to 5 TB in Azure Blob Storage. However, additional limits apply in Azure Media Services based on the VM sizes that are used by the service. The following table shows the limits on each of the Media Reserved Units (S1, S2, S3.) If your source file is larger than the limits defined in the table, your encoding job will fail. If you are encoding 4K resolution sources of long duration, you are required to use S3 Media Reserved Units to achieve the performance needed. If you have 4K content that is larger than 260 GB limit on the S3 Media Reserved Units, contact us at amshelp@microsoft.com for potential mitigations to support your scenario.

Media Reserved Unit type Maximum Input Size (GB)
S1 325
S2 640
S3 260

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

Read about the Azure Media Services learning paths:

Provide feedback

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: