Quotas and Limitations
This topic describes quotas and limitations associated with Microsoft Azure Media Services.
|Resource||Default Limit||Maximum Limit|
|Azure Media Services (AMS) accounts in a single subscription||25|
|Assets per AMS account||1,000,0001|
|Chained tasks per job||30|
|Assets per task||50|
|Assets per job||100|
|Jobs per AMS account||50,0002|
|Unique locators associated with an asset at one time||54|
|Live channels per AMS account||5||N/A1|
|Programs in stopped state per channel||50||N/A1|
|Programs in running state per channel||3||3|
|Streaming endpoints in running state per AMS account||2||N/A1|
|Streaming units per streaming endpoint||10||N/A1|
|Encoding units per AMS account||25||N/A1|
1 You can request to update the limits for this quota by opening a support ticket. Do not create more AMS accounts to increase limits, instead submit a support ticket.
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.
3 When making a request to list Job entities, a maximum of 1,000 will be 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.
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.
You can view AMS learning paths here:
Use the User Voice forum to provide feedback and make suggestions on how to improve Azure Media Services. You can also go directly to one of the following categories: