Azure Media Services quotas and limits
Warning
Azure Media Services will be retired June 30th, 2024. For more information, see the AMS Retirement Guide.
This article lists some of the most common Media Services limits, which are also sometimes called quotas.
Note
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.
Account limits
Resource | Default Limit | Per |
---|---|---|
Media Services accounts | 100 (fixed) | Subscription |
Asset limits
Resource | Default Limit | Per |
---|---|---|
Assets per Media Services account | 1,000,000 | Media Services account |
Storage limits
Azure Storage block blog limits apply to storage accounts used with Media Services. See Azure Blob Storage limits.
These limits include the total stored data storage size of the files that you upload for encoding and the file sizes of the encoded files. The limit for file size for encoding is a different limit. See File size for encoding.
Storage account limit
You can have up to 100 storage accounts. All storage accounts must be in the same Azure subscription.
File size for encoding limit
An individual file that you upload to be encoded should be no larger than 260 GB.
Jobs and transforms (encoding & analyzing) limits
Resource | Default Limit | Per |
---|---|---|
Jobs | 500,000 (3) (fixed) | Media Services account in a 3 month sliding window |
Input assets | 50 (fixed) | Job |
Output assets | 20 (fixed) | Job |
Videos | 100 (4) (fixed) | Job |
Transforms | 100 (fixed) | Media Services account |
Output encoding types | 20 (fixed) | Transform |
Files | 10 (fixed) | Input Asset |
3 This number includes queued, finished, active, and canceled jobs. It does not include deleted jobs.
4 There is an exception to this limit. The limit of 50 job inputs per job supersedes the limit of 100 clips per job. For example, if there are 51 job inputs and each job input contains 1 clip, then that will violate the limit of 50 job inputs per job, even though the clips per job limit has not been met.
Any job record in your account older than 90 days will be automatically deleted, even if the total number of records is below the maximum quota.
Live streaming limits
Resource | Default Limit | Per |
---|---|---|
Live events (5) | 5 | Media Services account |
Live outputs writing data to an output asset | 3 (6) | Live Event |
Max live output duration | Size of the DVR window | Live output |
5 For detailed information about live event limits, see Live Event types comparison and limits. Depending on your streaming use case and regional data center of choice, AMS is able to accommodate more than 5 live events per Media Services account. Please file a support request to increase your account quota.
6 Live outputs start on creation and stop when deleted.
Timed metadata limits
Resource | Default Limit | Per |
---|---|---|
Total message body payload size | 256 kb max | Request |
Requests | 2 | per second |
Packaging & delivery limits
Resource | Default Limit | Per |
---|---|---|
Streaming endpoints (stopped or running) | 2 | Media Services account |
Premium streaming units | 50 | Streaming Endpoint |
Dynamic manifest asset filters | 100 | Asset |
Streaming policies | 100 (7) | Media Services account |
Streaming policies | 3 | Streaming Locator |
Unique streaming locators | 100(8) (fixed) | Asset |
7 When using a custom streaming policy, design a limited set of policies for your Media Service account, and re-use them for your streaming locators whenever the same encryption options and protocols are needed. You should not be creating a new streaming policy for each streaming locator.
8 Streaming locators are not designed for managing per-user access control. To give different access rights to individual users, use Digital Rights Management (DRM) solutions.
Protection limits
Resource | Default Limit | Per |
---|---|---|
Optional claims | 30 | Content Key Policy |
Licenses on Media Services key delivery service | 1,000,000 | Each type Month |
Support ticket
For resources that are not fixed, you may ask for the quotas to be raised, by opening a support ticket. Include detailed information in the request on the desired quota changes, use-case scenarios, and regions required.
Do not create additional Azure Media Services accounts in an attempt to obtain higher limits.